model database locked

I receive the following message in the Event log when
trying to start SQLSERVER service...
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 11/06/2004
Time: 17:45:05
User: N/A
Computer: NWK-S-SQL
Description:
17052 :
Database 'model' cannot be opened. It is in the middle of
a restore.
Data:
0000: 9c 42 00 00 0a 00 00 00 œB.....
0008: 0a 00 00 00 4e 00 57 00 ...N.W.
0010: 4b 00 2d 00 53 00 2d 00 K.-.S.-.
0018: 53 00 51 00 4c 00 00 00 S.Q.L...
0020: 00 00 00 00 ...
This is preventing the service from starting... any
suggestions on how to resolve this? Unfortunately I do not
know how the database got into this state
After a reboot of the server, several databases came back
listed as 'loading' (in a restore mode) for no aparent
reason... after a further reboot... this!
all suggestions greatfully recieved
cheers
KeithHi,
If the model database is in middle of restore you can start sql server in
mimimal mode or Single user mode. To over come
thisadd the trace flag "-T3608" in the startup parameters. This trace flag
will
bypass recovery of databases except master. You should be able to start SQL
Server after this. After this try to restore the model
database from a backup.
(-T3608 can be added from control panel -- Admin tools-- services -- MSSQL
Server --Stop MSSQL Service-- In the parameter give the values -T3608--
Start MSSQL Server service)
If you still have issues then; stop SQL server service and then:-
1. COpy the exising model.mdf and modellog.ldf to a safe place
2. Overwriting model.mdf and modellog.ldf with the files in SQL Server CD,
and then try to startup the service.
Thanks
Hari
MCDBA
"Keith Newton" <keith.newton@.riba-enterprises.com> wrote in message
news:1b12c01c44fe1$fa128490$a601280a@.phx
.gbl...
> I receive the following message in the Event log when
> trying to start SQLSERVER service...
> Event Type: Information
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17055
> Date: 11/06/2004
> Time: 17:45:05
> User: N/A
> Computer: NWK-S-SQL
> Description:
> 17052 :
> Database 'model' cannot be opened. It is in the middle of
> a restore.
> Data:
> 0000: 9c 42 00 00 0a 00 00 00 œB.....
> 0008: 0a 00 00 00 4e 00 57 00 ...N.W.
> 0010: 4b 00 2d 00 53 00 2d 00 K.-.S.-.
> 0018: 53 00 51 00 4c 00 00 00 S.Q.L...
> 0020: 00 00 00 00 ...
> This is preventing the service from starting... any
> suggestions on how to resolve this? Unfortunately I do not
> know how the database got into this state
> After a reboot of the server, several databases came back
> listed as 'loading' (in a restore mode) for no aparent
> reason... after a further reboot... this!
> all suggestions greatfully recieved
> cheers
> Keith|||Hi,
If the model database is in middle of restore you can start sql server in
mimimal mode or Single user mode. To over come
thisadd the trace flag "-T3608" in the startup parameters. This trace flag
will
bypass recovery of databases except master. You should be able to start SQL
Server after this. After this try to restore the model
database from a backup.
(-T3608 can be added from control panel -- Admin tools-- services -- MSSQL
Server --Stop MSSQL Service-- In the parameter give the values -T3608--
Start MSSQL Server service)
If you still have issues then; stop SQL server service and then:-
1. COpy the exising model.mdf and modellog.ldf to a safe place
2. Overwriting model.mdf and modellog.ldf with the files in SQL Server CD,
and then try to startup the service.
Thanks
Hari
MCDBA
"Keith Newton" <keith.newton@.riba-enterprises.com> wrote in message
news:1b12c01c44fe1$fa128490$a601280a@.phx
.gbl...
> I receive the following message in the Event log when
> trying to start SQLSERVER service...
> Event Type: Information
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17055
> Date: 11/06/2004
> Time: 17:45:05
> User: N/A
> Computer: NWK-S-SQL
> Description:
> 17052 :
> Database 'model' cannot be opened. It is in the middle of
> a restore.
> Data:
> 0000: 9c 42 00 00 0a 00 00 00 œB.....
> 0008: 0a 00 00 00 4e 00 57 00 ...N.W.
> 0010: 4b 00 2d 00 53 00 2d 00 K.-.S.-.
> 0018: 53 00 51 00 4c 00 00 00 S.Q.L...
> 0020: 00 00 00 00 ...
> This is preventing the service from starting... any
> suggestions on how to resolve this? Unfortunately I do not
> know how the database got into this state
> After a reboot of the server, several databases came back
> listed as 'loading' (in a restore mode) for no aparent
> reason... after a further reboot... this!
> all suggestions greatfully recieved
> cheers
> Keith

model database locked

I receive the following message in the Event log when
trying to start SQLSERVER service...
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 11/06/2004
Time: 17:45:05
User: N/A
Computer: NWK-S-SQL
Description:
17052 :
Database 'model' cannot be opened. It is in the middle of
a restore.
Data:
0000: 9c 42 00 00 0a 00 00 00 œB.....
0008: 0a 00 00 00 4e 00 57 00 ...N.W.
0010: 4b 00 2d 00 53 00 2d 00 K.-.S.-.
0018: 53 00 51 00 4c 00 00 00 S.Q.L...
0020: 00 00 00 00 ...
This is preventing the service from starting... any
suggestions on how to resolve this? Unfortunately I do not
know how the database got into this state
After a reboot of the server, several databases came back
listed as 'loading' (in a restore mode) for no aparent
reason... after a further reboot... this!
all suggestions greatfully recieved
cheers
KeithHi,
If the model database is in middle of restore you can start sql server in
mimimal mode or Single user mode. To over come
thisadd the trace flag "-T3608" in the startup parameters. This trace flag
will
bypass recovery of databases except master. You should be able to start SQL
Server after this. After this try to restore the model
database from a backup.
(-T3608 can be added from control panel -- Admin tools-- services -- MSSQL
Server --Stop MSSQL Service-- In the parameter give the values -T3608--
Start MSSQL Server service)
If you still have issues then; stop SQL server service and then:-
1. COpy the exising model.mdf and modellog.ldf to a safe place
2. Overwriting model.mdf and modellog.ldf with the files in SQL Server CD,
and then try to startup the service.
Thanks
Hari
MCDBA
"Keith Newton" <keith.newton@.riba-enterprises.com> wrote in message
news:1b12c01c44fe1$fa128490$a601280a@.phx.gbl...
> I receive the following message in the Event log when
> trying to start SQLSERVER service...
> Event Type: Information
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17055
> Date: 11/06/2004
> Time: 17:45:05
> User: N/A
> Computer: NWK-S-SQL
> Description:
> 17052 :
> Database 'model' cannot be opened. It is in the middle of
> a restore.
> Data:
> 0000: 9c 42 00 00 0a 00 00 00 œB.....
> 0008: 0a 00 00 00 4e 00 57 00 ...N.W.
> 0010: 4b 00 2d 00 53 00 2d 00 K.-.S.-.
> 0018: 53 00 51 00 4c 00 00 00 S.Q.L...
> 0020: 00 00 00 00 ...
> This is preventing the service from starting... any
> suggestions on how to resolve this? Unfortunately I do not
> know how the database got into this state
> After a reboot of the server, several databases came back
> listed as 'loading' (in a restore mode) for no aparent
> reason... after a further reboot... this!
> all suggestions greatfully recieved
> cheers
> Keith

