Can not install - workstation components on Longhorn x86 or x64

Is Katmai supported on Longhorn? I tried both x64 and x86 (development edition) on Longhorn x64 and x86 versions respectively. The workstation components get errors and rolled back. Any fix?

I want to try Lognhorn, Katmai, Orcas, Biztalk R2 (on 32-bit platform first) and then x64. Can someone recommend what stacks are tried/supported ?

(Pingala@.discussions.microsoft.com) writes: > Is Katmai supported on Longhorn? I tried both x64 and x86 (development > edition) on Longhorn x64 and x86 versions respectively. The workstation > components get errors and rolled back. Any fix? The Readme says that Katmai runs on Win2003 SP1 x86/x64 and WinXP SP2 x86/x64. It's silent on Vista, Longhorn and Windows 2000. But I can answer the latter: it does not run on Win2000. I've tried. I guess that if you want to run Katmai on Longhorn, that you will have to wait for a later CTP. -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||

Actually, I postponed x64 tests.

On x86 Longhorn (w2k8), I was successful with Katmai when I installed a) .NET Framework 3.5 and b) windows update.

I also installed Orcas CTP and BizTalk 2006 R2 CTP. However, I did not see the Biztalk projects in VS. I am wondering why. I have to check with Biztalk forum.

|||

Has anyone been able to get reporting services for Katmai running on Longhorn?

Thanks,

Can not install - workstation components on Longhorn x86 or x64

Is Katmai supported on Longhorn? I tried both x64 and x86 (development edition) on Longhorn x64 and x86 versions respectively. The workstation components get errors and rolled back. Any fix?

I want to try Lognhorn, Katmai, Orcas, Biztalk R2 (on 32-bit platform first) and then x64. Can someone recommend what stacks are tried/supported ?

(Pingala@.discussions.microsoft.com) writes: > Is Katmai supported on Longhorn? I tried both x64 and x86 (development > edition) on Longhorn x64 and x86 versions respectively. The workstation > components get errors and rolled back. Any fix? The Readme says that Katmai runs on Win2003 SP1 x86/x64 and WinXP SP2 x86/x64. It's silent on Vista, Longhorn and Windows 2000. But I can answer the latter: it does not run on Win2000. I've tried. I guess that if you want to run Katmai on Longhorn, that you will have to wait for a later CTP. -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||

Actually, I postponed x64 tests.

On x86 Longhorn (w2k8), I was successful with Katmai when I installed a) .NET Framework 3.5 and b) windows update.

I also installed Orcas CTP and BizTalk 2006 R2 CTP. However, I did not see the Biztalk projects in VS. I am wondering why. I have to check with Biztalk forum.

|||

Has anyone been able to get reporting services for Katmai running on Longhorn?

Thanks,

Can not connect to mssql with php

Using mssql_connect($server, $user, $password) results in different ways the 'php server'

connects to the sql server.

On a workstation with WinXPProf, php uses the $user and $password to login and uses the

sql server authentication. Running the same script from a W2K3 server results in an error

because in this case the 'php server' tries to connect to the sql server using windows

authentication. (I have checked this difference with wireshark)

The problem has nothing to do with the sql server settings (mixed mode) / firewalls /

php.ini- file settings or versions of ntwdblib.dll because these are the same for both

connections. The problem looks more fundamental, probably due to settings in windows or

the iis version running on the server and the workstation.

Does anyone has a clue how to force php to use sql server authentication.

Pitching Theo pitcher_32@.hotmail.com

It should be as simple as setting mssql.secure_connection = Off in your php.ini. (Informative thread) If that still doesn't do it, check the output of the phpinfo() function to make sure php is using the php.ini file that you believe it is (I've had that bite me in the butt once or twice before).
|||

Like I said both php boxes read the php.ini file and yes mssql.secure_connection = Off.

This is also confirmed by phpinfo().

It seems to be a problem for more than 4 years now checking all sort of discussions

on the net. A lot of people mention this problem but no one seems to know why one

php box tries to login to the sql server with "serverName\IUSR_serverName"

