Hi,
I have been using 'MSXML2.ServerXMLHttp.4.0' to make web requests from SQL server with no problems for about 6 months now (on Win2K Servers).
Now trying to move the databases onto a new 2003 server and getting the well known 'Access denied' error message. I beleive I have sorted out the following:
- Execute permissions on the master database for sp_OACreate, sp_OAGetErrorInfo,....
- Allowed 'All unkown ISAPI Extensions' - not that I'm happy about that!!
- Uninstalled the 'Internet Explorer Enhanced Security Configuration'
- I have enabled 'Submit nonencrypted form data' for the relevant zones in IE Security Settings
But none of these seem to have had an effect. I have also tried using WinHTTP.WinHTTPRequest.5.1 as suggested in a MS KB article, but this is not suitable as I need to pass authenitication parameters with each request, and it seems as though the response size is limited.
If anyone has any tips/checklists for getting this going I would be very interested.
TIASolved it!
My inablility to read MS Info, for others here is a very stripped down version:
exec @.hr = sp_OACreate 'WinHTTP.WinHTTPRequest.5.1', @.obj OUT
IF @.hr <> 0
BEGIN
EXEC sp_OAGetErrorInfo @.obj, @.src OUT, @.desc OUT
goto eh
END
exec @.hr = sp_OAMethod @.obj, 'open', NULL, "GET", @.sUr
IF @.hr <> 0
BEGIN
EXEC sp_OAGetErrorInfo @.obj, @.src OUT, @.desc OUT
goto eh
END
exec @.hr = sp_OAMethod @.obj, 'SetCredentials', NULL, 'USERNAME', 'PASSWORD', '0'
exec @.hr = sp_OAMethod @.obj, 'send'
IF @.hr <> 0
BEGIN
EXEC sp_OAGetErrorInfo @.obj, @.src OUT, @.desc OUT
goto eh
END
exec @.hr = sp_OAMethod @.obj, 'status', @.status OUT
IF @.hr <> 0
BEGIN
EXEC sp_OAGetErrorInfo @.obj, @.src OUT, @.desc OUT
goto eh
END
IF @.status <> 200
BEGIN
SET @.desc = 'HTTP request failed. Server returned status of ' +cast(@.status as varchar) + '.'
goto eh
END
exec @.hr = sp_OAGetProperty @.obj, 'responseText', @.response OUT
IF @.hr <> 0
BEGIN
EXEC sp_OAGetErrorInfo @.obj, @.src OUT, @.desc OUT
goto eh
END
exec @.hr = sp_OADestroy @.obj
return 0
eh:
exec @.hr = sp_OADestroy @.obj
Raiserror(@.desc, 16, 1)sql
Showing posts with label win2k. Show all posts
Showing posts with label win2k. Show all posts
Wednesday, March 21, 2012
MSSQLServerADHelper Service Error on Reboot
I am running SQL Server 2000 sp 4 on Win2K Server sp 4.
Recently, I started getting an MSSQLServerADHelper service error. I can't
rely pin it on anything, other than I had a big database with 2 tables (7 and
20 million records respectively). I ran out of disk space trying to index
one of the tables.
Ultimately, I detached the database, because it was too much for my system.
Since then I have completely removed then reinstalled SQL Server and I still
get the following errors. The MSSQLServerADHelper is set to automatic, which
I believe is the correct state since is supposedly launched as needed. I
have done some research and cannot track down an answer. Any ideas?
Event Type:Error
Event Source:Service Control Manager
Event Category:None
Event ID:7024
Date:6/26/2005
Time:1:54:11 AM
User:N/A
Computer:MERLOT
Description:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
Event Type:Error
Event Source:MSSQLServerADHelper
Event Category:None
Event ID:100
Date:6/26/2005
Time:1:54:11 AM
User:N/A
Computer:MERLOT
Description:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17055
Date:6/26/2005
Time:2:33:04 PM
User:N/A
Computer:MERLOT
Description:
19012 :
SuperSocket Info: Bind failed on TCP port 1433.
Data:
0000: 44 4a 00 00 10 00 00 00 DJ.....
0008: 07 00 00 00 4d 00 45 00 ...M.E.
0010: 52 00 4c 00 4f 00 54 00 R.L.O.T.
0018: 00 00 00 00 00 00 .....
The MSSQLServerADHelper service should be set to manual. SQL
Server will start and stop the service itself when needed.
-Sue
On Sun, 26 Jun 2005 20:06:01 -0700, Jed
<Jed@.discussions.microsoft.com> wrote:
>I am running SQL Server 2000 sp 4 on Win2K Server sp 4.
>Recently, I started getting an MSSQLServerADHelper service error. I can't
>rely pin it on anything, other than I had a big database with 2 tables (7 and
>20 million records respectively). I ran out of disk space trying to index
>one of the tables.
>Ultimately, I detached the database, because it was too much for my system.
>Since then I have completely removed then reinstalled SQL Server and I still
>get the following errors. The MSSQLServerADHelper is set to automatic, which
>I believe is the correct state since is supposedly launched as needed. I
>have done some research and cannot track down an answer. Any ideas?
>Event Type:Error
>Event Source:Service Control Manager
>Event Category:None
>Event ID:7024
>Date:6/26/2005
>Time:1:54:11 AM
>User:N/A
>Computer:MERLOT
>Description:
>The MSSQLServerADHelper service terminated with service-specific error
>3221225572.
>Event Type:Error
>Event Source:MSSQLServerADHelper
>Event Category:None
>Event ID:100
>Date:6/26/2005
>Time:1:54:11 AM
>User:N/A
>Computer:MERLOT
>Description:
>'0' is an invalid number of start up parameters. This service takes two
>start up parameters.
>Event Type:Error
>Event Source:MSSQLSERVER
>Event Category:(2)
>Event ID:17055
>Date:6/26/2005
>Time:2:33:04 PM
>User:N/A
>Computer:MERLOT
>Description:
>19012 :
>SuperSocket Info: Bind failed on TCP port 1433.
>Data:
>0000: 44 4a 00 00 10 00 00 00 DJ.....
>0008: 07 00 00 00 4d 00 45 00 ...M.E.
>0010: 52 00 4c 00 4f 00 54 00 R.L.O.T.
>0018: 00 00 00 00 00 00 .....
Recently, I started getting an MSSQLServerADHelper service error. I can't
rely pin it on anything, other than I had a big database with 2 tables (7 and
20 million records respectively). I ran out of disk space trying to index
one of the tables.
Ultimately, I detached the database, because it was too much for my system.
Since then I have completely removed then reinstalled SQL Server and I still
get the following errors. The MSSQLServerADHelper is set to automatic, which
I believe is the correct state since is supposedly launched as needed. I
have done some research and cannot track down an answer. Any ideas?
Event Type:Error
Event Source:Service Control Manager
Event Category:None
Event ID:7024
Date:6/26/2005
Time:1:54:11 AM
User:N/A
Computer:MERLOT
Description:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
Event Type:Error
Event Source:MSSQLServerADHelper
Event Category:None
Event ID:100
Date:6/26/2005
Time:1:54:11 AM
User:N/A
Computer:MERLOT
Description:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17055
Date:6/26/2005
Time:2:33:04 PM
User:N/A
Computer:MERLOT
Description:
19012 :
SuperSocket Info: Bind failed on TCP port 1433.
Data:
0000: 44 4a 00 00 10 00 00 00 DJ.....
0008: 07 00 00 00 4d 00 45 00 ...M.E.
0010: 52 00 4c 00 4f 00 54 00 R.L.O.T.
0018: 00 00 00 00 00 00 .....
The MSSQLServerADHelper service should be set to manual. SQL
Server will start and stop the service itself when needed.
-Sue
On Sun, 26 Jun 2005 20:06:01 -0700, Jed
<Jed@.discussions.microsoft.com> wrote:
>I am running SQL Server 2000 sp 4 on Win2K Server sp 4.
>Recently, I started getting an MSSQLServerADHelper service error. I can't
>rely pin it on anything, other than I had a big database with 2 tables (7 and
>20 million records respectively). I ran out of disk space trying to index
>one of the tables.
>Ultimately, I detached the database, because it was too much for my system.
>Since then I have completely removed then reinstalled SQL Server and I still
>get the following errors. The MSSQLServerADHelper is set to automatic, which
>I believe is the correct state since is supposedly launched as needed. I
>have done some research and cannot track down an answer. Any ideas?
>Event Type:Error
>Event Source:Service Control Manager
>Event Category:None
>Event ID:7024
>Date:6/26/2005
>Time:1:54:11 AM
>User:N/A
>Computer:MERLOT
>Description:
>The MSSQLServerADHelper service terminated with service-specific error
>3221225572.
>Event Type:Error
>Event Source:MSSQLServerADHelper
>Event Category:None
>Event ID:100
>Date:6/26/2005
>Time:1:54:11 AM
>User:N/A
>Computer:MERLOT
>Description:
>'0' is an invalid number of start up parameters. This service takes two
>start up parameters.
>Event Type:Error
>Event Source:MSSQLSERVER
>Event Category:(2)
>Event ID:17055
>Date:6/26/2005
>Time:2:33:04 PM
>User:N/A
>Computer:MERLOT
>Description:
>19012 :
>SuperSocket Info: Bind failed on TCP port 1433.
>Data:
>0000: 44 4a 00 00 10 00 00 00 DJ.....
>0008: 07 00 00 00 4d 00 45 00 ...M.E.
>0010: 52 00 4c 00 4f 00 54 00 R.L.O.T.
>0018: 00 00 00 00 00 00 .....
Monday, March 19, 2012
MSSQLServerADHelper Service Error on Reboot
I am running SQL Server 2000 sp 4 on Win2K Server sp 4.
Recently, I started getting an MSSQLServerADHelper service error. I can't
rely pin it on anything, other than I had a big database with 2 tables (7 an
d
20 million records respectively). I ran out of disk space trying to index
one of the tables.
Ultimately, I detached the database, because it was too much for my system.
Since then I have completely removed then reinstalled SQL Server and I still
get the following errors. The MSSQLServerADHelper is set to automatic, whic
h
I believe is the correct state since is supposedly launched as needed. I
have done some research and cannot track down an answer. Any ideas?
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 6/26/2005
Time: 1:54:11 AM
User: N/A
Computer: MERLOT
Description:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
Event Type: Error
Event Source: MSSQLServerADHelper
Event Category: None
Event ID: 100
Date: 6/26/2005
Time: 1:54:11 AM
User: N/A
Computer: MERLOT
Description:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 6/26/2005
Time: 2:33:04 PM
User: N/A
Computer: MERLOT
Description:
19012 :
SuperSocket Info: Bind failed on TCP port 1433.
Data:
0000: 44 4a 00 00 10 00 00 00 DJ.....
0008: 07 00 00 00 4d 00 45 00 ...M.E.
0010: 52 00 4c 00 4f 00 54 00 R.L.O.T.
0018: 00 00 00 00 00 00 .....The MSSQLServerADHelper service should be set to manual. SQL
Server will start and stop the service itself when needed.
-Sue
On Sun, 26 Jun 2005 20:06:01 -0700, Jed
<Jed@.discussions.microsoft.com> wrote:
>I am running SQL Server 2000 sp 4 on Win2K Server sp 4.
>Recently, I started getting an MSSQLServerADHelper service error. I can't
>rely pin it on anything, other than I had a big database with 2 tables (7 a
nd
>20 million records respectively). I ran out of disk space trying to index
>one of the tables.
>Ultimately, I detached the database, because it was too much for my system.
>Since then I have completely removed then reinstalled SQL Server and I stil
l
>get the following errors. The MSSQLServerADHelper is set to automatic, whi
ch
>I believe is the correct state since is supposedly launched as needed. I
>have done some research and cannot track down an answer. Any ideas?
>Event Type: Error
>Event Source: Service Control Manager
>Event Category: None
>Event ID: 7024
>Date: 6/26/2005
>Time: 1:54:11 AM
>User: N/A
>Computer: MERLOT
>Description:
>The MSSQLServerADHelper service terminated with service-specific error
>3221225572.
>Event Type: Error
>Event Source: MSSQLServerADHelper
>Event Category: None
>Event ID: 100
>Date: 6/26/2005
>Time: 1:54:11 AM
>User: N/A
>Computer: MERLOT
>Description:
>'0' is an invalid number of start up parameters. This service takes two
>start up parameters.
>Event Type: Error
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17055
>Date: 6/26/2005
>Time: 2:33:04 PM
>User: N/A
>Computer: MERLOT
>Description:
>19012 :
>SuperSocket Info: Bind failed on TCP port 1433.
>Data:
>0000: 44 4a 00 00 10 00 00 00 DJ.....
>0008: 07 00 00 00 4d 00 45 00 ...M.E.
>0010: 52 00 4c 00 4f 00 54 00 R.L.O.T.
>0018: 00 00 00 00 00 00 .....
Recently, I started getting an MSSQLServerADHelper service error. I can't
rely pin it on anything, other than I had a big database with 2 tables (7 an
d
20 million records respectively). I ran out of disk space trying to index
one of the tables.
Ultimately, I detached the database, because it was too much for my system.
Since then I have completely removed then reinstalled SQL Server and I still
get the following errors. The MSSQLServerADHelper is set to automatic, whic
h
I believe is the correct state since is supposedly launched as needed. I
have done some research and cannot track down an answer. Any ideas?
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 6/26/2005
Time: 1:54:11 AM
User: N/A
Computer: MERLOT
Description:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
Event Type: Error
Event Source: MSSQLServerADHelper
Event Category: None
Event ID: 100
Date: 6/26/2005
Time: 1:54:11 AM
User: N/A
Computer: MERLOT
Description:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 6/26/2005
Time: 2:33:04 PM
User: N/A
Computer: MERLOT
Description:
19012 :
SuperSocket Info: Bind failed on TCP port 1433.
Data:
0000: 44 4a 00 00 10 00 00 00 DJ.....
0008: 07 00 00 00 4d 00 45 00 ...M.E.
0010: 52 00 4c 00 4f 00 54 00 R.L.O.T.
0018: 00 00 00 00 00 00 .....The MSSQLServerADHelper service should be set to manual. SQL
Server will start and stop the service itself when needed.
-Sue
On Sun, 26 Jun 2005 20:06:01 -0700, Jed
<Jed@.discussions.microsoft.com> wrote:
>I am running SQL Server 2000 sp 4 on Win2K Server sp 4.
>Recently, I started getting an MSSQLServerADHelper service error. I can't
>rely pin it on anything, other than I had a big database with 2 tables (7 a
nd
>20 million records respectively). I ran out of disk space trying to index
>one of the tables.
>Ultimately, I detached the database, because it was too much for my system.
>Since then I have completely removed then reinstalled SQL Server and I stil
l
>get the following errors. The MSSQLServerADHelper is set to automatic, whi
ch
>I believe is the correct state since is supposedly launched as needed. I
>have done some research and cannot track down an answer. Any ideas?
>Event Type: Error
>Event Source: Service Control Manager
>Event Category: None
>Event ID: 7024
>Date: 6/26/2005
>Time: 1:54:11 AM
>User: N/A
>Computer: MERLOT
>Description:
>The MSSQLServerADHelper service terminated with service-specific error
>3221225572.
>Event Type: Error
>Event Source: MSSQLServerADHelper
>Event Category: None
>Event ID: 100
>Date: 6/26/2005
>Time: 1:54:11 AM
>User: N/A
>Computer: MERLOT
>Description:
>'0' is an invalid number of start up parameters. This service takes two
>start up parameters.
>Event Type: Error
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17055
>Date: 6/26/2005
>Time: 2:33:04 PM
>User: N/A
>Computer: MERLOT
>Description:
>19012 :
>SuperSocket Info: Bind failed on TCP port 1433.
>Data:
>0000: 44 4a 00 00 10 00 00 00 DJ.....
>0008: 07 00 00 00 4d 00 45 00 ...M.E.
>0010: 52 00 4c 00 4f 00 54 00 R.L.O.T.
>0018: 00 00 00 00 00 00 .....
MSSQLServerADHelper Service Error on Reboot
I am running SQL Server 2000 sp 4 on Win2K Server sp 4.
Recently, I started getting an MSSQLServerADHelper service error. I can't
rely pin it on anything, other than I had a big database with 2 tables (7 and
20 million records respectively). I ran out of disk space trying to index
one of the tables.
Ultimately, I detached the database, because it was too much for my system.
Since then I have completely removed then reinstalled SQL Server and I still
get the following errors. The MSSQLServerADHelper is set to automatic, which
I believe is the correct state since is supposedly launched as needed. I
have done some research and cannot track down an answer. Any ideas?
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 6/26/2005
Time: 1:54:11 AM
User: N/A
Computer: MERLOT
Description:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
Event Type: Error
Event Source: MSSQLServerADHelper
Event Category: None
Event ID: 100
Date: 6/26/2005
Time: 1:54:11 AM
User: N/A
Computer: MERLOT
Description:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 6/26/2005
Time: 2:33:04 PM
User: N/A
Computer: MERLOT
Description:
19012 :
SuperSocket Info: Bind failed on TCP port 1433.
Data:
0000: 44 4a 00 00 10 00 00 00 DJ.....
0008: 07 00 00 00 4d 00 45 00 ...M.E.
0010: 52 00 4c 00 4f 00 54 00 R.L.O.T.
0018: 00 00 00 00 00 00 .....The MSSQLServerADHelper service should be set to manual. SQL
Server will start and stop the service itself when needed.
-Sue
On Sun, 26 Jun 2005 20:06:01 -0700, Jed
<Jed@.discussions.microsoft.com> wrote:
>I am running SQL Server 2000 sp 4 on Win2K Server sp 4.
>Recently, I started getting an MSSQLServerADHelper service error. I can't
>rely pin it on anything, other than I had a big database with 2 tables (7 and
>20 million records respectively). I ran out of disk space trying to index
>one of the tables.
>Ultimately, I detached the database, because it was too much for my system.
>Since then I have completely removed then reinstalled SQL Server and I still
>get the following errors. The MSSQLServerADHelper is set to automatic, which
>I believe is the correct state since is supposedly launched as needed. I
>have done some research and cannot track down an answer. Any ideas?
>Event Type: Error
>Event Source: Service Control Manager
>Event Category: None
>Event ID: 7024
>Date: 6/26/2005
>Time: 1:54:11 AM
>User: N/A
>Computer: MERLOT
>Description:
>The MSSQLServerADHelper service terminated with service-specific error
>3221225572.
>Event Type: Error
>Event Source: MSSQLServerADHelper
>Event Category: None
>Event ID: 100
>Date: 6/26/2005
>Time: 1:54:11 AM
>User: N/A
>Computer: MERLOT
>Description:
>'0' is an invalid number of start up parameters. This service takes two
>start up parameters.
>Event Type: Error
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17055
>Date: 6/26/2005
>Time: 2:33:04 PM
>User: N/A
>Computer: MERLOT
>Description:
>19012 :
>SuperSocket Info: Bind failed on TCP port 1433.
>Data:
>0000: 44 4a 00 00 10 00 00 00 DJ.....
>0008: 07 00 00 00 4d 00 45 00 ...M.E.
>0010: 52 00 4c 00 4f 00 54 00 R.L.O.T.
>0018: 00 00 00 00 00 00 .....
Recently, I started getting an MSSQLServerADHelper service error. I can't
rely pin it on anything, other than I had a big database with 2 tables (7 and
20 million records respectively). I ran out of disk space trying to index
one of the tables.
Ultimately, I detached the database, because it was too much for my system.
Since then I have completely removed then reinstalled SQL Server and I still
get the following errors. The MSSQLServerADHelper is set to automatic, which
I believe is the correct state since is supposedly launched as needed. I
have done some research and cannot track down an answer. Any ideas?
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 6/26/2005
Time: 1:54:11 AM
User: N/A
Computer: MERLOT
Description:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
Event Type: Error
Event Source: MSSQLServerADHelper
Event Category: None
Event ID: 100
Date: 6/26/2005
Time: 1:54:11 AM
User: N/A
Computer: MERLOT
Description:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 6/26/2005
Time: 2:33:04 PM
User: N/A
Computer: MERLOT
Description:
19012 :
SuperSocket Info: Bind failed on TCP port 1433.
Data:
0000: 44 4a 00 00 10 00 00 00 DJ.....
0008: 07 00 00 00 4d 00 45 00 ...M.E.
0010: 52 00 4c 00 4f 00 54 00 R.L.O.T.
0018: 00 00 00 00 00 00 .....The MSSQLServerADHelper service should be set to manual. SQL
Server will start and stop the service itself when needed.
-Sue
On Sun, 26 Jun 2005 20:06:01 -0700, Jed
<Jed@.discussions.microsoft.com> wrote:
>I am running SQL Server 2000 sp 4 on Win2K Server sp 4.
>Recently, I started getting an MSSQLServerADHelper service error. I can't
>rely pin it on anything, other than I had a big database with 2 tables (7 and
>20 million records respectively). I ran out of disk space trying to index
>one of the tables.
>Ultimately, I detached the database, because it was too much for my system.
>Since then I have completely removed then reinstalled SQL Server and I still
>get the following errors. The MSSQLServerADHelper is set to automatic, which
>I believe is the correct state since is supposedly launched as needed. I
>have done some research and cannot track down an answer. Any ideas?
>Event Type: Error
>Event Source: Service Control Manager
>Event Category: None
>Event ID: 7024
>Date: 6/26/2005
>Time: 1:54:11 AM
>User: N/A
>Computer: MERLOT
>Description:
>The MSSQLServerADHelper service terminated with service-specific error
>3221225572.
>Event Type: Error
>Event Source: MSSQLServerADHelper
>Event Category: None
>Event ID: 100
>Date: 6/26/2005
>Time: 1:54:11 AM
>User: N/A
>Computer: MERLOT
>Description:
>'0' is an invalid number of start up parameters. This service takes two
>start up parameters.
>Event Type: Error
>Event Source: MSSQLSERVER
>Event Category: (2)
>Event ID: 17055
>Date: 6/26/2005
>Time: 2:33:04 PM
>User: N/A
>Computer: MERLOT
>Description:
>19012 :
>SuperSocket Info: Bind failed on TCP port 1433.
>Data:
>0000: 44 4a 00 00 10 00 00 00 DJ.....
>0008: 07 00 00 00 4d 00 45 00 ...M.E.
>0010: 52 00 4c 00 4f 00 54 00 R.L.O.T.
>0018: 00 00 00 00 00 00 .....
MSSQLSERVER service will not start
I Have a server running win2k and sql server 2k We wook a power hit and the server comes back but sql will not start up.. The 2 services MSSQLSERVER and SQLSERVER services are set for automaic but are not starting If i try a manual start it will not start. I also tried to use sql Service manager to start the server and it starts then stops right away. very puzzling.
I am new to SQL server 2k and not shure where to go form here.
win 2k server is on sp3 and sql is not patched.. I know that is bad and will get it fixed.
I am wondering if i am hosed and have to reinstall.
ANy help would be great.
ThanksDo the SQL logs and NT logs show anything?|||Originally posted by jh923
I Have a server running win2k and sql server 2k We wook a power hit and the server comes back but sql will not start up.. The 2 services MSSQLSERVER and SQLSERVER services are set for automaic but are not starting If i try a manual start it will not start. I also tried to use sql Service manager to start the server and it starts then stops right away. very puzzling.
I am new to SQL server 2k and not shure where to go form here.
win 2k server is on sp3 and sql is not patched.. I know that is bad and will get it fixed.
I am wondering if i am hosed and have to reinstall.
ANy help would be great.
Thanks
What id are you using for your SQLServerAgent? Is it admin and the paswword changed? If not admin, do you have policies in place to force password change. Is the Agent account licked out? Check the events log.|||Originally posted by jh923
I Have a server running win2k and sql server 2k We wook a power hit and the server comes back but sql will not start up.. The 2 services MSSQLSERVER and SQLSERVER services are set for automaic but are not starting If i try a manual start it will not start. I also tried to use sql Service manager to start the server and it starts then stops right away. very puzzling.
I am new to SQL server 2k and not shure where to go form here.
win 2k server is on sp3 and sql is not patched.. I know that is bad and will get it fixed.
I am wondering if i am hosed and have to reinstall.
ANy help would be great.
Thanks
It is using the local system account
the event log showed
event it 17055
description: Error: 9003, severity:20, State:1
before description, there is a 18052
i cannnot look ate the sql logs becuse i cannot connect to it in enterprise manager
thanks|||The SQL logs are text files that can be opened with notepad/wordpad
check out: http://dbforums.com/arch/71/2003/2/692910 looks like a similar problem|||You can edit the Error.Log file from windows explorer.
I am new to SQL server 2k and not shure where to go form here.
win 2k server is on sp3 and sql is not patched.. I know that is bad and will get it fixed.
I am wondering if i am hosed and have to reinstall.
ANy help would be great.
ThanksDo the SQL logs and NT logs show anything?|||Originally posted by jh923
I Have a server running win2k and sql server 2k We wook a power hit and the server comes back but sql will not start up.. The 2 services MSSQLSERVER and SQLSERVER services are set for automaic but are not starting If i try a manual start it will not start. I also tried to use sql Service manager to start the server and it starts then stops right away. very puzzling.
I am new to SQL server 2k and not shure where to go form here.
win 2k server is on sp3 and sql is not patched.. I know that is bad and will get it fixed.
I am wondering if i am hosed and have to reinstall.
ANy help would be great.
Thanks
What id are you using for your SQLServerAgent? Is it admin and the paswword changed? If not admin, do you have policies in place to force password change. Is the Agent account licked out? Check the events log.|||Originally posted by jh923
I Have a server running win2k and sql server 2k We wook a power hit and the server comes back but sql will not start up.. The 2 services MSSQLSERVER and SQLSERVER services are set for automaic but are not starting If i try a manual start it will not start. I also tried to use sql Service manager to start the server and it starts then stops right away. very puzzling.
I am new to SQL server 2k and not shure where to go form here.
win 2k server is on sp3 and sql is not patched.. I know that is bad and will get it fixed.
I am wondering if i am hosed and have to reinstall.
ANy help would be great.
Thanks
It is using the local system account
the event log showed
event it 17055
description: Error: 9003, severity:20, State:1
before description, there is a 18052
i cannnot look ate the sql logs becuse i cannot connect to it in enterprise manager
thanks|||The SQL logs are text files that can be opened with notepad/wordpad
check out: http://dbforums.com/arch/71/2003/2/692910 looks like a similar problem|||You can edit the Error.Log file from windows explorer.
Subscribe to:
Posts (Atom)