model database locked

I receive the following message in the Event log when
trying to start SQLSERVER service...
Event Type:Information
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17055
Date:11/06/2004
Time:17:45:05
User:N/A
Computer:NWK-S-SQL
Description:
17052 :
Database 'model' cannot be opened. It is in the middle of
a restore.
Data:
0000: 9c 42 00 00 0a 00 00 00 œB.....
0008: 0a 00 00 00 4e 00 57 00 ...N.W.
0010: 4b 00 2d 00 53 00 2d 00 K.-.S.-.
0018: 53 00 51 00 4c 00 00 00 S.Q.L...
0020: 00 00 00 00 ...
This is preventing the service from starting... any
suggestions on how to resolve this? Unfortunately I do not
know how the database got into this state
After a reboot of the server, several databases came back
listed as 'loading' (in a restore mode) for no aparent
reason... after a further reboot... this!
all suggestions greatfully recieved
cheers
Keith
Hi,
If the model database is in middle of restore you can start sql server in
mimimal mode or Single user mode. To over come
thisadd the trace flag "-T3608" in the startup parameters. This trace flag
will
bypass recovery of databases except master. You should be able to start SQL
Server after this. After this try to restore the model
database from a backup.
(-T3608 can be added from control panel -- Admin tools-- services -- MSSQL
Server --Stop MSSQL Service-- In the parameter give the values -T3608--
Start MSSQL Server service)
If you still have issues then; stop SQL server service and then:-
1. COpy the exising model.mdf and modellog.ldf to a safe place
2. Overwriting model.mdf and modellog.ldf with the files in SQL Server CD,
and then try to startup the service.
Thanks
Hari
MCDBA
"Keith Newton" <keith.newton@.riba-enterprises.com> wrote in message
news:1b12c01c44fe1$fa128490$a601280a@.phx.gbl...
> I receive the following message in the Event log when
> trying to start SQLSERVER service...
> Event Type: Information
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17055
> Date: 11/06/2004
> Time: 17:45:05
> User: N/A
> Computer: NWK-S-SQL
> Description:
> 17052 :
> Database 'model' cannot be opened. It is in the middle of
> a restore.
> Data:
> 0000: 9c 42 00 00 0a 00 00 00 œB.....
> 0008: 0a 00 00 00 4e 00 57 00 ...N.W.
> 0010: 4b 00 2d 00 53 00 2d 00 K.-.S.-.
> 0018: 53 00 51 00 4c 00 00 00 S.Q.L...
> 0020: 00 00 00 00 ...
> This is preventing the service from starting... any
> suggestions on how to resolve this? Unfortunately I do not
> know how the database got into this state
> After a reboot of the server, several databases came back
> listed as 'loading' (in a restore mode) for no aparent
> reason... after a further reboot... this!
> all suggestions greatfully recieved
> cheers
> Keith

MMC Cannot open

who knows how to fix this:
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\Sql Server Enterprise Manager.MSC.
This may be because the file doesnt exist, is not an MMC console, or
was created by a later version of MMC. This may also be because
you do not have sufficient access rights to the file.
I have rebooted the server, and restarted my machine, uninstalled and reinstalled SQL Server 7.0 Client. I still can't start SQL Server Enterprise Manager. Can anyone help?
Thanks in advance
Jane
Jane, once again, have you considered using SQL Server 2000 Enterprise
Manager? You seem to have both installed on your machine, and when you try
to launch 7.0 it is looking in \80\ and causing a conflict. I suggest
uninstalling SQL 7.0 client, reinstalling 2000 client, installing 2000 SP3a,
and using 2000 client tools.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:C0397850-DCCD-4AEE-9ADF-AAD21DC84737@.microsoft.com...
> who knows how to fix this:
> MMC cannot open the file C:\Program Files\Microsoft SQL
> Server\80\Tools\BINN\Sql Server Enterprise Manager.MSC.
> This may be because the file doesnt exist, is not an MMC console, or
> was created by a later version of MMC. This may also be because
> you do not have sufficient access rights to the file.
> I have rebooted the server, and restarted my machine, uninstalled and
reinstalled SQL Server 7.0 Client. I still can't start SQL Server Enterprise
Manager. Can anyone help?
> Thanks in advance
> Jane
>
|||Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000. The problem is very strange. I suppose I am locked by the server. Don't know what to do now.
As I said, I am new to SQL Server, I am trying to explore it. But there isn't a senior member in our team, so your help turns to be very important for me. I am looking forward to any ideas.
Cheers
Jane
|||Jane,
Refer the steps 3 to 5 given in the 'workaround' section of this article:
'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server 2000'
http://support.microsoft.com/default.aspx?id=272453
PS: I know that the title of the article doesnt concern you, but those steps
might help.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
> Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000.
The problem is very strange. I suppose I am locked by the server. Don't know
what to do now.
> As I said, I am new to SQL Server, I am trying to explore it. But there
isn't a senior member in our team, so your help turns to be very important
for me. I am looking forward to any ideas.
> Cheers
> Jane
|||Thanks for your help, but it doesn't work. Any ideas?
Jane
-- Dinesh T.K wrote: --
Jane,
Refer the steps 3 to 5 given in the 'workaround' section of this article:
'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server 2000'
http://support.microsoft.com/default.aspx?id=272453
PS: I know that the title of the article doesnt concern you, but those steps
might help.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
> Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000.
The problem is very strange. I suppose I am locked by the server. Don't know
what to do now.
> As I said, I am new to SQL Server, I am trying to explore it. But there
isn't a senior member in our team, so your help turns to be very important
for me. I am looking forward to any ideas.
> Cheers
> Jane
|||Jane,
May be EM is missing some DLLs .The relevant ones are
sqlns.dll,sqlmmc.dll,sqldmo.dll,dtsui.dll and sqllex.dll.Usually you can
find them in c:\mssql7\binn\.
Try re-registering them using regsvr32.exe.After each one, try opening up
EM.
If this too doesnt help, see if a reinstall of the relevant MDAC helps.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:032389DE-4113-42A4-9DA0-B78F4864A746@.microsoft.com...
> Thanks for your help, but it doesn't work. Any ideas?
> Jane
> -- Dinesh T.K wrote: --
> Jane,
> Refer the steps 3 to 5 given in the 'workaround' section of this
article:
> 'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server
2000'
> http://support.microsoft.com/default.aspx?id=272453
> PS: I know that the title of the article doesnt concern you, but
those steps[vbcol=seagreen]
> might help.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane" <anonymous@.discussions.microsoft.com> wrote in message
> news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
2000.
> The problem is very strange. I suppose I am locked by the server.
Don't know[vbcol=seagreen]
> what to do now.
there
> isn't a senior member in our team, so your help turns to be very
important
> for me. I am looking forward to any ideas.
>
>
|||Jane,
What is the version of you mmc.exe? What is the OS and SP level of your
workstation?
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:032389DE-4113-42A4-9DA0-B78F4864A746@.microsoft.com...
> Thanks for your help, but it doesn't work. Any ideas?
> Jane
> -- Dinesh T.K wrote: --
> Jane,
> Refer the steps 3 to 5 given in the 'workaround' section of this
article:
> 'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server
2000'
> http://support.microsoft.com/default.aspx?id=272453
> PS: I know that the title of the article doesnt concern you, but
those steps[vbcol=seagreen]
> might help.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane" <anonymous@.discussions.microsoft.com> wrote in message
> news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
2000.
> The problem is very strange. I suppose I am locked by the server.
Don't know[vbcol=seagreen]
> what to do now.
there
> isn't a senior member in our team, so your help turns to be very
important
> for me. I am looking forward to any ideas.
>
>