(anonymous IIS account) and the other php box with an empty string continuing with

an sql server authentication providing $user and $password from the mssql_connect()

function. Like I said it doesn't look a php problem/setting but a windows specific thing.

Anyone has a clue ? please let me know

sql

Can not connect to mssql with php

Using mssql_connect($server, $user, $password) results in different ways the 'php server'

connects to the sql server.

On a workstation with WinXPProf, php uses the $user and $password to login and uses the

sql server authentication. Running the same script from a W2K3 server results in an error

because in this case the 'php server' tries to connect to the sql server using windows

authentication. (I have checked this difference with wireshark)

The problem has nothing to do with the sql server settings (mixed mode) / firewalls /

php.ini- file settings or versions of ntwdblib.dll because these are the same for both

connections. The problem looks more fundamental, probably due to settings in windows or

the iis version running on the server and the workstation.

Does anyone has a clue how to force php to use sql server authentication.

Pitching Theo pitcher_32@.hotmail.com

It should be as simple as setting mssql.secure_connection = Off in your php.ini. (Informative thread) If that still doesn't do it, check the output of the phpinfo() function to make sure php is using the php.ini file that you believe it is (I've had that bite me in the butt once or twice before).
|||

Like I said both php boxes read the php.ini file and yes mssql.secure_connection = Off.

This is also confirmed by phpinfo().

It seems to be a problem for more than 4 years now checking all sort of discussions

on the net. A lot of people mention this problem but no one seems to know why one

php box tries to login to the sql server with "serverName\IUSR_serverName"

(anonymous IIS account) and the other php box with an empty string continuing with

an sql server authentication providing $user and $password from the mssql_connect()

function. Like I said it doesn't look a php problem/setting but a windows specific thing.

Anyone has a clue ? please let me know

Can my ASP.NET dev workstation see remote SQL server?

I would like to develop my ASP.NET application against a SQL 2000 database
residing on another server, rather than against the SQL server installed
locally. We're using Windows integrated security. When I'm using Visual
Studio the ASP.NET user belongs to my XP machine's local domain, which is
not recognized by the remote SQL server as belong to its domain. It is
possible to set up the SQL Server, my local XP machine, or my web.config
file so that when I develop an app in Visual Studio (Debug -> Start), I can
access the remote SQL database?
Thanks !You should be able to register the server using the format domain\username
and then develop against it. NOTE that, by default, the method of security
is windows and not mixed, but that sounds fine in your case.
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
****************************************
******************************
Think Outside the Box!
****************************************
******************************
"Timo" <timo@.anonymous.com> wrote in message
news:uPs3ZS4BEHA.624@.TK2MSFTNGP10.phx.gbl...
> I would like to develop my ASP.NET application against a SQL 2000 database
> residing on another server, rather than against the SQL server installed
> locally. We're using Windows integrated security. When I'm using Visual
> Studio the ASP.NET user belongs to my XP machine's local domain, which is
> not recognized by the remote SQL server as belong to its domain. It is
> possible to set up the SQL Server, my local XP machine, or my web.config
> file so that when I develop an app in Visual Studio (Debug -> Start), I
can
> access the remote SQL database?
> Thanks !
>|||Timo wrote:

