When starting my SQL Server 2000 generate error and stop. This is the log:
Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
2004-01-20 11:05:36.59 server Copyright (C) 1988-2000 Microsoft Corporation.
2004-01-20 11:05:36.59 server All rights reserved.
2004-01-20 11:05:36.59 server Server Process ID is 115.
2004-01-20 11:05:36.59 server Logging SQL Server messages in file 'C:MSSQL7logERRORLOG'.
2004-01-20 11:05:36.63 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-01-20 11:05:36.66 server SQL Server configured for thread mode processing.
2004-01-20 11:05:36.66 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2004-01-20 11:05:36.67 server Attempting to initialize Distributed Transaction Coordinator.
2004-01-20 11:05:38.69 spid3 Starting up database 'master'.
2004-01-20 11:05:38.85 spid3 Server name is 'DB_SERVER'.
2004-01-20 11:05:38.85 server Using 'SSNETLIB.DLL' version '8.0.194'.
2004-01-20 11:05:38.87 server SQL server listening on TCP, Shared Memory, Named Pipes.
2004-01-20 11:05:38.87 server SQL server listening on 192.168.1.29:1433, 172.16.48.10:1433, 127.0.0.1:1433.
2004-01-20 11:05:38.87 server SQL Server is ready for client connections
2004-01-20 11:05:38.87 spid5 Starting up database 'model'.
2004-01-20 11:05:38.87 spid8 Starting up database 'msdb'.
2004-01-20 11:05:38.87 spid9 Starting up database 'pubs'.
2004-01-20 11:05:38.87 spid10 Starting up database 'Northwind'.
2004-01-20 11:05:38.87 spid11 Starting up database 'SIM'.
2004-01-20 11:05:39.21 spid5 Error: 9003, Severity: 20, State: 1
2004-01-20 11:05:39.21 spid5 The LSN (5:377:1) passed to log scan in database 'model' is invalid..
2004-01-20 11:05:39.31 spid8 Bypassing recovery for database 'msdb' because it is marked SUSPECT.
2004-01-20 11:05:39.39 spid11 Starting up database 'GMS'.
2004-01-20 11:05:39.39 spid8 Starting up database 'euro'.
2004-01-20 11:05:40.14 spid10 Starting up database 'TigrisDB'.
hi .everyone ! i have ms visual studio 2005 with sql sever 2005 management tools
anyway .. i want to use and install sql server 2000 in this machine .. i tried to install it, but when i tried to connect to the server .. it gives me this error: "you must use sql server 2005 management tools to connect to this server"
Hi, I am a VB programmer and we have a VB application that uses Access as its db (~500MB mdb file) using DAO. We want to upgrade to MSDE/Sql Server because we have clients that will use around 5 connections to the db and others with no more then 20 users. I was asked to build a simple test program in Vb under MSDE that will enable us to test few clients working simultaneously (I have few days for that). There is so much material on MSDE and we just ordered an MSDE Developer guide book from the Amazon that will arrive in a few days. The amount of material is confusing like hell and I didn't work with ADO before, I don't even know if to work with Access 2000 or with a different db, can you advice ? Do you know of a good sample that show a beginner like me how to access MSDE from VB using ADO? If you do please please advice it will ease the pressure and the days are numbered. Thanks a lot.
I never use Microsoft SQL Server .. somebody told me to start with 2000 version .. but I know that there is 2005 I want to know if it is ok to start with 2000 version and at the same time i can follow others who use 2005? Thanks
the service is already automatic, but when starting Windows XP MSDE "asks" to be installed correctly, run setup again and as you can imagine i did so. I can't find the answer
for some reason i dont get any errors, but i believe that my server isnot running on port 1433. the tcpip protocol is selected in thenetwork configuration utility as well as name piper. the portselected is 1433. but when i telnet to 1433 i get the same errors as iwould if i telnet to a non existant port. i also tried nbstat with noluck. what else can i do? thanks
I'm new to sql. Can someone help me to write a script to select overlapping start dates for each client records. For example: Clientid 1 have 3 episode as below(I only want to see the first two records with overlapping start date records)
We have a sql2000 clustered server running on a windows 2003 cluster, today we noticed that the SQL resources where in a Online Pending state and do not came up anymore.
I have searched the net and found some info about the sqlstate = 08001 Native error 11 , witch indicated that the SQL Network name could have been renamed , however this is not the case here , . i also found that there might be Resolve issue but The Cluster Name and the SQL Network name can be resolved by both Cluster nodes ..
does anyone here got experience with this kind of problem ? Pls Help
Here is a part of the cluster.log with the errors :
ERR SQL Server : [sqsrvres] ODBC sqldriverconnect failed ERR SQL Server : [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = 11; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. ERR SQL Server : [sqsrvres] ODBC sqldriverconnect failed ERR SQL Server : [sqsrvres] checkODBCConnectError: sqlstate = 01000; native error = 2; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). ERR SQL Server : [sqsrvres] ODBC sqldriverconnect failed ERR SQL Server : [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = 11; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. ERR SQL Server : [sqsrvres] ODBC sqldriverconnect failed ERR SQL Server : [sqsrvres] checkODBCConnectError: sqlstate = 01000; native error = 2; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). INFO [CP] CppRegNotifyThread checkpointing key SOFTWAREMicrosoftMicrosoft SQL ServerDBHSBMSSQLSERVER to id 4 due to timer INFO [Qfs] QfsGetTempFileName C:DOCUME~1SRVCCL~1LOCALS~1Temp, CLS, 13 => C:DOCUME~1SRVCCL~1LOCALS~1TempCLSD.tmp, status 0
According to the SQL server log the server is started and all databases are brought on-line then a stop request from Service Control Manager terminates SQL Server see log below:
2007-11-05 14:04:02.89 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: )
2007-11-05 14:04:02.89 server Copyright (C) 1988-2002 Microsoft Corporation. 2007-11-05 14:04:02.89 server All rights reserved. 2007-11-05 14:04:02.89 server Server Process ID is 3264. 2007-11-05 14:04:02.89 server Logging SQL Server messages in file 'P:mssqlMSSQL$DBHSBlogERRORLOG'. 2007-11-05 14:04:02.89 server SQL Server is starting at priority class 'high'(2 CPUs detected). 2007-11-05 14:04:03.61 server initdata: Warning: Could not set working set size to 823168 KB. 2007-11-05 14:04:03.66 server SQL Server configured for thread mode processing. 2007-11-05 14:04:03.72 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks. 2007-11-05 14:04:03.77 server Attempting to initialize Distributed Transaction Coordinator. 2007-11-05 14:04:06.32 spid2 Starting up database 'master'. 2007-11-05 14:04:06.52 spid2 Server name is 'HSBSQL01DBHSB'. 2007-11-05 14:04:06.52 spid5 Starting up database 'msdb'. 2007-11-05 14:04:06.52 spid6 Starting up database 'model'. 2007-11-05 14:04:06.52 spid8 Starting up database 'dbHSB'. 2007-11-05 14:04:06.52 server Using 'SSNETLIB.DLL' version '8.0.2039'. 2007-11-05 14:04:06.56 server SQL server listening on 10.122.131.103: 1433. 2007-11-05 14:04:06.62 spid8 Analysis of database 'dbHSB' (7) is 100% complete (approximately 0 more seconds) 2007-11-05 14:04:06.63 server SQL server listening on TCP, Shared Memory, Named Pipes. 2007-11-05 14:04:06.63 server SQL Server is ready for client connections 2007-11-05 14:04:06.66 spid6 Clearing tempdb database. 2007-11-05 14:04:07.10 spid6 Starting up database 'tempdb'. 2007-11-05 14:04:07.20 spid2 Recovery complete. 2007-11-05 14:04:07.20 spid2 SQL global counter collection task is created. 2007-11-05 14:04:16.41 spid1 Warning: unable to allocate 'min server memory' of 1658MB. 2007-11-05 14:10:45.18 spid2 SQL Server is terminating due to 'stop' request from Service Control Manager.
Hi I have upgraded my local to sql server 2005, but still need to access the remote instance which is still at version 2008/8.0. Enterprise Manager has been removed (by the SQL server 2005 installation) Does anyone know how I can restart older version of SQL server instance (ie 2000/8.0) using SQL server Management Studio?
I don't have admin access on the server which the sql remote instance is hosted. Can get around it by asking the sys admin guy to do it for now but would prefer to continue to be able to do it myself. SQL Server Configuration Manager can only manage SQL server 2005 versions - a nice little caveat!
Is there a way to stop/start remote services using 'net stop/start'? - without having to write code.... I'll continue to search for a solution, but if someon can point me in the right direction, I'd be most greatful.
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?
moving to a new sql server box because of a problem with the SAN its connected to. started my named instance in single user mode and restored master. sqlserve.exe -c -m -s ovops now the instance won't start. tried starting it with the -t3608 switch.. won't start!! Its because my drive configuration is different on the new server than it was on the old server, I cannot start the instance because it is expecting model, msdb, temdb and all of the user databases on drives that don't exist?? what can I do?????
We are going insane trying to start Report Manager on a SQL Reporting Services 2000 installation. The programmer/admin who originally set this up for us is gone.
We recently upgraded a database/application server to a new server, causing the data source being used by reports in reporting services to no longer be valid. Unfortunately, we do not have access to the original report project to 're-deploy' with the corrected data source.
We desperately need to get the reports that are installed to retrieve their data from the new database location/machine. We understand this can be done by specifying a new data source in Report Manager. (To clarify, we have NOT moved the report servier installation or database, these remain in place - it's just the deployed reports that no longer point to the correct data source.)
For some reason, our Report Manager will no longer run - when we try to launch it, we get a windows login dialog - nothing will work here. We've tried both local and domain admins and constantly get ACCESS IS DENIED 401.3 error messages that we do not have permission/problems with ACL's.
We've gone so far as to allow EVERYONE read/write access to the ReportManager and ReportServer folders and the RS virtual directories, but nothing seems to help.
Can anyone help with this? Ideas on how to change our data source, or how to get back into Report Manager?
Since we are somewhat technical, but not experts, and don't have much more time to waste, we are willing to pay $500 for this project to someone willing to access the server and fix the problem so that the reports point to the correct database and restore access to Report Manager.
good morning everyone, I have created some scheduled jobs which basically are transfer data from Oracle DB to SQL server through DTS package. I created DTS pacakages and right click to schedule the job for daily run. I was able to execute DTS package to transfer data w/o problems at all. However it seemed scheduled job could not run automatically nor I kick off the job manually. I have attached the error message below. It seemed I need some components be installed. Would someone take a look and let me know what is it, name of the components, probably cost information? Thank you very much for the help in advance.
I have an install of SQL Server 2005 Developer Edition, and the Integration Services Service will not start. If I attempt to start the service via the Services Computer Management screen, the system throws a message that says the service started, then stopped.
If I attempt to start the service via the SQL Server Configuration Manager, I get a "service did not respond in a timely fashion", which is so unfashionable.
Of particular interest is that during the install I did get an error message about WMI security. Looking at the WMI Security tab in WMI Control, I noticed that the key that the setup program was trying to configure did not exist under "ServerEvents".
There is a key named "MSSQLSERVER", but that did not match the key that the setup program was complaining about.
I am not seeing any event log items relating to errors. The system log shows the service startup and service shutdown as information items.
I get the following error when I try to start SQL Server: "An error 1069 - (The service did not start due to logon failure) occured performing this service operation on the MSSQL Server service"
I'm switching between 6.5 and 7.0 and get the same message in both. It worked before, does anyone know what the problem can be?
I use an "SQL task" to run a stored procedure (SP) to bring me an XML as resultset. The SP generates an XML using "XML EXPLICIT".
When I run my package from my Visual Studio (at my PC) I get a clean XML that I am capable of traversing. I was very happy....but when I schedule a job on my server to run this package, I get : ERROR: End tag 'Doc' does not match the start tag 'D彈Ӏęoc. Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly'. (I had to add a log provider to catch this).
Why is getting a start tag with invalid characters, thus causing to fail my package?
Does it have to do with the regional settings on my PC/Server?
I am getting the following error when I try to start SQL 2005 Management Studio to manage my SQL Server : Cannot load the DLL xpstar.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.).
I've opened port 1433 in the Config Manager (error: The request failed or the service did not respond in a timely fashion.)
My Shared Memory Protocol is enabled, I've confirmed that the Server is allowed in Windows Firewall, I've configured the SQL Server to allow remote connections, I've started the SQL Browser with success....
I also receive the error message that (The MSSQL$SQLEXPRESS service on .... started and then stopped (Object Explorer)).
I uninstalled and reinstalled SQL Server Express 2012 and get the following failures:
Database Engine Services SQL Server Replication
I think this the the core of my issue. how to remedy this?
I have my Sql server 2005 running perfectly (until yesterday) on vista. But today when I tried to connect to the server I get error 3417 meaning my master database needs rebuilt or repaired.
I tried all sort of techniques I found on internet like checking if my data files in data dir are not compressed and for the SQL Server Servies it logs on local account with interact with desktop checkbox checked. But no luck.
I tried to use setup.exe in my installer CD to rebuild master database but it seems the cmd doing nothing. To rebuild, I use the following command “start /wait setup.exe /qn INSTANCENAME=<instance> REINSTALL=SQL_Engine REBUILDDATABASE=1 SAPWD=<New SA Password>�. This cmd runs but due to some reason my master db is not being repaired. Ideally, I should see recent date change for this file.
Please advice how can I connect back to my server again making sure my databases are not lost.
The local sql server that was working fine earlier does not start now. I have already created tables and accessed them using stored procedures.
I get an error 1069: The service did not start due to logon problems. I have only changed my domain password. I do not remember what authentication I chose for log on.
when i try to start SQL SERVER 2005 its give me this ERROR MESSAGE:
"The service did not respond to the start or control request in atimely fashion ,you need administrator privileges to be able to start/stop this servic.(SQLSAC)"
Notes: am login in as system administrator with full previligies,
its was work normally ,but after i made update for windows then this error hapen after windwos repair.
when i try to start SQL SERVER 2005 its give me this ERROR MESSAGE:
"The service did not respond to the start or control request in atimely fashion ,you need administrator privileges to be able to start/stop this servic.(SQLSAC)"
Notes: am login in as system administrator with full previligies,
its was work normally ,but after i made update for windows then this error hapen after windwos repair.
We have changed the Network Domain name of a SQL server and restarted before changing any of the settings in SQL server. When we now try to start the SQL server service manager we get the following error
Your SQL server is either corrupt or has been tampered with. Unknown package id please rerun setup
Any suggestions on how to get the SQL server back on line without having to take the server down and changing the Netowrk Domain Name back ??
Is there a trick to getting this installed correctly? Everything works great until it gets up to starting the service. Here is the complete section of my setup log file.
SQL 2005 Standard.
Machine : KINGSERVER550 Product : SQL Server Database Services Error : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually." -------------------------------------------------------------------------------- Machine : KINGSERVER550 Product : Microsoft SQL Server 2005 Product Version : 9.00.1399.06 Install : Failed Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0003_KINGSERVER550_SQL.log Last Action : InstallFinalize Error String : The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually." The error is (1067) The process terminated unexpectedly. Error Number : 29503
I searched a previous thread dealing with this error, but seems like nobody has found a solution.
I have Vista x64 and I had been fighting SQL Server for a few days and yesterday I decided for reinstallation. Unfortunately now I am not able to instal the server back!
Each time I got the following error (it refers to SQL Server service):
Code Snippet <Func Name='LaunchFunction'> Function=Do_sqlShutDownRANUInstance <Func Name='GetCAContext'> <EndFunc Name='GetCAContext' Return='T' GetLastError='203'> Doing Action: Do_sqlShutDownRANUInstance PerfTime Start: Do_sqlShutDownRANUInstance : Tue Sep 04 23:32:16 2007 <Func Name='Do_sqlShutDownRANUInstance'> Service SQLEXPRESS with parameters '' is being started at Tue Sep 04 23:32:16 2007 Unable to start service (3) Error Code: 0x80070003 (3) Windows Error Text: System nie może odnaleźć określonej ścieżki. Source File Name: sqlsetuplibservice.cpp Compiler Timestamp: Wed Jun 14 16:29:04 2006 Function Name: sqls::Service::Start Source Line Number: 316
Setting status of unmanaged components and removing unmanaged resources
Error Code: 3 MSI (s) (F4:E4) [23:32:24:490]: I/O on thread 3716 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:493]: I/O on thread 788 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:493]: I/O on thread 2948 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:493]: I/O on thread 4392 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:493]: I/O on thread 5048 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:495]: I/O on thread 4464 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:495]: I/O on thread 4992 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:495]: I/O on thread 4768 could not be cancelled. Error: 1168 MSI (s) (F4:E4) [23:32:24:497]: I/O on thread 3004 could not be cancelled. Error: 1168 MSI (s) (F4!4C) [23:32:24:497]: Product: Microsoft SQL Server 2005 -- Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually." The error is (3) System nie może odnaleźć określonej ścieżki. . Error 29503. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually." The error is (3) System nie może odnaleźć określonej ścieżki. . <Failure Type='Fatal' Error='3'> <EndFunc Name='LaunchFunction' Return='3' GetLastError='203'> MSI (s) (F4:80) [23:32:24:507]: User policy value 'DisableRollback' is 0 MSI (s) (F4:80) [23:32:24:507]: Machine policy value 'DisableRollback' is 0 Action ended 23:32:24: InstallFinalize. Return value 3. MSI (s) (F4:80) [23:32:24:512]: Executing op: Header(Signature=1397708873,Version=400,Timestamp=925154312,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1) MSI (s) (F4:80) [23:32:24:512]: Executing op: DialogInfo(Type=0,Argument=1033) MSI (s) (F4:80) [23:32:24:513]: Executing op: DialogInfo(Type=1,Argument=Microsoft SQL Server 2005) MSI (s) (F4:80) [23:32:24:514]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1]) MSI (s) (F4:80) [23:32:24:516]: Executing op: ActionStart(Name=Do_sqlShutDownRANUInstance.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Running action to shutdown instance(Run As Normal User),) MSI (s) (F4:80) [23:32:24:517]: Executing op: ProductInfo(ProductKey={C3F5DBA5-ABFC-443E-AA60-928223AADF53},ProductName=Microsoft SQL Server 2005,PackageName=sqlrun_sql.msi,Language=1033,Version=151129058,Assignment=1,ObsoleteArg=0,ProductIcon=ARPIcon.ico,PackageMediaPath=Setup,PackageCode={08AD0897-0300-4F7D-A3CC-A0CCEDD42E0D},,,InstanceType=1,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3) MSI (s) (F4:80) [23:32:24:518]: Executing op: ActionStart(Name=ProcessComponents,Description=Updating component registration,) MSI (s) (F4:80) [23:32:24:519]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWAREMicrosoftWindowsCurrentVersionSharedDLLs,,BinaryType=0,) MSI (s) (F4:80) [23:32:24:520]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWAREMicrosoftWindowsCurrentVersionSharedDLLs,,BinaryType=0,) MSI (s) (F4:80) [23:32:24:520]: Executing op: ComponentUnregister(ComponentId={68C6D258-77E0-11D5-8528-00C04F68155C},ProductKey={C3F5DBA5-ABFC-443E-AA60-928223AADF53},BinaryType=0,) MSI (s) (F4:80) [23:32:24:520]: Executing op: ComponentUnregister(ComponentId={68C6D257-77E0-11D5-8528-00C04F68155C},ProductKey={C3F5DBA5-ABFC-443E-AA60-928223AADF53},BinaryType=0,)
"Windows could not start the SQL Server (RETAIL) service on local computer."
"Error 1053: The service did not respond to the start or control request in a timely fashion."
I am trying to start my SQL Server service and I get the above error. I am using Windows 7 32 bit. SQL 2008 R2 32bit. SQL has ran successfully for 2 years on this machine until a power outage the other night. Now I have this happening on two computers.
I have read every event viewer message up and down and searched Google for hours trying to find a solution. I have done so many things from changing dll's to reinstalling sql 2008 to trying sql 2012.
I uninstalled SQL2008 and installed SQL2012 and it had the exact same error message. It wont start that one process. I have read this forum and I see many instances of this issue being reported but none of them have been recent. I attempted to do everything the previous posts said to try and nothing has worked. I have tried to roll back using windows restore point, I have tried to change the servicespipetimeline registry edit in the HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControl. I have changed permissions.
I've installed Visual Studio 2005 Professional evaluation edition on both my desktop & on the server to try out the Debugger to be used with my Stored procedures
I got this error message every time i try to 'Step into Stored Procedure' from my desktop to connect to the stored procedure which resides on the Server.
Error message: Unable to Start T-SQL Debugging. Could not attach to SQL Server Process on 'Server1'.The RPC server is unavailable
The 'Step into Stored Procedure' works though if I open the stored procedure directly on the server.
Both my PC and Server has been installed with Remote Debugger and my windows login has been assigned permission to debug on the debugger that resides on the Server and has sysadmin server role on SQL 2005 both on PC and Server.
Can someone tell me what i miss out to debug Stored procedure in the SQL Server 2005 on the Server from my PC?
Hi all, I'm kinda new at programming, and am currently attempting to create a web application. I have an error when I try to insert information into a sql server database, and can't find how to fix it no matter how hard I try. The error I get is: Cannot start your application. The workgroup information file is missing or opened exclusively by another user. I have it so a user is logged in and is shown a form to fill out, then submits it (which creates an insert statement and sends it to the database). My connection string is as follows: CnnString = "Provider=Microsoft.Jet.OLEDB.4.0;" + "data source=serverdestination;" + "User id=user;" + "Password=pass;"; If you need any more information, just let me know. Any help would be greatly appreciated!
I have a web application developed in VS.NET 2005 [using C# as code behind]; and it uses SQL Server 2000 Enterprise edition as backend. The application runs fine, though it gives an error on IRREGULAR intervals on SQL data requests. Error Details: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
My problem is this: 1) Why does it show an error of SQL 2005, while I use SQL 2000. SQL 2005 is not even installed on the server, though VS.NET 2005 is installed. 2) The error comes only at irregular intervals. Users are able to login properly otherwise. 3) Application starts working again if we do either of the following: (a) Restart IIS (b) Restart application pool (c) Restart server. 4) Named pipes and TCP/IP are added to the "Network Configuration" of the SQL server 2000. 5) Error does not come on any specific page; or any specific code; or at any specific time. 6) We do not have any background service or any other activity happening on the server; and the server hosts only this application, within a single virtual root.
Any thoughts on why is this happening, and how to resolve this?