MMC Cannot open

who knows how to fix this:
MMC cannot open the file C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\Sql Server Enterprise Manager.MSC.
This may be because the file doesnt exist, is not an MMC console, or
was created by a later version of MMC. This may also be because
you do not have sufficient access rights to the file.
I have rebooted the server, and restarted my machine, uninstalled and reinst
alled SQL Server 7.0 Client. I still can't start SQL Server Enterprise Manag
er. Can anyone help?
Thanks in advance
JaneJane, once again, have you considered using SQL Server 2000 Enterprise
Manager? You seem to have both installed on your machine, and when you try
to launch 7.0 it is looking in \80\ and causing a conflict. I suggest
uninstalling SQL 7.0 client, reinstalling 2000 client, installing 2000 SP3a,
and using 2000 client tools.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:C0397850-DCCD-4AEE-9ADF-AAD21DC84737@.microsoft.com...
> who knows how to fix this:
> MMC cannot open the file C:\Program Files\Microsoft SQL
> Server\80\Tools\BINN\Sql Server Enterprise Manager.MSC.
> This may be because the file doesnt exist, is not an MMC console, or
> was created by a later version of MMC. This may also be because
> you do not have sufficient access rights to the file.
> I have rebooted the server, and restarted my machine, uninstalled and
reinstalled SQL Server 7.0 Client. I still can't start SQL Server Enterprise
Manager. Can anyone help?
> Thanks in advance
> Jane
>|||Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000. The
problem is very strange. I suppose I am locked by the server. Don't know wh
at to do now.
As I said, I am new to SQL Server, I am trying to explore it. But there isn'
t a senior member in our team, so your help turns to be very important for m
e. I am looking forward to any ideas.
Cheers
Jane|||Jane,
Refer the steps 3 to 5 given in the 'workaround' section of this article:
'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server 2000'
http://support.microsoft.com/default.aspx?id=272453
PS: I know that the title of the article doesnt concern you, but those steps
might help.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
> Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000.
The problem is very strange. I suppose I am locked by the server. Don't know
what to do now.
> As I said, I am new to SQL Server, I am trying to explore it. But there
isn't a senior member in our team, so your help turns to be very important
for me. I am looking forward to any ideas.
> Cheers
> Jane|||Thanks for your help, but it doesn't work. Any ideas?
Jane
-- Dinesh T.K wrote: --
Jane,
Refer the steps 3 to 5 given in the 'workaround' section of this article:
'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server 2000'
http://support.microsoft.com/default.aspx?id=272453
PS: I know that the title of the article doesnt concern you, but those steps
might help.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
> Hi, Aaron, Thanks for your reply. Actually I don't have SQL Server 2000.
The problem is very strange. I suppose I am locked by the server. Don't know
what to do now.
> As I said, I am new to SQL Server, I am trying to explore it. But there
isn't a senior member in our team, so your help turns to be very important
for me. I am looking forward to any ideas.
> Cheers
> Jane|||Jane,
May be EM is missing some DLLs .The relevant ones are
sqlns.dll,sqlmmc.dll,sqldmo.dll,dtsui.dll and sqllex.dll.Usually you can
find them in c:\mssql7\binn\.
Try re-registering them using regsvr32.exe.After each one, try opening up
EM.
If this too doesnt help, see if a reinstall of the relevant MDAC helps.
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:032389DE-4113-42A4-9DA0-B78F4864A746@.microsoft.com...
> Thanks for your help, but it doesn't work. Any ideas?
> Jane
> -- Dinesh T.K wrote: --
> Jane,
> Refer the steps 3 to 5 given in the 'workaround' section of this
article:
> 'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server
2000'
> http://support.microsoft.com/default.aspx?id=272453
> PS: I know that the title of the article doesnt concern you, but
those steps
> might help.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane" <anonymous@.discussions.microsoft.com> wrote in message
> news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
2000.[vbcol=seagreen]
> The problem is very strange. I suppose I am locked by the server.
Don't know
> what to do now.
there[vbcol=seagreen]
> isn't a senior member in our team, so your help turns to be very
important
> for me. I am looking forward to any ideas.
>
>|||Jane,
What is the version of you mmc.exe? What is the OS and SP level of your
workstation?
Andrew C. Madsen
Information Architect
Harley-Davidson Motor Company
"Jane" <anonymous@.discussions.microsoft.com> wrote in message
news:032389DE-4113-42A4-9DA0-B78F4864A746@.microsoft.com...
> Thanks for your help, but it doesn't work. Any ideas?
> Jane
> -- Dinesh T.K wrote: --
> Jane,
> Refer the steps 3 to 5 given in the 'workaround' section of this
article:
> 'PRB: Cannot Use SQL Server 7.0 Tools After You Remove SQL Server
2000'
> http://support.microsoft.com/default.aspx?id=272453
> PS: I know that the title of the article doesnt concern you, but
those steps
> might help.
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "Jane" <anonymous@.discussions.microsoft.com> wrote in message
> news:42525A24-E330-44F9-A037-F17141FB0156@.microsoft.com...
2000.[vbcol=seagreen]
> The problem is very strange. I suppose I am locked by the server.
Don't know
> what to do now.
there[vbcol=seagreen]
> isn't a senior member in our team, so your help turns to be very
important
> for me. I am looking forward to any ideas.
>
>

Missing What To Start SQLServer Agent in EM

Installed Office service pack and it 'messed' up the Enterprise Manager. Af
ter reinstalling the client tools and the sp3a service pack all worked but s
cheduled jobs. It turns out that the SQL Server Agent is not running. It d
oesn't automatically start
up but can be started from DOS whereby my jobs in turn can execute with no p
roblem.
Would like to know what the proper registry setting for SQLServerAgent under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\SQLServerAgent should
be for SQL Server 8.0.859 with service pack 3a as suspect that the problem m
ay be there.
Otherwise open to suggestions so that do not have to backup, uninstall, and
reinstall 10 database.....
Thanxs,
dmatta59The first thing to do here is go into the Control Panel -> Admin Tools ->
Services applet & see if the SQLAgent$[instance] service is configured t
o
auto-start. Your post doesn't indicated that you've done that, so make sure
the service's "Startup Type" property is set to "Automatic". If it still
doesn't start automatically, check the Windows Event Log to see what's
wrong.
Regards,
Greg Linwood
SQL Server MVP
"dmatta59" <anonymous@.discussions.microsoft.com> wrote in message
news:6F7A83AF-FE7A-46EF-8F44-50C94788109C@.microsoft.com...
> Installed Office service pack and it 'messed' up the Enterprise Manager.
After reinstalling the client tools and the sp3a service pack all worked but
scheduled jobs. It turns out that the SQL Server Agent is not running. It
doesn't automatically start up but can be started from DOS whereby my jobs
in turn can execute with no problem.
> Would like to know what the proper registry setting for SQLServerAgent
under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\SQLServerAgent
should be for SQL Server 8.0.859 with service pack 3a as suspect that the
problem may be there.
> Otherwise open to suggestions so that do not have to backup, uninstall,
and reinstall 10 database.....
> Thanxs,
> dmatta59|||The SqlServerAgent is set to automatic. There used to be an error 8344 Supe
rSocket Error but after the registers were cleaned and errors removed the e
rror no longer appears. When viewing the registry for SQLServerAgent there
was some mention in one of
the previous posts about a "dependancies" which is not present so would app
reciate what the registry would look like for MSSQLSERVER and SQLSERVERAGENT
.
Again it works fine if started from a dos command line but most inconvienent
not to have it start automatically or start from within the EM.
Any suggestions?
dmatta59|||Have resolved the problem. Used scm.exe to install the SQLServerAgent servi
ce using the instructions on the following article:
http://groups.google.com/groups?q=i...tngxa06&rnum=21
**Please note that the in this case the sqlagent -c -v was working from the
dos prompt and the jobs could run properly. The only problem was that the S
QLServerAgent was not automatically starting or couldn't be started within E
M.
Thank you,
dmatta59

Missing Join Predicate error

All,
We did an inplace upgrade of our "SQLServer 2000 SP3a" production server to
"SQLServer 2005 SP2 Enterprise Edition" on saturday. The system has 8 CPUs
and 4GB of RAM. This evening, the server crashed and I had to reboot the box.
I checked the eventvwr and this is what I get. I also found a stack dump in
the log. I checked the blackbox trace for any signs and I found "MIssing Join
Predicate" in the EventClass for one of the databases. This leads me to
believe that this is the reason why SQLServer crashed though we never
encountered this problem in the SQLServer 2000 installation before we
upgraded -- the application has been working fine without any problem over
the past several years. I could have trouble shooted this issue more but
unfortunately the text of the code that resulted in the "MIssing Join
Predicate" is empty in the Text column.
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17311
Date:1/14/2008
Time:5:59:11 PM
User:N/A
Computer:ENSQLP2
Description:
SQL Server is terminating because of fatal exception c0000005. This error
may be caused by an unhandled Win32 or C++ exception, or by an access
violation encountered during exception handling. Check the SQL error log for
any related stack dumps or messages. This exception forces SQL Server to
shutdown. To recover from this error, restart the server (unless SQLAgent is
configured to auto restart).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 9f 43 00 00 10 00 00 00 ?C.....
0008: 08 00 00 00 45 00 4e 00 ...E.N.
0010: 53 00 51 00 4c 00 50 00 S.Q.L.P.
0018: 32 00 00 00 00 00 00 00 2......
Has anyone encountered this problem before? I will start a user defined
trace and get to the core tomorrow. Neverthless, I was wondering if anyone
has encountered this issue before
Here is the stack dump. Note that at this point I also dont know which
query/SP caused the crash.
================================================== ===================
BugCheck Dump
================================================== ===================
This file is generated by Microsoft SQL Server
version 9.00.3042.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is HP - 2
Current time is 17:59:12 01/14/08.
8 Intel x86 level 15, 2833 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 1.
Memory
MemoryLoad = 51%
Total Physical = 4094 MB
Available Physical = 1986 MB
Total Page File = 10069 MB
Available Page File = 7980 MB
Total Virtual = 2047 MB
Available Virtual = 217 MB
**Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
***Stack Dump being sent to e:\MSSQL\MSSQL\LOG\SQLDump0005.txt
*
************************************************** *****************************
*
* BEGIN STACK DUMP:
* 01/14/08 17:59:12 spid 0
*
* ex_handle_except encountered exception C0000005 - Server terminating
*
*
* MODULE BASE END SIZE
* sqlservr 01000000 02C09FFF 01c0a000
* ntdll 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* MSVCR80 78130000 781CAFFF 0009b000
* msvcrt 77BA0000 77BF9FFF 0005a000
* MSVCP80 7C420000 7C4A6FFF 00087000
* ADVAPI32 77F50000 77FEBFFF 0009c000
* RPCRT4 77C50000 77CEEFFF 0009f000
* USER32 77380000 77411FFF 00092000
* GDI32 77C00000 77C48FFF 00049000
* CRYPT32 761B0000 76242FFF 00093000
* MSASN1 76190000 761A1FFF 00012000
* Secur32 76F50000 76F62FFF 00013000
* MSWSOCK 71B20000 71B60FFF 00041000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* USERENV 76920000 769E3FFF 000c4000
* opends60 333E0000 333E6FFF 00007000
* NETAPI32 71C40000 71C97FFF 00058000
* SHELL32 7C8D0000 7D0D3FFF 00804000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* comctl32 77420000 77522FFF 00103000
* psapi 76B70000 76B7AFFF 0000b000
* instapi 48060000 48069FFF 0000a000
* sqlevn70 4F610000 4F7B8FFF 001a9000
* SQLOS 344D0000 344D4FFF 00005000
* rsaenh 68000000 6802EFFF 0002f000
* AUTHZ 76C40000 76C53FFF 00014000
* MSCOREE 79000000 79044FFF 00045000
* ole32 77670000 777A3FFF 00134000
* msv1_0 76C90000 76CB6FFF 00027000
* iphlpapi 76CF0000 76D09FFF 0001a000
* kerberos 62810000 62867FFF 00058000
* cryptdll 766E0000 766EBFFF 0000c000
* schannel 76750000 76776FFF 00027000
* COMRES 77010000 770D5FFF 000c6000
* XOLEHLP 628D0000 628D5FFF 00006000
* MSDTCPRX 628E0000 62957FFF 00078000
* msvcp60 780C0000 78120FFF 00061000
* MTXCLU 62960000 62978FFF 00019000
* VERSION 77B90000 77B97FFF 00008000
* WSOCK32 71BB0000 71BB8FFF 00009000
* OLEAUT32 77D00000 77D8BFFF 0008c000
* CLUSAPI 62980000 62991FFF 00012000
* RESUTILS 629A0000 629B2FFF 00013000
* DNSAPI 76ED0000 76EFEFFF 0002f000
* winrnr 76F70000 76F76FFF 00007000
* WLDAP32 76F10000 76F3DFFF 0002e000
* rasadhlp 76F80000 76F87FFF 00008000
* security 62DF0000 62DF3FFF 00004000
* msfte 63750000 639A8FFF 00259000
* dbghelp 639B0000 63AC4FFF 00115000
* WINTRUST 76BB0000 76BDAFFF 0002b000
* imagehlp 76C10000 76C38FFF 00029000
* dssenh 68100000 68123FFF 00024000
* hnetcfg 63D20000 63D78FFF 00059000
* wshtcpip 71AE0000 71AE7FFF 00008000
* NTMARTA 77E00000 77E21FFF 00022000
* SAMLIB 63DC0000 63DCEFFF 0000f000
* ntdsapi 766F0000 76704FFF 00015000
* xpsp2res 63E50000 64114FFF 002c5000
* CLBCatQ 777B0000 77832FFF 00083000
* sqlncli 64120000 64343FFF 00224000
* COMCTL32 77530000 775C6FFF 00097000
* comdlg32 762B0000 762F9FFF 0004a000
* SQLNCLIR 007A0000 007D2FFF 00033000
* msftepxy 645D0000 645E4FFF 00015000
* EntApi 65E90000 65EA2FFF 00013000
* WININET 77210000 772B7FFF 000a8000
* xpsqlbot 66100000 66105FFF 00006000
* xpstar90 66120000 66168FFF 00049000
* SQLSCM90 66180000 66188FFF 00009000
* ODBC32 661A0000 661DCFFF 0003d000
* BatchParser90 661E0000 661FEFFF 0001f000
* ATL80 7C630000 7C64AFFF 0001b000
* odbcint 664D0000 664E6FFF 00017000
* xpstar90 664F0000 66515FFF 00026000
* xplog70 66520000 6652BFFF 0000c000
* xplog70 66540000 66542FFF 00003000
* odsole70 66550000 6655EFFF 0000f000
* SXS 66BD0000 66C8BFFF 000bc000
* oledb32 668E0000 66958FFF 00079000
* MSDART 64510000 64529FFF 0001a000
* OLEDB32R 64530000 64540FFF 00011000
* msdaora 66FF0000 67030FFF 00041000
* MSDATL3 66BA0000 66BB4FFF 00015000
* MSDAORAR 644F0000 644F3FFF 00004000
* oci 67040000 67096FFF 00057000
* MSVCR71 7C340000 7C395FFF 00056000
* OCIW32 670A0000 670F5FFF 00056000
* ORACLIENT10 67100000 67351FFF 00252000
* oracore10 67360000 67442FFF 000e3000
* oranls10 67450000 67513FFF 000c4000
* oraunls10 67520000 67537FFF 00018000
* orauts 66BC0000 66BC6FFF 00007000
* WINMM 76AA0000 76ACCFFF 0002d000
* oravsn10 67540000 67545FFF 00006000
* oracommon10 67550000 67641FFF 000f2000
* orageneric10 67650000 67BA6FFF 00557000
* orasnls10 67BB0000 67BD6FFF 00027000
* oraxml10 67BE0000 67D3FFFF 00160000
* MSVCIRT 67D40000 67D4FFFF 00010000
* oran10 67D50000 67E5CFFF 0010d000
* oranl10 67E60000 67E9CFFF 0003d000
* oranldap10 67EA0000 67EB6FFF 00017000
* orannzsbb10 67EC0000 67FC8FFF 00109000
* oraldapclnt10 68030000 68082FFF 00053000
* orancrypt10 67FD0000 67FEAFFF 0001b000
* oranro10 68090000 680DBFFF 0004c000
* oranhost10 67FF0000 67FF6FFF 00007000
* orancds10 680E0000 680E5FFF 00006000
* orantns10 680F0000 680F7FFF 00008000
* orapls10 68130000 68487FFF 00358000
* oraslax10 68490000 68498FFF 00009000
* oraplp10 684A0000 686A3FFF 00204000
* orahasgen10 686B0000 6873AFFF 0008b000
* oraocr10 68740000 687A9FFF 0006a000
* oraocrb10 687B0000 687EFFFF 00040000
* orantcp10 687F0000 687FFFFF 00010000
* orasql10 68800000 68899FFF 0009a000
* comsvcs 68B10000 68C48FFF 00139000
* activeds 76DF0000 76E22FFF 00033000
* adsldpc 76DC0000 76DE6FFF 00027000
* credui 76B80000 76BADFFF 0002e000
* ATL 76A80000 76A97FFF 00018000
* msadce 68DD0000 68E27FFF 00058000
* msadcer 68D70000 68D74FFF 00005000
* sqlmap90 6A090000 6A0ADFFF 0001e000
* MAPI32 6A0C0000 6A0DEFFF 0001f000
* sqlmap90 6A0E0000 6A0E5FFF 00006000
* MSMAPI32 6A0F0000 6A24BFFF 0015c000
* MAPIR 6A570000 6A62FFFF 000c0000
* mso 6AAC0000 6B67CFFF 00bbd000
* EMSABP32 6B690000 6B6D2FFF 00043000
* MPRAPI 76CD0000 76CE8FFF 00019000
* rtutils 76E30000 76E3BFFF 0000c000
* SETUPAPI 770E0000 771E9FFF 0010a000
* netman 77840000 77882FFF 00043000
* netshell 76300000 764C0FFF 001c1000
* RASAPI32 76E90000 76ECEFFF 0003f000
* rasman 76E40000 76E51FFF 00012000
* TAPI32 76E60000 76E8EFFF 0002f000
* WZCSAPI 6B820000 6B82CFFF 0000d000
* WZCSvc 77890000 77900FFF 00071000
* WMI 76CC0000 76CC4FFF 00005000
* DHCPCSVC 76D10000 76D2EFFF 0001f000
* WTSAPI32 76F00000 76F07FFF 00008000
* WINSTA 771F0000 77200FFF 00011000
* ESENT 6B830000 6B934FFF 00105000
* contab32 6C4E0000 6C4FEFFF 0001f000
* EMSMDB32 6C510000 6C5BEFFF 000af000
* encryption 6C930000 6C936FFF 00007000
* MSVBVM60 6C940000 6CA91FFF 00152000
* Dciph32 02C40000 02C4DFFF 0000e000
* dbghelp 69530000 69644FFF 00115000
*
* Edi: 6995E178: 6533D2F8 77F5E95E 00000000 6995E2C8 00000000
77FC2190
* Esi: 00000000:
* Eax: 6995E05C: 000042AC 00000000 00000000 77E55E02 00000000
0000000C
* Ebx: 0000003F:
* Ecx: 6995E6CC: 00000000 00010007 00000000 00460044 6533D2FC
6995E08C
* Edx: 0000003D:
* Eip: 77E55E02: 10C2C95E 90909000 A1649090 00000018 C334408B
891C428B
* Ebp: 6995E0AC: 6995E0F0 021A29C4 000042AC 00000000 00000000
00000000
* SegCs: 0000001B:
* EFlags: 00000246:
* Esp: 6995E058: 00000000 000042AC 00000000 00000000 77E55E02
00000000
* SegSs: 78130023: 00000000 00000000 00000000 00000000 00000000
00000000
*
************************************************** *****************************
*
* Short Stack Dump
77E55E02 Module(kernel32+00015E02)
021A29C4 Module(sqlservr+011A29C4)
021A6880 Module(sqlservr+011A6880)
021A642D Module(sqlservr+011A642D)
02414429 Module(sqlservr+01414429)
77E99F7A Module(kernel32+00059F7A)
78138B5E Module(MSVCR80+00008B5E)
781329C1 Module(MSVCR80+000029C1)
78132A36 Module(MSVCR80+00002A36)

Missing Join Predicate error

All,
We did an inplace upgrade of our "SQLServer 2000 SP3a" production server to
"SQLServer 2005 SP2 Enterprise Edition" on saturday. The system has 8 CPUs
and 4GB of RAM. This evening, the server crashed and I had to reboot the box.
I checked the eventvwr and this is what I get. I also found a stack dump in
the log. I checked the blackbox trace for any signs and I found "MIssing Join
Predicate" in the EventClass for one of the databases. This leads me to
believe that this is the reason why SQLServer crashed though we never
encountered this problem in the SQLServer 2000 installation before we
upgraded -- the application has been working fine without any problem over
the past several years. I could have trouble shooted this issue more but
unfortunately the text of the code that resulted in the "MIssing Join
Predicate" is empty in the Text column.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17311
Date: 1/14/2008
Time: 5:59:11 PM
User: N/A
Computer: ENSQLP2
Description:
SQL Server is terminating because of fatal exception c0000005. This error
may be caused by an unhandled Win32 or C++ exception, or by an access
violation encountered during exception handling. Check the SQL error log for
any related stack dumps or messages. This exception forces SQL Server to
shutdown. To recover from this error, restart the server (unless SQLAgent is
configured to auto restart).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 9f 43 00 00 10 00 00 00 Â?C.....
0008: 08 00 00 00 45 00 4e 00 ...E.N.
0010: 53 00 51 00 4c 00 50 00 S.Q.L.P.
0018: 32 00 00 00 00 00 00 00 2......
Has anyone encountered this problem before? I will start a user defined
trace and get to the core tomorrow. Neverthless, I was wondering if anyone
has encountered this issue beforeHere is the stack dump. Note that at this point I also dont know which
query/SP caused the crash.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.3042.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is HP - 2
Current time is 17:59:12 01/14/08.
8 Intel x86 level 15, 2833 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 1.
Memory
MemoryLoad = 51%
Total Physical = 4094 MB
Available Physical = 1986 MB
Total Page File = 10069 MB
Available Page File = 7980 MB
Total Virtual = 2047 MB
Available Virtual = 217 MB
**Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
***Stack Dump being sent to e:\MSSQL\MSSQL\LOG\SQLDump0005.txt
*
*******************************************************************************
*
* BEGIN STACK DUMP:
* 01/14/08 17:59:12 spid 0
*
* ex_handle_except encountered exception C0000005 - Server terminating
*
*
* MODULE BASE END SIZE
* sqlservr 01000000 02C09FFF 01c0a000
* ntdll 7C800000 7C8BFFFF 000c0000
* kernel32 77E40000 77F41FFF 00102000
* MSVCR80 78130000 781CAFFF 0009b000
* msvcrt 77BA0000 77BF9FFF 0005a000
* MSVCP80 7C420000 7C4A6FFF 00087000
* ADVAPI32 77F50000 77FEBFFF 0009c000
* RPCRT4 77C50000 77CEEFFF 0009f000
* USER32 77380000 77411FFF 00092000
* GDI32 77C00000 77C48FFF 00049000
* CRYPT32 761B0000 76242FFF 00093000
* MSASN1 76190000 761A1FFF 00012000
* Secur32 76F50000 76F62FFF 00013000
* MSWSOCK 71B20000 71B60FFF 00041000
* WS2_32 71C00000 71C16FFF 00017000
* WS2HELP 71BF0000 71BF7FFF 00008000
* USERENV 76920000 769E3FFF 000c4000
* opends60 333E0000 333E6FFF 00007000
* NETAPI32 71C40000 71C97FFF 00058000
* SHELL32 7C8D0000 7D0D3FFF 00804000
* SHLWAPI 77DA0000 77DF1FFF 00052000
* comctl32 77420000 77522FFF 00103000
* psapi 76B70000 76B7AFFF 0000b000
* instapi 48060000 48069FFF 0000a000
* sqlevn70 4F610000 4F7B8FFF 001a9000
* SQLOS 344D0000 344D4FFF 00005000
* rsaenh 68000000 6802EFFF 0002f000
* AUTHZ 76C40000 76C53FFF 00014000
* MSCOREE 79000000 79044FFF 00045000
* ole32 77670000 777A3FFF 00134000
* msv1_0 76C90000 76CB6FFF 00027000
* iphlpapi 76CF0000 76D09FFF 0001a000
* kerberos 62810000 62867FFF 00058000
* cryptdll 766E0000 766EBFFF 0000c000
* schannel 76750000 76776FFF 00027000
* COMRES 77010000 770D5FFF 000c6000
* XOLEHLP 628D0000 628D5FFF 00006000
* MSDTCPRX 628E0000 62957FFF 00078000
* msvcp60 780C0000 78120FFF 00061000
* MTXCLU 62960000 62978FFF 00019000
* VERSION 77B90000 77B97FFF 00008000
* WSOCK32 71BB0000 71BB8FFF 00009000
* OLEAUT32 77D00000 77D8BFFF 0008c000
* CLUSAPI 62980000 62991FFF 00012000
* RESUTILS 629A0000 629B2FFF 00013000
* DNSAPI 76ED0000 76EFEFFF 0002f000
* winrnr 76F70000 76F76FFF 00007000
* WLDAP32 76F10000 76F3DFFF 0002e000
* rasadhlp 76F80000 76F87FFF 00008000
* security 62DF0000 62DF3FFF 00004000
* msfte 63750000 639A8FFF 00259000
* dbghelp 639B0000 63AC4FFF 00115000
* WINTRUST 76BB0000 76BDAFFF 0002b000
* imagehlp 76C10000 76C38FFF 00029000
* dssenh 68100000 68123FFF 00024000
* hnetcfg 63D20000 63D78FFF 00059000
* wshtcpip 71AE0000 71AE7FFF 00008000
* NTMARTA 77E00000 77E21FFF 00022000
* SAMLIB 63DC0000 63DCEFFF 0000f000
* ntdsapi 766F0000 76704FFF 00015000
* xpsp2res 63E50000 64114FFF 002c5000
* CLBCatQ 777B0000 77832FFF 00083000
* sqlncli 64120000 64343FFF 00224000
* COMCTL32 77530000 775C6FFF 00097000
* comdlg32 762B0000 762F9FFF 0004a000
* SQLNCLIR 007A0000 007D2FFF 00033000
* msftepxy 645D0000 645E4FFF 00015000
* EntApi 65E90000 65EA2FFF 00013000
* WININET 77210000 772B7FFF 000a8000
* xpsqlbot 66100000 66105FFF 00006000
* xpstar90 66120000 66168FFF 00049000
* SQLSCM90 66180000 66188FFF 00009000
* ODBC32 661A0000 661DCFFF 0003d000
* BatchParser90 661E0000 661FEFFF 0001f000
* ATL80 7C630000 7C64AFFF 0001b000
* odbcint 664D0000 664E6FFF 00017000
* xpstar90 664F0000 66515FFF 00026000
* xplog70 66520000 6652BFFF 0000c000
* xplog70 66540000 66542FFF 00003000
* odsole70 66550000 6655EFFF 0000f000
* SXS 66BD0000 66C8BFFF 000bc000
* oledb32 668E0000 66958FFF 00079000
* MSDART 64510000 64529FFF 0001a000
* OLEDB32R 64530000 64540FFF 00011000
* msdaora 66FF0000 67030FFF 00041000
* MSDATL3 66BA0000 66BB4FFF 00015000
* MSDAORAR 644F0000 644F3FFF 00004000
* oci 67040000 67096FFF 00057000
* MSVCR71 7C340000 7C395FFF 00056000
* OCIW32 670A0000 670F5FFF 00056000
* ORACLIENT10 67100000 67351FFF 00252000
* oracore10 67360000 67442FFF 000e3000
* oranls10 67450000 67513FFF 000c4000
* oraunls10 67520000 67537FFF 00018000
* orauts 66BC0000 66BC6FFF 00007000
* WINMM 76AA0000 76ACCFFF 0002d000
* oravsn10 67540000 67545FFF 00006000
* oracommon10 67550000 67641FFF 000f2000
* orageneric10 67650000 67BA6FFF 00557000
* orasnls10 67BB0000 67BD6FFF 00027000
* oraxml10 67BE0000 67D3FFFF 00160000
* MSVCIRT 67D40000 67D4FFFF 00010000
* oran10 67D50000 67E5CFFF 0010d000
* oranl10 67E60000 67E9CFFF 0003d000
* oranldap10 67EA0000 67EB6FFF 00017000
* orannzsbb10 67EC0000 67FC8FFF 00109000
* oraldapclnt10 68030000 68082FFF 00053000
* orancrypt10 67FD0000 67FEAFFF 0001b000
* oranro10 68090000 680DBFFF 0004c000
* oranhost10 67FF0000 67FF6FFF 00007000
* orancds10 680E0000 680E5FFF 00006000
* orantns10 680F0000 680F7FFF 00008000
* orapls10 68130000 68487FFF 00358000
* oraslax10 68490000 68498FFF 00009000
* oraplp10 684A0000 686A3FFF 00204000
* orahasgen10 686B0000 6873AFFF 0008b000
* oraocr10 68740000 687A9FFF 0006a000
* oraocrb10 687B0000 687EFFFF 00040000
* orantcp10 687F0000 687FFFFF 00010000
* orasql10 68800000 68899FFF 0009a000
* comsvcs 68B10000 68C48FFF 00139000
* activeds 76DF0000 76E22FFF 00033000
* adsldpc 76DC0000 76DE6FFF 00027000
* credui 76B80000 76BADFFF 0002e000
* ATL 76A80000 76A97FFF 00018000
* msadce 68DD0000 68E27FFF 00058000
* msadcer 68D70000 68D74FFF 00005000
* sqlmap90 6A090000 6A0ADFFF 0001e000
* MAPI32 6A0C0000 6A0DEFFF 0001f000
* sqlmap90 6A0E0000 6A0E5FFF 00006000
* MSMAPI32 6A0F0000 6A24BFFF 0015c000
* MAPIR 6A570000 6A62FFFF 000c0000
* mso 6AAC0000 6B67CFFF 00bbd000
* EMSABP32 6B690000 6B6D2FFF 00043000
* MPRAPI 76CD0000 76CE8FFF 00019000
* rtutils 76E30000 76E3BFFF 0000c000
* SETUPAPI 770E0000 771E9FFF 0010a000
* netman 77840000 77882FFF 00043000
* netshell 76300000 764C0FFF 001c1000
* RASAPI32 76E90000 76ECEFFF 0003f000
* rasman 76E40000 76E51FFF 00012000
* TAPI32 76E60000 76E8EFFF 0002f000
* WZCSAPI 6B820000 6B82CFFF 0000d000
* WZCSvc 77890000 77900FFF 00071000
* WMI 76CC0000 76CC4FFF 00005000
* DHCPCSVC 76D10000 76D2EFFF 0001f000
* WTSAPI32 76F00000 76F07FFF 00008000
* WINSTA 771F0000 77200FFF 00011000
* ESENT 6B830000 6B934FFF 00105000
* contab32 6C4E0000 6C4FEFFF 0001f000
* EMSMDB32 6C510000 6C5BEFFF 000af000
* encryption 6C930000 6C936FFF 00007000
* MSVBVM60 6C940000 6CA91FFF 00152000
* Dciph32 02C40000 02C4DFFF 0000e000
* dbghelp 69530000 69644FFF 00115000
*
* Edi: 6995E178: 6533D2F8 77F5E95E 00000000 6995E2C8 00000000
77FC2190
* Esi: 00000000:
* Eax: 6995E05C: 000042AC 00000000 00000000 77E55E02 00000000
0000000C
* Ebx: 0000003F:
* Ecx: 6995E6CC: 00000000 00010007 00000000 00460044 6533D2FC
6995E08C
* Edx: 0000003D:
* Eip: 77E55E02: 10C2C95E 90909000 A1649090 00000018 C334408B
891C428B
* Ebp: 6995E0AC: 6995E0F0 021A29C4 000042AC 00000000 00000000
00000000
* SegCs: 0000001B:
* EFlags: 00000246:
* Esp: 6995E058: 00000000 000042AC 00000000 00000000 77E55E02
00000000
* SegSs: 78130023: 00000000 00000000 00000000 00000000 00000000
00000000
*
*******************************************************************************
*
----
* Short Stack Dump
77E55E02 Module(kernel32+00015E02)
021A29C4 Module(sqlservr+011A29C4)
021A6880 Module(sqlservr+011A6880)
021A642D Module(sqlservr+011A642D)
02414429 Module(sqlservr+01414429)
77E99F7A Module(kernel32+00059F7A)
78138B5E Module(MSVCR80+00008B5E)
781329C1 Module(MSVCR80+000029C1)
78132A36 Module(MSVCR80+00002A36)

Missing Format() - Function

Hi folks,
i have to translate SQL-Statements from Access 2000 to SQL
Server 2000. There was a lot of Access-Functions used
(mid, str, iif ...) and i convert them to SQL-Server
Syntax, but i dont found a way to simulate the results of
the Format-Function with was used for numeric data
as "##0.##" or "##0 %" and so on ...
What is the best way to substitute the FORMAT() function
at SQL Server?
Thanks for any help.
Niels
On Fri, 15 Apr 2005 01:33:00 -0700, nieurig wrote:

>Hi folks,
>i have to translate SQL-Statements from Access 2000 to SQL
>Server 2000. There was a lot of Access-Functions used
>(mid, str, iif ...) and i convert them to SQL-Server
>Syntax, but i dont found a way to simulate the results of
>the Format-Function with was used for numeric data
>as "##0.##" or "##0 %" and so on ...
>What is the best way to substitute the FORMAT() function
>at SQL Server?
>Thanks for any help.
>Niels
Hi Niels,
The best way is to return unformatted data to the client and let the
client handle the formatting. Formatting is not a task that the server
is ideally suited for.
If you must do it at the server, then start by looking into functions
such as CONVERT, CAST and STR. If they don't do what you need, then post
some examples of unformatted data and how you want it to look, so that I
(and others) can look into it and try to come up with something.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)
|||good morning hugo,
thanks for your comment.

>The best way is to return unformatted data to the client
and let the
>client handle the formatting. Formatting is not a task
that the server
>is ideally suited for.
Well i have to format the results, because the code of the
given application was lost and i translate the sql-
statements coming from a textfile.

>If you must do it at the server, then start by looking
into functions
>such as CONVERT, CAST and STR. If they don't do what you
need,
I use them for formating datetime values. It works well
but at numeric data the results a not good. therefore i
start to write a serverside function. I will post the code
if it was ready.
Niels
|||On Sat, 16 Apr 2005 00:30:57 -0700, nieurig wrote:

>good morning hugo,
>thanks for your comment.
>and let the
>that the server
>Well i have to format the results, because the code of the
>given application was lost and i translate the sql-
>statements coming from a textfile.
Hi Niels,
I might have misunderstood you. I thought you wanted to find a way to
control the format used for outputting numeric values from SQL Server,
but now I'm starting to think that you need to do the reverse: read in a
file with formatted results and make sure that they are converted to the
correct numeric values by SQL Server.
But maybe I am still misunderstanding you?

>into functions
>need,
>I use them for formating datetime values. It works well
>but at numeric data the results a not good. therefore i
>start to write a serverside function. I will post the code
>if it was ready.
Yes, you can do that. Or you can post some examples of typical data in
input / output pairs, to help me understand what exactly you need to get
done. I can only try to help if I know what you're trying to achieve,
and frankly, I don't know right now. Since I don't know what Access'
FORMAT() function does, you'll need to teach me (by example) - then I
can try to find a way to mimic this in SQL Server.
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)