> I would like to develop my ASP.NET application against a SQL 2000 database
> residing on another server, rather than against the SQL server installed
> locally. We're using Windows integrated security. When I'm using Visual
> Studio the ASP.NET user belongs to my XP machine's local domain, which is
> not recognized by the remote SQL server as belong to its domain. It is
> possible to set up the SQL Server, my local XP machine, or my web.config
> file so that when I develop an app in Visual Studio (Debug -> Start), I ca
n
> access the remote SQL database?
> Thanks !
In order to have ASP.NET connect to the database server, you must
configure ASP.NET to run as a domain account. I believe it is the
machine.config file that you will need to modify on Windows XP to change
what user ASP.NET runs as. It is different on different OSes. The good
thing is that with Windows 2003 you configure it directly in IIS and
each application can run under a different user.
Aaron Weiker
http://blogs.sqladvice.com/aweiker
http://aaronweiker.com/|||You certainly can
A couple of ways to do it (one OR the other)
1) Edit machine.config (C:\WINNT\Microsoft.NET\Framework\v.....\Config) and
change the userName / password of the <processModel ..> element as described
in the same file
That way you can run the ASP.NET working process on the identity of a domain
account that may be allowed access to the SQL Server
2) For your Web application (on the IIS console), replace the default
anonymous user (IUSR_xxxxxxx) with a domain user / password and allow access
to that user in the SQL Server. You should also set <identity
impersonate=true> in your Web.config
Regards
Jose.
"Timo" <timo@.anonymous.com> escribi en el mensaje
news:uPs3ZS4BEHA.624@.TK2MSFTNGP10.phx.gbl...
> I would like to develop my ASP.NET application against a SQL 2000 database
> residing on another server, rather than against the SQL server installed
> locally. We're using Windows integrated security. When I'm using Visual
> Studio the ASP.NET user belongs to my XP machine's local domain, which is
> not recognized by the remote SQL server as belong to its domain. It is
> possible to set up the SQL Server, my local XP machine, or my web.config
> file so that when I develop an app in Visual Studio (Debug -> Start), I
can
> access the remote SQL database?
> Thanks !
>|||I follow step #1 below (it seems preferable to editing the live IIS server).
On my local PC, I edit the userName element replacing the value with
DOMAIN\USERNAME
This domain user has been granted login on the remote SQL server, has been
granted dbaccess, and has been added as a member of a role which can access
the relevant tables.When I try to run my ASP.NET page, I get the following
error:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection
I don't know what our network admin has done when setting up my PC, which
has XP Pro on it; he is used to Win2K. He knows only a little more than I do
about Windows authentication, which has me worried :-) Why does the error
message have 'null' for the username? Because SQL does not recognize it and
so refuses to repeat the name?
Thanks
Timo
"Jose Marcenaro" <josem@.nospam.da-vinci.com.ar> wrote in message
news:eDZZXh4BEHA.3568@.tk2msftngp13.phx.gbl...
> You certainly can
> A couple of ways to do it (one OR the other)
> 1) Edit machine.config (C:\WINNT\Microsoft.NET\Framework\v.....\Config)
and
> change the userName / password of the <processModel ..> element as
described
> in the same file
> That way you can run the ASP.NET working process on the identity of a
domain
> account that may be allowed access to the SQL Server
> 2) For your Web application (on the IIS console), replace the default
> anonymous user (IUSR_xxxxxxx) with a domain user / password and allow
access
> to that user in the SQL Server. You should also set <identity
> impersonate=true> in your Web.config
> Regards
> Jose.
> "Timo" <timo@.anonymous.com> escribi en el mensaje
> news:uPs3ZS4BEHA.624@.TK2MSFTNGP10.phx.gbl...
database
Visual
is
> can
>|||Thanks for responding. But I don't know what is meant by "register the
server". Is that something I do with Visual Studio.NET? Do I need a special
"enterprise" level of VS.NET for that?
Timo
"Cowboy (Gregory A. Beamer)" <NoSpamMgbworld@.comcast.netNoSpamM> wrote in
message news:u2P1gd4BEHA.2380@.TK2MSFTNGP10.phx.gbl...
> You should be able to register the server using the format domain\username
> and then develop against it. NOTE that, by default, the method of security
> is windows and not mixed, but that sounds fine in your case.
> --
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
> "Timo" <timo@.anonymous.com> wrote in message
> news:uPs3ZS4BEHA.624@.TK2MSFTNGP10.phx.gbl...
database
Visual
is
> can|||Login failed for user 'null' means that we were unable to 'impersonate' the
user. We need to be able to impersonate when we authenticate to SQL using
your Windows NT credentials.
Typical client server environment:
Scenario 1:
Client --> SQL
If this fails, then it may be a problem with the communication between the
client and the Domain Controller. You can make network traces from the
client and /or enable Kerberos logging to verify if this is the case. This
may occur when using sockets, but not with Named Pipes connections.
Scenario 2:
Web Server/SQL Environment
Client-->IIS-->SQL.
If your scenario looks like the Scenario 2 (Web Server/SQL Environment),
then this scenario is more complicated to configure.
The middle machine (IIS) must be trusted for Security Delegation. And the
Domain Admin needs to set the spn for SQL Server.
The client machine must use TCP/IP and authenticate via Kerberos
authentication. If it uses NTLM, then this will fail with "Login failed
for user 'null'".
This article goes over various scenarios:
http://msdn.microsoft.com/library/d...-us/dnnetsec/ht
ml/SecNetch05.asp
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||If you want to use step #1 (ASPNET account) make sure you dont have
<impersonate="true"> in Web.config (you should keep the default which is
false or absent).
Otherwise, the local IUSR_xxxxx identity would be used.
If you do not currently have <impersonate="true"> ... then I guess it may be
some "extra-cautious" security setting of XPPro which prevents the identity
to be passed along.. sorry for not being able to help there
"Timo" <timo@.anonymous.com> escribi en el mensaje
news:e7M3M$4BEHA.3472@.TK2MSFTNGP09.phx.gbl...
> I follow step #1 below (it seems preferable to editing the live IIS
server).
> On my local PC, I edit the userName element replacing the value with
> DOMAIN\USERNAME
> This domain user has been granted login on the remote SQL server, has been
> granted dbaccess, and has been added as a member of a role which can
access
> the relevant tables.When I try to run my ASP.NET page, I get the following
> error:
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection
> I don't know what our network admin has done when setting up my PC, which
> has XP Pro on it; he is used to Win2K. He knows only a little more than I
do
> about Windows authentication, which has me worried :-) Why does the error
> message have 'null' for the username? Because SQL does not recognize it
and
> so refuses to repeat the name?
> Thanks
> Timo
>
> "Jose Marcenaro" <josem@.nospam.da-vinci.com.ar> wrote in message
> news:eDZZXh4BEHA.3568@.tk2msftngp13.phx.gbl...
> and
> described
> domain
> access
> database
installed
> Visual
> is
is
web.config
I
>

