I'm working on deploying an ASP.NET 2.0 app onto a Windows 2003 server and I'm having trouble with SQL 2000 authentication. When I run my app from my development box running IIS 5.1 I have no problems. In order to get it to work on my this machine, I had set the account for anonymous access to run under an ASPNETDOMAIN account and configured my SQL database to allow this account.
On the Windows 2003 box with IIS 6.0, I've done the same thing with anonymous access for the web app, and also created an application pool that the app runs under and have set the application pool to run under the same account. It appears the app is looking for a local SQL 2005 instance (which doesn't exist). Why would it do this and what do I need to change for this to work?
Error:An error has occurred while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be
caused by the fact that under the default settings SQL Server does not
allow remote connections. (provider: SQL Network Interfaces, error: 26
- Error Locating Server/Instance Specified)
Stack Trace:
[SqlException (0x80131904): An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)]
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +735043
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188
System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +820
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130
System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +27
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +47
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +68
Hi all,I have a Windows 2003 server, which is also a terminal server forapplication, with sql 2000 installed. My company has developed anapplication that uses SQL 2000 as its database. The application is aclient/server one. In each client computer there's a link to theapplication on the server. There is no problem with Windows 98,Windows 2000 pro, Windows xp pro clients, but the windows 95 onescannot log in to the database. The log of the application shows thefollowing error:connection error -2147467259. Cannot open database requested in login'database name'. Login fails.Till a week ago the application was running on a Windows 2000 serverwith SQL 2000 install and the W95 clients had no problem connecting tothe database, so my guess is the error has something to do withWindows 2003 server, but what'causing the error?I tried to install a newer version of MDAC (MDAC 2.5, the last versionof MDAC you can install on W95)but with no success. By the way W95clients have no problem accessing shared folder on the Windows 2003server.Any idea?ThanksMarino
When windows 2003 server is not log on to the domain, SQL worksfine.(workgroup) Everyone can connect to SQL. When everyone is on thedomain, nothing can connect remotely to SQL.
Just spoke w/ our network admin and he mentioned that we use SPI, so being brand new to ASP, i did some googling and found this string:
the username and password is the account i have for the database, which is windows authentication, so i made sure the domain was in there. i am unsure of what i am doing wrong.
Hello y'all, I have to do a new install of SERVER 2000 using WINDOWS 2003 . Has anyone done this. If so, what are the steps. Should I expect any problems ? Any help appreciated. Thanx
I have XP workstations and windows 2003 SBS. I setup an ODBC for anapplication (tried both User and System DSN), but after a few usage, I getthe following error:Connection failed:SQLState: 'HY000'SQL Server Error: 0[Microsoft][ODBC SQL Server Driver]Cannot generate SSPI context.Any ideas? Is this a bug?--Thank youPlease post only
I installed MS SQL 2000 on a Windows 2003 server cluster (no servicepacks). Both nodes are online and both domain controllers are online.I tried to install SP3 and got the following error:--------------Logon Account could not be validated.No authority could be contacted for authentication.---------------I installed SQL SP 2 and did not get the error but I do get it everytime I try to install SP3.Does anybody have an idea that might help resolve the problem.
Logins failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. (microsoft SQL Server, Error: 18452)
Hi Guys.
How are you, its something very complicated to understand my issue. i am receiving the above error message when i tried to login with using windows accout to connect to SQL server Instance using client tool.
ok Let me start step by step. 1) Initially we have one box using windows 2000 (OS) and having SQL Server 2000. 2) Here on SQL Server instance i have created windows account login and gave permissions to one of the database on that instance. 3) this windows account is in the right domain and also in the same domain 4) when i right click on Management Studio on the different machine --> Run As--> enter the windows account --> select the above Sql server instance.then connect 5) Here i am not able to connect to the sql server. the below error generates when i press the connect button Logins failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. (microsoft SQL Server, Error: 18452)
if we gave the full permission to connect to box with this windows account then i am able to connect the sql server instance, otherwise its not allowing me to connect to the Sql server instance.
we have another box using windows 2000 (OS) and having SQL Server 2005. i have followed the same as above with same windows account login. Here i am able to connect to the SQL Server Instance and also this windows account donot have permission to connet the box.
Anybody have idea about this issue??? if the SQL server 2000 doesnot have the option to connect remotely. unless that windows account have the full permissions to box. if you have any white paper please let know. i really appreciate for your effort, if you dont understand please let me know. thanks so much.
Hi !when installing sqlserver 2000 on a Windows 2003 server it explicitlytells "server not compatible with Windows 2003" during install, but itcan carry on.After we applied serfice pack 3a then the db server seems to runnormally, but does it risk to behave randomly afterwards ???Is sqlserver 2000 standard edition compatible with Windows 2003 server?Or does it exist a specific sqlserver edition for Win2003 ?thanks !Patrice
We got SQL Server 2000 Standard Edition SP3 running on Windows 2003 server.
Now, we would like to apply windows 2003 SP1 to the Operating System.
We are concerned that whether windows 2003 SP1 is compatible with SQL server 2000 (SP3)?
I was looking at the application comaptibility chart for Windows 2003 SP1.Among them SQL Server 2000 Enterprise Edition Service Pack 3a was listed but not the Standard Edition.
My Question - Is windows 2003 server SP1 is compatible with SQL Server 2000 (SP3)?
Can SQL 2000 32 bit run on a Windows 2003 64-bit Intel OS installation? What about the SQL 2000 64 bit version? Is the Enterprise Edition required for this?
I have been running Windows 2003 64bit and SQL2000 SP4 for over 2 months with out any issues.
Sadly we had a server crash "NTldr missing or corrupted"
now when the one engineer looked at it he suggested to reload the server with Windows 2003 32 bit version as there were known compatibility problems between 2003 64bit and SQL 2000 32bit but that you can install SQL 2000 32bit onto a Windows 2003 64 bit server.
Now i dont really believe this statement nor can i find any documentation supporting this. I believe this server might have crashed due to a new patch that was released the last 2 or 3 week either on Windows or SQL. Does anyone know where i can verify what patches was released?
Maybe someone else can share their thoughts with me.
We have SQL server 2000 on windows 2000. From our desktop MS Access was connected to database through ODBC. Since yesterday (after our consultant had updated another asp application in the same server) we are getting €œSQL Server Error: 18452. €¦.. Login failed for user €˜(null)€™. Reason: not associated with a trusted SQL Server connection. €œ
The consultant saying he did not touch any settings on server (?). And the problem is even server€™s security property shows it has mixed mode authentication. But I cannot connect to server even through my SQL server enterprise manager in windows authentication mode. I can connect if I use SQL server authentication. Through ODBC I can connect also and test fine, if I use SQL authentication. But the Access application wouldn€™t connect using SQL authentication in ODBC.
So, can any one help me to find out what else could be done to make sure that the server is going to accept windows authentication. I€™m thinking any other settings or registry change €¦ etc. Please help.
After differential restore I start Remedy service. It starts in few seconds.
After full restore the same service takes 15 minutes to start. Bothe the things are done through SQL service agent. Even manual restaring the service also takes 15 minutes after full restore. WHy is it happening this way?
I am looking for some recommendations for memory sizing and options for a SQL 2000 Cluster. This is a two node cluster built on Windows 2003 ENT SP1 (x86). Both the nodes have the following hardware:
- 4 x Dual Core AMD Processors - 16 GB Memory - EMC Shared Disk
We are running six SQL 2000 instances and don't expect each of these instances to use more than 1.7 GB of memory. All these instances are going to support BizTalk 2004 Databases. I already have /PAE enabled on the nodes. I am looking for the following answers:
- Do I need to enable AWE on all the instances even if the instances ? Currently, we don't have that enabled and we have seen some issues regarding excessive paging even when there is physical memory available. The DBAs think that we don't need to enable AWE. I am bit confused on this one.
- We normally run 3 instances on each node and would like size the cluster in such a way that it can take six instances in case of a node failure
I have a Windows 2003 Enterprise x64 edition cluster setup and functioning normally. Now, I am trying to get SQL Server 2000 installed as a failover cluster but am having some difficulty. When installing, I get the message '[sqsrvres] ODBC sqldriverconnect failed' in the event log. The message happens when the installer is trying to bring the SQL Server Service resource online.
I am able to ping the name of the instance successfully. I am able to manually start the 'MSSQL$InstanceName' service. I have turned off the firewall on both machines, but this did not help. I have the DTC Service setup as a resource in the same cluster group.
I also read http://support.microsoft.com/default.aspx?scid=kb;en-us;815431 which seemed promising, but did not reolve the problem.
I have a mobile device application using mobile sql 2005 replicating with sql 2000 in a x86 environment. This works fine!
I'm having issues getting this to work under Windows Server 2003 X64.
I've got all the components installed under the X64 environment including CLR 2.0 X64 and the mobile sql tools. the but when I run the Configure Web Synchronization Wizard I get the following error. SQL Server 2005 Mobile Edition Server Tools were not found on the IIS server. Run the SQL Server 2005 Mobile Edition Server Tools installer....
My question is: Were do I get the X64 version of these tools?
sqlce30setupen.msi sql2Ken@P4.msi
The SQL environment is X86 as follows: SQL2000 SP4
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Will it be possible to do an in-place upgrade from SQL 2000 Server Enterprise SP4 32 bit running on top of 64 bit Windows 2003 Enterprise , clustered, to SQL 2005 Enterprise 64 bit? The 32 bit SQL 2000 to 64 bit SQL 2005 in place upgrade seems questionable to me... Anybody tried anything like this?
Hi there,I have installed MS SQL Server 2005 on my machine with windows authentication. But now I want to switch the authentication mode to SQL Authentication. I am unable to switch, I can’t find the proper way to do so here in 2005.Could any one help me in doing this?Thank you,-Ahsan
Hi all,I just asked some people to help me out and phone microsoft with thefollowing information, kindly they refused unless we setup a supportcontract with them first, for pre-sales information. (That really doesnot sound like good business sense to me - anyway here is our problem,if anyone could help thanks)."To tell and ask microsoft:We will be setting up a microsoft sql server 2000 instance running on awindows 2003 server.1) We need to check this can run alongside a microsoft 2003 sql server(either workgroup or standard edition), on the same machine. Are thereany .dll clashes if we do this? If there are can we run SQL Server2000, in a virtual machine running windows 2000 professional. (I have alicenced copy we can use for this).2) If we run one instance of 2000, and one of 2003 of the sql servers,can one use the processor licence model, and one use the CAL licencemodel."Thanks for any help, and any idea why they actually force you to usenews groups for pre-sales information?David
My uncle runs a small networking company and has extra licenses for Windows 2003 Server as well as SQL Server 2000. Since I just graduated from college and have started working as a database programmer (for a different company) I'd like to setup a small server at home to learn more about SQL (as well as networking, but SQL is my primary concern). I know I can setup SQL Server 2000 on my main PC, but I'd still like to set everything up in a server environment.
So, what I'm wondering is if any books (or web sites?) exist that walk you through setting up Windows 2003 Server and SQL Server 2000. I've actually set these up before (it's not very complicated) but I'm not sure if I did it the "correct" way.
Ideally if any books exist on O'Reilly's Safari Bookshelf that would be even better.
Windows 2003 backup utility uses the shadow copy option that allows it to copy open files. Therefore, can I use this utility to backup the .mdf and .ldf files for my SQL 2000 database? I can then attach the .mdf files if I need to restore the database to another server. Can anyone tell me if this is safe? I've tried it and it worked but I'm worried there maybe some lurking danger in using this approach.
We got SQL Server 2000 Standard Edition SP3 running on Windows 2003 Standard Edition server.
Now, we would like to apply windows 2003 SP2 to the Operating System.
We are concerned that whether windows 2003 SP2 is compatible with SQL server 2000 (SP3)?
I was looking at the application compatibility chart for Windows 2003 SP2.Among them Microsoft SQL Server Standard (2000) was listed but with no Service pack details. And also does Standard means standard edition there?
My Question - Is windows 2003 server SP2 compatible with SQL Server 2000 (SP3) Standard Edition? And what if I plan to apply SP4 to Sql Server ?
I'moving my asp application to a new hosting server.
So when i tried the setup locally with the live DB & application in my test machine... The DB access is denied when application tries to hit the DB.
DB is in seperate machine with SQL Server 2000 & application(ASP) is in Windows server 2003..... Kindly help me with your suggestions....on what went wrong?
Where can I further educate myself on this subject?
Right off from the start I would assume that installing SQL Server 2000 or 2005 on Windows Server 2003 that is set up as a web server hosting a website would be against "best practices." Is my assumption right?
Common sense tells me to not to host a website on a pc that is also hosting my database.
set up windows 2003 serversql server 2000have public IP from netword soluctionsI can see websitewhat settings to i need to open up sql server to the public?
(Using win2k, sqlserver2k, framework 1.1) I have an fairly data-heavy application that uses Windows authentication (Trusted connection/aspnet account) to connect to Sql Server. The site uses IIS basic authentication.
On the dev server everything works fine but when I move to the live server things get strange and it starts to crawl along. (Pages load OK but then it just crawls as it loads the datagrids etc. Sometimes it brings back incomplete/incorrect data )
BUT When I use Sql Authentication to connect to Sql Server and there is no problem at all!
Ok, there is something obviously wrong with the live server (which is identical setup to dev)but I dont know where to start.