Can I manage MSDE with SSMS?

Hello,

We have an XP workstation containing a very important MSDE-based
application. Its MSDE database isn't likely to change for quite a
while.

The app contains an internal backup method (File, Backup, Backup) and
an auxiliary app/script for shrinking the database and logs. I would
like to automate the backup and shrinking so end users don't have to
remember to do them.

The workstation has a static IP so it can go out to the Internet when
necessary.
The workstation is presently not joined to the domain.

1. Can I install SSMS Express *only* as a local app (without SQL
Express 2005) and thus use SSMS to set up nightly backups and periodic
shrink database/logs jobs??

2. We have SSMS running on SQL 2005 server box in the domain. If I
join the workstation only to the domain (local account logon is not
changed, still used), could I use SSMS from the SQL 2005 box?? Would I
need a domain login on the XP box to make this work??

Thank you, Tomtlyczko (tlyczko@.gmail.com) writes:

Quote:

Originally Posted by

The app contains an internal backup method (File, Backup, Backup) and
an auxiliary app/script for shrinking the database and logs. I would
like to automate the backup and shrinking so end users don't have to
remember to do them.

Shrinking? Have you read this one:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp

Quote:

Originally Posted by

1. Can I install SSMS Express *only* as a local app (without SQL
Express 2005) and thus use SSMS to set up nightly backups and periodic
shrink database/logs jobs??

SSMS or SSMS Express? SSMS Express does not have support for SQL Agent,
you would need the real SSMS.

There used to be a license issue which precluded using the SQL 2000
tools with MSDE. That is, it was technically possible, it was not just
permitted by the license. I don't know what applies for the SQL 2005
tools and MSDE. You may want to check this with your local MS
representative.

Quote:

Originally Posted by

2. We have SSMS running on SQL 2005 server box in the domain. If I
join the workstation only to the domain (local account logon is not
changed, still used), could I use SSMS from the SQL 2005 box?? Would I
need a domain login on the XP box to make this work??

You could connect with SQL authentication to the XP box.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx