Hello,
My 1st attempt to install .Net framework, MSDE, my application and the databases during setup (using the MSDE deployment toolkit RC) works fine on windows xp. Now when I try to do the same for windows 98 SE machine, I am able to install .Net framweork an
d MSDE, but after that during the installation I get the following error message:
"An exception occured in the OnAfterInstall event handler of DBInstaller.CustomInstaller --> Unable to access service: Operating system does not support controlling a Windows service. A service can only be controlled on Windows NT, Windows 2000, or lat
er."
It's clear that when the setup tries to start the service to create the database etc it fails. Is this a known issue. I researched on web but couldn't find anything. Any ideas.
Thanks
dev
Any ideas..
Friday, March 30, 2012
MSDE Tookit thinks MSDE is not installed when it is.
I have multiple applications that will use the same named instance of MSDE. When I try to setup my second application using the MSDE Deployment addin it thinks that MSDE needs to be installed again. According to the flowchart it should bypass this and
just install my appliation. Any suggestions as to why my setup insists in needs to install another instance? My instance name is the same for all applications.
Thanks,
Bill
Bill in one of the previous messages someone from Microsoft mentioned that it is a known bug in the beta version of the toolkit. Hopefully it will be fixed.
goodluck
dev
|||Thanks for the info. Does anyone know when the full release will be out?
sql
just install my appliation. Any suggestions as to why my setup insists in needs to install another instance? My instance name is the same for all applications.
Thanks,
Bill
Bill in one of the previous messages someone from Microsoft mentioned that it is a known bug in the beta version of the toolkit. Hopefully it will be fixed.
goodluck
dev
|||Thanks for the info. Does anyone know when the full release will be out?
sql
MSDE to SQL2000
I would like to know if it's possible to transfer a database from MSDE to SQ
L 2000 with the use of sp_detach_db from MSDE and sp_attach_db tp SQL2000Yep. Just handle orphaned users afterwards. sp_change_users_logins or
http://dbmaint.com/SyncSqlLogins.asp.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:C3EE7F95-750A-4559-AC34-3D1514DA5919@.microsoft.com...
> I would like to know if it's possible to transfer a database from MSDE to
SQL 2000 with the use of sp_detach_db from MSDE and sp_attach_db tp SQL2000
L 2000 with the use of sp_detach_db from MSDE and sp_attach_db tp SQL2000Yep. Just handle orphaned users afterwards. sp_change_users_logins or
http://dbmaint.com/SyncSqlLogins.asp.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:C3EE7F95-750A-4559-AC34-3D1514DA5919@.microsoft.com...
> I would like to know if it's possible to transfer a database from MSDE to
SQL 2000 with the use of sp_detach_db from MSDE and sp_attach_db tp SQL2000
MSDE to SQL2000
I would like to know if it's possible to transfer a database from MSDE to SQL 2000 with the use of sp_detach_db from MSDE and sp_attach_db tp SQL2000Yep. Just handle orphaned users afterwards. sp_change_users_logins or
http://dbmaint.com/SyncSqlLogins.asp.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:C3EE7F95-750A-4559-AC34-3D1514DA5919@.microsoft.com...
> I would like to know if it's possible to transfer a database from MSDE to
SQL 2000 with the use of sp_detach_db from MSDE and sp_attach_db tp SQL2000
http://dbmaint.com/SyncSqlLogins.asp.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:C3EE7F95-750A-4559-AC34-3D1514DA5919@.microsoft.com...
> I would like to know if it's possible to transfer a database from MSDE to
SQL 2000 with the use of sp_detach_db from MSDE and sp_attach_db tp SQL2000
MSDE to SQL Server Express
Hi - I have an MSDE database running on my server - I'd like to port my asp.net 1.1 app to asp.net2, and make use of SQL 2005 Express.
How do I transfer my data from an MSDE database to SQL Server Express, keeping intact all of my unique ID fields, indexes, and SPs (I don't have any functions or views)
Thanks for any help,
Mark
Your best bet is either to "detach" it on the MSDE side, and "attach" it or "restore from backup" on the SQL 2005 side, or use DTS (data transformation services).
|||Hi - it's just SQL Server 2005 Express I have available, so no management tools are there to allow me to 'restore from backup' - I'm not sure it supports DTS either.
Has anyone else been able to do this?
Thanks, Mark|||
Even with SQL Express you should have the ability to detach the database. You need the Management studio installed to work with the Express server engine though. You can download it here.
http://www.microsoft.com/downloads/details.aspx?familyid=82afbd59-57a4-455e-a2d6-1d4c98d40f6e&displaylang=en
|||You don't have to detach from SQL Express if you are using a file based database (You are if you use the AttachDB attribute in your connect string). Just stop whatever application that uses it, and copy the mdb/ldb files to SQL Sever 2005 and attach.MSDE to SQL Server 2005 Express
Howdy,
My company is setting up a new dedicated hosting server and we're debating
using the new SQL 2005 verse the MSDE. I'm not familiar with the new
version, so I have one big question:: Outside of the connection string, will
any syntax in my existing ASP.NET script/stored procs have to change to
support SQL 2005? Is the migration process painless?
I've searched MSDN but really can't find what I'm looking for.
Thanks,
David Lozzi
Web Applications Developer
dlozzi@.(remove-this)delphi-ts.comHello David,
> Outside of the
> connection string, will any syntax in my existing ASP.NET
> script/stored procs have to change to support SQL 2005?
Without specifics, its hard to say precisely. Some things change some, a
few a lot, most hardly at all. There's an upgrade advisor tool on the distri
bution
media and here [0] that I'd recommend starting with. It should catch a major
ity
of the changes needed with a minimum of effort.
> Is the
> migration process painless?
Again, that depends on what you've done in the past. I suspect not, but the
upgrade advisor will help you know more for sure.
[0]: http://www.microsoft.com/downloads/...&displaylang=en
Thank you,
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/
My company is setting up a new dedicated hosting server and we're debating
using the new SQL 2005 verse the MSDE. I'm not familiar with the new
version, so I have one big question:: Outside of the connection string, will
any syntax in my existing ASP.NET script/stored procs have to change to
support SQL 2005? Is the migration process painless?
I've searched MSDN but really can't find what I'm looking for.
Thanks,
David Lozzi
Web Applications Developer
dlozzi@.(remove-this)delphi-ts.comHello David,
> Outside of the
> connection string, will any syntax in my existing ASP.NET
> script/stored procs have to change to support SQL 2005?
Without specifics, its hard to say precisely. Some things change some, a
few a lot, most hardly at all. There's an upgrade advisor tool on the distri
bution
media and here [0] that I'd recommend starting with. It should catch a major
ity
of the changes needed with a minimum of effort.
> Is the
> migration process painless?
Again, that depends on what you've done in the past. I suspect not, but the
upgrade advisor will help you know more for sure.
[0]: http://www.microsoft.com/downloads/...&displaylang=en
Thank you,
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/
MSDE to SQL Server 2000 connection drops on XP Pro
Using MSDE 2000 SP3
Sql Server 2000 SP3
Win XP Pro SP1
Microsoft.Jet.OLEDB.4.0
We have recently upgraded field laptops from Windows 2000 to XP Pro. One of our applications which was developed with Visual C++ 6.0 and using MSDE will just drop it's connection to our consolidated Sql Server 2000. This works on Windows 2000 machines.
I have ran the profiler, monitored Sql Processes for locks, checked Event logs and I am unable to find any type of error. Our sync process just drops off. I am uncertain if it is MSDE, Sql Server or XP.
I even set the application's compatiability settings to Windows 2000 but still same result. I am uncertain as to how to do anymore troubleshooting.
Any ideas would be much appreciated.
Thanks,
Vannie Keever
SQL Server (including the MSDE edition) cannot close a connection by itself
except when shutting down. The client, the OS, or the network has to tell
SQL Server to drop the connection. Try a netmon trace to get more details.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
sql
Sql Server 2000 SP3
Win XP Pro SP1
Microsoft.Jet.OLEDB.4.0
We have recently upgraded field laptops from Windows 2000 to XP Pro. One of our applications which was developed with Visual C++ 6.0 and using MSDE will just drop it's connection to our consolidated Sql Server 2000. This works on Windows 2000 machines.
I have ran the profiler, monitored Sql Processes for locks, checked Event logs and I am unable to find any type of error. Our sync process just drops off. I am uncertain if it is MSDE, Sql Server or XP.
I even set the application's compatiability settings to Windows 2000 but still same result. I am uncertain as to how to do anymore troubleshooting.
Any ideas would be much appreciated.
Thanks,
Vannie Keever
SQL Server (including the MSDE edition) cannot close a connection by itself
except when shutting down. The client, the OS, or the network has to tell
SQL Server to drop the connection. Try a netmon trace to get more details.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
sql
MSDE to SQL Server
HI
Is it possible to upgrade SQL 2000 developer edition to SQL Serevr standered
edition
if so, how and what is the easist option
Thanks
bAccording to BOL, you can upgrade Developer Edition on SQL Server 2000 to
Enterprise Edition on SQL Server 2000/2005.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Is it possible to upgrade SQL 2000 developer edition to SQL Serevr standered
edition
if so, how and what is the easist option
Thanks
bAccording to BOL, you can upgrade Developer Edition on SQL Server 2000 to
Enterprise Edition on SQL Server 2000/2005.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
MSDE to SQL Server
HI
Is it possible to upgrade SQL 2000 developer edition to SQL Serevr standered
edition
if so, how and what is the easist option
Thanks
bAccording to BOL, you can upgrade Developer Edition on SQL Server 2000 to
Enterprise Edition on SQL Server 2000/2005.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Is it possible to upgrade SQL 2000 developer edition to SQL Serevr standered
edition
if so, how and what is the easist option
Thanks
bAccording to BOL, you can upgrade Developer Edition on SQL Server 2000 to
Enterprise Edition on SQL Server 2000/2005.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
MSDE to SQL 2000
What's the best way to get the data from the MSDE server
to the SQL 2000 server?
I've tried backing up and restoring from the SQL 2000
server, but I get "consistency errors". I ran DBCC
CHECKDB and MSDE DB was clean.
Then I tried to import the tables using EM, but am
getting errors.
Thanks,
DonDon wrote:
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
I assume that "using EM" means creating and executing DTS data import/export
package using the wizard. What are the errors you get?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||I guess you are trying to take across the system databases too... which is
why you are probably getting errors. you should only try to bring across the
user dbs in this scenario.
detach and reattach the dbs to the new server.
see also http://www.support.microsoft.com/?id=314546
Br,
Mark.
"Don" <ddachner@.hotmail.com> wrote in message
news:241601c3ffeb$03baff50$a601280a@.phx.gbl...
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
> Thanks,
> Don
>
to the SQL 2000 server?
I've tried backing up and restoring from the SQL 2000
server, but I get "consistency errors". I ran DBCC
CHECKDB and MSDE DB was clean.
Then I tried to import the tables using EM, but am
getting errors.
Thanks,
DonDon wrote:
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
I assume that "using EM" means creating and executing DTS data import/export
package using the wizard. What are the errors you get?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||I guess you are trying to take across the system databases too... which is
why you are probably getting errors. you should only try to bring across the
user dbs in this scenario.
detach and reattach the dbs to the new server.
see also http://www.support.microsoft.com/?id=314546
Br,
Mark.
"Don" <ddachner@.hotmail.com> wrote in message
news:241601c3ffeb$03baff50$a601280a@.phx.gbl...
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
> Thanks,
> Don
>
MSDE to SQL 2000
What's the best way to get the data from the MSDE server
to the SQL 2000 server?
I've tried backing up and restoring from the SQL 2000
server, but I get "consistency errors". I ran DBCC
CHECKDB and MSDE DB was clean.
Then I tried to import the tables using EM, but am
getting errors.
Thanks,
DonDon wrote:
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
I assume that "using EM" means creating and executing DTS data import/export
package using the wizard. What are the errors you get?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||I guess you are trying to take across the system databases too... which is
why you are probably getting errors. you should only try to bring across the
user dbs in this scenario.
detach and reattach the dbs to the new server.
see also http://www.support.microsoft.com/?id=314546
Br,
Mark.
"Don" <ddachner@.hotmail.com> wrote in message
news:241601c3ffeb$03baff50$a601280a@.phx.gbl...
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
> Thanks,
> Don
>
to the SQL 2000 server?
I've tried backing up and restoring from the SQL 2000
server, but I get "consistency errors". I ran DBCC
CHECKDB and MSDE DB was clean.
Then I tried to import the tables using EM, but am
getting errors.
Thanks,
DonDon wrote:
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
I assume that "using EM" means creating and executing DTS data import/export
package using the wizard. What are the errors you get?
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||I guess you are trying to take across the system databases too... which is
why you are probably getting errors. you should only try to bring across the
user dbs in this scenario.
detach and reattach the dbs to the new server.
see also http://www.support.microsoft.com/?id=314546
Br,
Mark.
"Don" <ddachner@.hotmail.com> wrote in message
news:241601c3ffeb$03baff50$a601280a@.phx.gbl...
> What's the best way to get the data from the MSDE server
> to the SQL 2000 server?
> I've tried backing up and restoring from the SQL 2000
> server, but I get "consistency errors". I ran DBCC
> CHECKDB and MSDE DB was clean.
> Then I tried to import the tables using EM, but am
> getting errors.
> Thanks,
> Don
>
MSDE to SQL
When scaling a system's back end from MSDE to the enterprise version of SQL what types of issues or concerns would you watch for?
Thanks
I am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/pr...o/overview.asp
Greg Jackson
PDX, Oregon
|||Miles,
MSDE IS SQL Server... You should have no problems at all...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks
sql
Thanks
I am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/pr...o/overview.asp
Greg Jackson
PDX, Oregon
|||Miles,
MSDE IS SQL Server... You should have no problems at all...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks
sql
MSDE to SQL
When scaling a system's back end from MSDE to the enterprise version of SQL
what types of issues or concerns would you watch for?
ThanksI am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/p...fo/overview.asp
Greg Jackson
PDX, Oregon|||Miles,
MSDE IS SQL Server... You should have no problems at all...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks
what types of issues or concerns would you watch for?
ThanksI am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/p...fo/overview.asp
Greg Jackson
PDX, Oregon|||Miles,
MSDE IS SQL Server... You should have no problems at all...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks
MSDE to SQL
When scaling a system's back end from MSDE to the enterprise version of SQL what types of issues or concerns would you watch for?
ThanksI am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/productinfo/overview.asp
Greg Jackson
PDX, Oregon|||i have a MS Windows 2003 Enterprise Edition but i don't have PDC installed so i don't have a domain in the LAN, i installed SQL Server 2000 on this server, but the clients ( MSDE 2000 ) can not se the SQL server.
My cuestion is , i have to install a pdc and then mount SQL server , and add the clients to the domain
"Jaxon" wrote:
> I am sure there are tons of white papers on this, but I dont suspect that
> you'll experience any huge hurdles.
> MSDE is essentially a throttled down version of the SQL Server Engine.
> "Because it is fully compatible with other editions of SQL Server,
> developers can easily target both SQL Server and MSDE 2000 with the same
> core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
> Server if an application grows beyond the storage and scalability limits of
> MSDE 2000."
>
> http://www.microsoft.com/sql/msde/productinfo/overview.asp
>
>
> Greg Jackson
> PDX, Oregon
>
>|||MSDE doesn't have network access enabled by default. Enable using svrnetcn.exe.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Visual FoxPro programmer" <VisualFoxProprogrammer@.discussions.microsoft.com> wrote in message
news:927CFF5D-751E-4040-AF0D-B3896E64D68C@.microsoft.com...
> i have a MS Windows 2003 Enterprise Edition but i don't have PDC installed so i don't have a
domain in the LAN, i installed SQL Server 2000 on this server, but the clients ( MSDE 2000 ) can not
se the SQL server.
> My cuestion is , i have to install a pdc and then mount SQL server , and add the clients to the
domain
>
> "Jaxon" wrote:
> > I am sure there are tons of white papers on this, but I dont suspect that
> > you'll experience any huge hurdles.
> >
> > MSDE is essentially a throttled down version of the SQL Server Engine.
> >
> > "Because it is fully compatible with other editions of SQL Server,
> > developers can easily target both SQL Server and MSDE 2000 with the same
> > core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
> > Server if an application grows beyond the storage and scalability limits of
> > MSDE 2000."
> >
> >
> > http://www.microsoft.com/sql/msde/productinfo/overview.asp
> >
> >
> >
> >
> > Greg Jackson
> > PDX, Oregon
> >
> >
> >|||Miles,
MSDE IS SQL Server... You should have no problems at all...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks
ThanksI am sure there are tons of white papers on this, but I dont suspect that
you'll experience any huge hurdles.
MSDE is essentially a throttled down version of the SQL Server Engine.
"Because it is fully compatible with other editions of SQL Server,
developers can easily target both SQL Server and MSDE 2000 with the same
core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
Server if an application grows beyond the storage and scalability limits of
MSDE 2000."
http://www.microsoft.com/sql/msde/productinfo/overview.asp
Greg Jackson
PDX, Oregon|||i have a MS Windows 2003 Enterprise Edition but i don't have PDC installed so i don't have a domain in the LAN, i installed SQL Server 2000 on this server, but the clients ( MSDE 2000 ) can not se the SQL server.
My cuestion is , i have to install a pdc and then mount SQL server , and add the clients to the domain
"Jaxon" wrote:
> I am sure there are tons of white papers on this, but I dont suspect that
> you'll experience any huge hurdles.
> MSDE is essentially a throttled down version of the SQL Server Engine.
> "Because it is fully compatible with other editions of SQL Server,
> developers can easily target both SQL Server and MSDE 2000 with the same
> core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
> Server if an application grows beyond the storage and scalability limits of
> MSDE 2000."
>
> http://www.microsoft.com/sql/msde/productinfo/overview.asp
>
>
> Greg Jackson
> PDX, Oregon
>
>|||MSDE doesn't have network access enabled by default. Enable using svrnetcn.exe.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Visual FoxPro programmer" <VisualFoxProprogrammer@.discussions.microsoft.com> wrote in message
news:927CFF5D-751E-4040-AF0D-B3896E64D68C@.microsoft.com...
> i have a MS Windows 2003 Enterprise Edition but i don't have PDC installed so i don't have a
domain in the LAN, i installed SQL Server 2000 on this server, but the clients ( MSDE 2000 ) can not
se the SQL server.
> My cuestion is , i have to install a pdc and then mount SQL server , and add the clients to the
domain
>
> "Jaxon" wrote:
> > I am sure there are tons of white papers on this, but I dont suspect that
> > you'll experience any huge hurdles.
> >
> > MSDE is essentially a throttled down version of the SQL Server Engine.
> >
> > "Because it is fully compatible with other editions of SQL Server,
> > developers can easily target both SQL Server and MSDE 2000 with the same
> > core code base. This provides a seamless upgrade path from MSDE 2000 to SQL
> > Server if an application grows beyond the storage and scalability limits of
> > MSDE 2000."
> >
> >
> > http://www.microsoft.com/sql/msde/productinfo/overview.asp
> >
> >
> >
> >
> > Greg Jackson
> > PDX, Oregon
> >
> >
> >|||Miles,
MSDE IS SQL Server... You should have no problems at all...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Niles" <Niles@.discussions.microsoft.com> wrote in message
news:5A4CD4C1-9923-436B-B711-C3F702A505DB@.microsoft.com...
> When scaling a system's back end from MSDE to the enterprise version of
SQL what types of issues or concerns would you watch for?
> Thanks
MSDE to MSDE replication with T-SQL/sp?
How can we replicate data in one MSDE to the other MSDE without having to
pay for MSSQL2000 full version to use the sql enterprise manager?
It seems that Enterprise Manager or SQL-DMO based programs rely on
system-provided stored procedures to do replication. So why not run sp thru
osql?
Is is possible for a t-sql expert to create such an sp? I searched
Internet and found few resources about msde to msde replication.
hi,
"news.microsoft.com" <martinc@.hume-travel.com> ha scritto nel messaggio
news:u40hNYVWEHA.4092@.TK2MSFTNGP11.phx.gbl...
> How can we replicate data in one MSDE to the other MSDE without having to
> pay for MSSQL2000 full version to use the sql enterprise manager?
> It seems that Enterprise Manager or SQL-DMO based programs rely on
> system-provided stored procedures to do replication. So why not run sp
thru
> osql?
> Is is possible for a t-sql expert to create such an sp? I searched
> Internet and found few resources about msde to msde replication.
>
yep... it's not very documented, but you can even use SQL-DMO replication
ActiveX controls
this is a great article,
http://www.winnetmag.com/Article/Art...079/39079.html , but only for
SQL Server Magazine subscribers...
http://www.compman.co.uk/cgi-win/browse.exe?ref=552118 has an entire
(little) chapter about replication and SQL-DMO... this is the best book
about SQL-DMO ever released...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||With the developers edition of SQL Server you can setup replication between
test systems, then script out the the entire replication setup. The script
can then be used as a template for setting up future replications.
Jim
"news.microsoft.com" <martinc@.hume-travel.com> wrote in message
news:u40hNYVWEHA.4092@.TK2MSFTNGP11.phx.gbl...
> How can we replicate data in one MSDE to the other MSDE without having to
> pay for MSSQL2000 full version to use the sql enterprise manager?
> It seems that Enterprise Manager or SQL-DMO based programs rely on
> system-provided stored procedures to do replication. So why not run sp
thru
> osql?
> Is is possible for a t-sql expert to create such an sp? I searched
> Internet and found few resources about msde to msde replication.
>
pay for MSSQL2000 full version to use the sql enterprise manager?
It seems that Enterprise Manager or SQL-DMO based programs rely on
system-provided stored procedures to do replication. So why not run sp thru
osql?
Is is possible for a t-sql expert to create such an sp? I searched
Internet and found few resources about msde to msde replication.
hi,
"news.microsoft.com" <martinc@.hume-travel.com> ha scritto nel messaggio
news:u40hNYVWEHA.4092@.TK2MSFTNGP11.phx.gbl...
> How can we replicate data in one MSDE to the other MSDE without having to
> pay for MSSQL2000 full version to use the sql enterprise manager?
> It seems that Enterprise Manager or SQL-DMO based programs rely on
> system-provided stored procedures to do replication. So why not run sp
thru
> osql?
> Is is possible for a t-sql expert to create such an sp? I searched
> Internet and found few resources about msde to msde replication.
>
yep... it's not very documented, but you can even use SQL-DMO replication
ActiveX controls
this is a great article,
http://www.winnetmag.com/Article/Art...079/39079.html , but only for
SQL Server Magazine subscribers...
http://www.compman.co.uk/cgi-win/browse.exe?ref=552118 has an entire
(little) chapter about replication and SQL-DMO... this is the best book
about SQL-DMO ever released...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||With the developers edition of SQL Server you can setup replication between
test systems, then script out the the entire replication setup. The script
can then be used as a template for setting up future replications.
Jim
"news.microsoft.com" <martinc@.hume-travel.com> wrote in message
news:u40hNYVWEHA.4092@.TK2MSFTNGP11.phx.gbl...
> How can we replicate data in one MSDE to the other MSDE without having to
> pay for MSSQL2000 full version to use the sql enterprise manager?
> It seems that Enterprise Manager or SQL-DMO based programs rely on
> system-provided stored procedures to do replication. So why not run sp
thru
> osql?
> Is is possible for a t-sql expert to create such an sp? I searched
> Internet and found few resources about msde to msde replication.
>
MSDE to MSDE Replication
Hi,
I would like to know if I can do Replication from a MSDE 2000 to another
MSDE 2000 system (one way).
All I need to do is Sync Server database changes on to a Workstation
database(Real-Time).
Let me give an example.
We have Server and Workstation product. Our Server will have a LiveConfig db
and each workstation will have a localLookupDB(basically same as
LiveConfig). I know If I have the Server as Std SQL Server 2000 I can use
Replication to propogate changes onto workstation what if the Server is
MSDE?
Are there any ways to Replicate data From a Server database onto Workstation
database (Real-Time).
Your advice is appreciated.
Thanks
Arun
You can use merge replication for msde to msde. You can use snapshot,
transactional or merge replication to MSDE from SQL Server 2000. Your
latency may be in the order of minutes.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Arun Kumar" <arunpv@.hotmail.com> wrote in message
news:ObTva%232pFHA.748@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I would like to know if I can do Replication from a MSDE 2000 to another
> MSDE 2000 system (one way).
> All I need to do is Sync Server database changes on to a Workstation
> database(Real-Time).
> Let me give an example.
> We have Server and Workstation product. Our Server will have a LiveConfig
db
> and each workstation will have a localLookupDB(basically same as
> LiveConfig). I know If I have the Server as Std SQL Server 2000 I can use
> Replication to propogate changes onto workstation what if the Server is
> MSDE?
> Are there any ways to Replicate data From a Server database onto
Workstation
> database (Real-Time).
> Your advice is appreciated.
> Thanks
> Arun
>
|||Thanks for the reply.
If I do use merge replication from MSDE to MSDE what are the drawbacks?
Are there any other ways you can suggest for replicating data from one
server to another? (or one to many MSDE)
Thanks
Arun
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23KmSQu3pFHA.820@.TK2MSFTNGP09.phx.gbl...
> You can use merge replication for msde to msde. You can use snapshot,
> transactional or merge replication to MSDE from SQL Server 2000. Your
> latency may be in the order of minutes.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Arun Kumar" <arunpv@.hotmail.com> wrote in message
> news:ObTva%232pFHA.748@.TK2MSFTNGP12.phx.gbl...
> db
> Workstation
>
I would like to know if I can do Replication from a MSDE 2000 to another
MSDE 2000 system (one way).
All I need to do is Sync Server database changes on to a Workstation
database(Real-Time).
Let me give an example.
We have Server and Workstation product. Our Server will have a LiveConfig db
and each workstation will have a localLookupDB(basically same as
LiveConfig). I know If I have the Server as Std SQL Server 2000 I can use
Replication to propogate changes onto workstation what if the Server is
MSDE?
Are there any ways to Replicate data From a Server database onto Workstation
database (Real-Time).
Your advice is appreciated.
Thanks
Arun
You can use merge replication for msde to msde. You can use snapshot,
transactional or merge replication to MSDE from SQL Server 2000. Your
latency may be in the order of minutes.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Arun Kumar" <arunpv@.hotmail.com> wrote in message
news:ObTva%232pFHA.748@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I would like to know if I can do Replication from a MSDE 2000 to another
> MSDE 2000 system (one way).
> All I need to do is Sync Server database changes on to a Workstation
> database(Real-Time).
> Let me give an example.
> We have Server and Workstation product. Our Server will have a LiveConfig
db
> and each workstation will have a localLookupDB(basically same as
> LiveConfig). I know If I have the Server as Std SQL Server 2000 I can use
> Replication to propogate changes onto workstation what if the Server is
> MSDE?
> Are there any ways to Replicate data From a Server database onto
Workstation
> database (Real-Time).
> Your advice is appreciated.
> Thanks
> Arun
>
|||Thanks for the reply.
If I do use merge replication from MSDE to MSDE what are the drawbacks?
Are there any other ways you can suggest for replicating data from one
server to another? (or one to many MSDE)
Thanks
Arun
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23KmSQu3pFHA.820@.TK2MSFTNGP09.phx.gbl...
> You can use merge replication for msde to msde. You can use snapshot,
> transactional or merge replication to MSDE from SQL Server 2000. Your
> latency may be in the order of minutes.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Arun Kumar" <arunpv@.hotmail.com> wrote in message
> news:ObTva%232pFHA.748@.TK2MSFTNGP12.phx.gbl...
> db
> Workstation
>
MSDE to MS SQL restore
I have a MSDE database that I am trying to restore into MS SQL 7.
I am running the following restore from Query Analyzer;
RESTORE DATABASE name
FROM DISK = 'c:\mssql7\backup\name_backup'
I am getting the following error
Server: Msg 3624, Level 20, State 1, Line 1
Location: upgraddb.cpp:214
Expression: tableIndex < ARRAY_LEN (upgradeMap)
SPID: 7
Process ID: 748
Connection Broken
Is what I'm trying to do impossible or something I'm doing wrong. Any help would be much appreciatedI don't know if this will help.
I had the same problem where I wanted to resore a MSDE database to SQL Server 2000. There was just no way. So I then used DTS to just transfer the Database to the SQL Server 2000.|||Originally posted by machado
I don't know if this will help.
I had the same problem where I wanted to resore a MSDE database to SQL Server 2000. There was just no way. So I then used DTS to just transfer the Database to the SQL Server 2000.
I only have the backup file, I don't actually posess MSDE so as far as I know I can't actually connect to anything for a dts to work|||MSDE can be distributed free and is included on the MS Office Prof. 2000/XP CDs.
What I would suggest is installing MSDE on any other machine on your network and restoring the database to MSDE and then transfering the databse using DTS.|||Originally posted by machado
MSDE can be distributed free and is included on the MS Office Prof. 2000/XP CDs.
What I would suggest is installing MSDE on any other machine on your network and restoring the database to MSDE and then transfering the databse using DTS.
So it is :)
Thanks, I'm installing it nowsql
I am running the following restore from Query Analyzer;
RESTORE DATABASE name
FROM DISK = 'c:\mssql7\backup\name_backup'
I am getting the following error
Server: Msg 3624, Level 20, State 1, Line 1
Location: upgraddb.cpp:214
Expression: tableIndex < ARRAY_LEN (upgradeMap)
SPID: 7
Process ID: 748
Connection Broken
Is what I'm trying to do impossible or something I'm doing wrong. Any help would be much appreciatedI don't know if this will help.
I had the same problem where I wanted to resore a MSDE database to SQL Server 2000. There was just no way. So I then used DTS to just transfer the Database to the SQL Server 2000.|||Originally posted by machado
I don't know if this will help.
I had the same problem where I wanted to resore a MSDE database to SQL Server 2000. There was just no way. So I then used DTS to just transfer the Database to the SQL Server 2000.
I only have the backup file, I don't actually posess MSDE so as far as I know I can't actually connect to anything for a dts to work|||MSDE can be distributed free and is included on the MS Office Prof. 2000/XP CDs.
What I would suggest is installing MSDE on any other machine on your network and restoring the database to MSDE and then transfering the databse using DTS.|||Originally posted by machado
MSDE can be distributed free and is included on the MS Office Prof. 2000/XP CDs.
What I would suggest is installing MSDE on any other machine on your network and restoring the database to MSDE and then transfering the databse using DTS.
So it is :)
Thanks, I'm installing it nowsql
MSDE timeout with wireless network enabled
Hi,
I have local MSDE installed on my laptop. When I am physically
connected to our network I can connect through my ODBC application
without issue.
However, when I have wireless networking enabled the first time I try to
connect I get a timeout. But, I'm able to immediately connect after
that initial timeout without a problem. This only occurs when wireless
networking is enabled, as the timeout does not occur with a physical LAN
connection.
I have the following installation:
MDAC SDK 2.8
MSDE 8.00.761
XP SP2
VS.NET 7.1
Any help would be greatly appreciated.
Thanks,
John
I am having a similar issue using SQL querries over a wireless connection.
Is there a technology that is better suited for wireless? Say .net?
Thanks in advance...
"JohnD" wrote:
> Hi,
> I have local MSDE installed on my laptop. When I am physically
> connected to our network I can connect through my ODBC application
> without issue.
> However, when I have wireless networking enabled the first time I try to
> connect I get a timeout. But, I'm able to immediately connect after
> that initial timeout without a problem. This only occurs when wireless
> networking is enabled, as the timeout does not occur with a physical LAN
> connection.
> I have the following installation:
> MDAC SDK 2.8
> MSDE 8.00.761
> XP SP2
> VS.NET 7.1
> Any help would be greatly appreciated.
> Thanks,
> John
>
|||Do you have the same problem if you use an IP address instead of the MSDE
instance name? Perhaps you're having a name resolution problem?
Jim
"Chris James" <Chris James@.discussions.microsoft.com> wrote in message
news:B19527EB-85E1-4DBC-9E51-A8CD463C1A89@.microsoft.com...[vbcol=seagreen]
>I am having a similar issue using SQL querries over a wireless connection.
> Is there a technology that is better suited for wireless? Say .net?
> Thanks in advance...
> "JohnD" wrote:
|||Thanks for the post Jim, Ive tried it using IP and Instance name... The
funny thing is that not all wireless installations have this issue, I have
two sites across the street and down about 1/4 mile. One site with approx
250' between wireless access point and client work fairly reliably, the other
is only 50' apart and they fail all the time. I wonder if its the
application making too many querries and boging down the wireless. Both
sites are using identical equipment as well.
"Jim Young" wrote:
> Do you have the same problem if you use an IP address instead of the MSDE
> instance name? Perhaps you're having a name resolution problem?
> Jim
> "Chris James" <Chris James@.discussions.microsoft.com> wrote in message
> news:B19527EB-85E1-4DBC-9E51-A8CD463C1A89@.microsoft.com...
>
>
I have local MSDE installed on my laptop. When I am physically
connected to our network I can connect through my ODBC application
without issue.
However, when I have wireless networking enabled the first time I try to
connect I get a timeout. But, I'm able to immediately connect after
that initial timeout without a problem. This only occurs when wireless
networking is enabled, as the timeout does not occur with a physical LAN
connection.
I have the following installation:
MDAC SDK 2.8
MSDE 8.00.761
XP SP2
VS.NET 7.1
Any help would be greatly appreciated.
Thanks,
John
I am having a similar issue using SQL querries over a wireless connection.
Is there a technology that is better suited for wireless? Say .net?
Thanks in advance...
"JohnD" wrote:
> Hi,
> I have local MSDE installed on my laptop. When I am physically
> connected to our network I can connect through my ODBC application
> without issue.
> However, when I have wireless networking enabled the first time I try to
> connect I get a timeout. But, I'm able to immediately connect after
> that initial timeout without a problem. This only occurs when wireless
> networking is enabled, as the timeout does not occur with a physical LAN
> connection.
> I have the following installation:
> MDAC SDK 2.8
> MSDE 8.00.761
> XP SP2
> VS.NET 7.1
> Any help would be greatly appreciated.
> Thanks,
> John
>
|||Do you have the same problem if you use an IP address instead of the MSDE
instance name? Perhaps you're having a name resolution problem?
Jim
"Chris James" <Chris James@.discussions.microsoft.com> wrote in message
news:B19527EB-85E1-4DBC-9E51-A8CD463C1A89@.microsoft.com...[vbcol=seagreen]
>I am having a similar issue using SQL querries over a wireless connection.
> Is there a technology that is better suited for wireless? Say .net?
> Thanks in advance...
> "JohnD" wrote:
|||Thanks for the post Jim, Ive tried it using IP and Instance name... The
funny thing is that not all wireless installations have this issue, I have
two sites across the street and down about 1/4 mile. One site with approx
250' between wireless access point and client work fairly reliably, the other
is only 50' apart and they fail all the time. I wonder if its the
application making too many querries and boging down the wireless. Both
sites are using identical equipment as well.
"Jim Young" wrote:
> Do you have the same problem if you use an IP address instead of the MSDE
> instance name? Perhaps you're having a name resolution problem?
> Jim
> "Chris James" <Chris James@.discussions.microsoft.com> wrote in message
> news:B19527EB-85E1-4DBC-9E51-A8CD463C1A89@.microsoft.com...
>
>
MSDE Text datatype - unable to store more than 900 characters. (msde + visual studio 2003)
Hello,
I'm not sure if it's the setup I did wrong, but I can't seem to get mytext datatype in my database to store more than 900 characters. I'm trying to setup a news database for my website, which will populatethe information into a datagrid. To test, I manually added a newsitem in the database through the visual studio 2003 gui. Iimmediately noticed a problem as the I was getting an error after along news item saying:
"The value you entered is not consistent with the data type or length of the column, or over grid buffer limit."
I couldn't find anthing to set the buffer limit and the datatype is"text" filled with simple text in the column. As a further test,Isimply entered 12334567890123... up to 900 characters and stillrecevied the error.
I would appreciate someone leading me in the right direction on this one.
Thanks a lot.
I think may be your create table statement was not executed correctly because text can grow it is not table space based SQL Server creates an Arithmetic pointer to the file. Try the link below see if you can download the eval edition of the SQL Server. Or you could drop the table and recreate it and test again. Hope this helps.
http://www.microsoft.com/sql/evaluation/trial/default.mspx
I'm not sure if it's the setup I did wrong, but I can't seem to get mytext datatype in my database to store more than 900 characters. I'm trying to setup a news database for my website, which will populatethe information into a datagrid. To test, I manually added a newsitem in the database through the visual studio 2003 gui. Iimmediately noticed a problem as the I was getting an error after along news item saying:
"The value you entered is not consistent with the data type or length of the column, or over grid buffer limit."
I couldn't find anthing to set the buffer limit and the datatype is"text" filled with simple text in the column. As a further test,Isimply entered 12334567890123... up to 900 characters and stillrecevied the error.
I would appreciate someone leading me in the right direction on this one.
Thanks a lot.
I think may be your create table statement was not executed correctly because text can grow it is not table space based SQL Server creates an Arithmetic pointer to the file. Try the link below see if you can download the eval edition of the SQL Server. Or you could drop the table and recreate it and test again. Hope this helps.
http://www.microsoft.com/sql/evaluation/trial/default.mspx
MSDE TCP listen problem
I have recently installed a MSDE 2000 (unfortunately with no service pack yet) on a Standard Windows 2003 server. I have used the srvntcn.exe utility to make the MSDE server listen on TCP/IP port 1433. But it will not listen on that port! Or any other TCP
/IP port!! There is no information in the ERRORLOG file. This file just tells me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there were some security settings on that port. And my application had no problem in listening on port 1433.
After looking in the Event Viewer I found a solution to my problem: Windows 2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is not updated with a Service Pack. MSDE without Service Pack is not very secure to virusses like Slammer.
|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.
/IP port!! There is no information in the ERRORLOG file. This file just tells me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there were some security settings on that port. And my application had no problem in listening on port 1433.
After looking in the Event Viewer I found a solution to my problem: Windows 2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is not updated with a Service Pack. MSDE without Service Pack is not very secure to virusses like Slammer.
|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.
MSDE TCP listen problem
I have recently installed a MSDE 2000 (unfortunately with no service pack ye
t) on a Standard Windows 2003 server. I have used the srvntcn.exe utility to
make the MSDE server listen on TCP/IP port 1433. But it will not listen on
that port! Or any other TCP
/IP port!! There is no information in the ERRORLOG file. This file just tell
s me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there w
ere some security settings on that port. And my application had no problem i
n listening on port 1433.After looking in the Event Viewer I found a solution to my problem: Windows
2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is n
ot updated with a Service Pack. MSDE without Service Pack is not very secure
to virusses like Slammer.|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.
t) on a Standard Windows 2003 server. I have used the srvntcn.exe utility to
make the MSDE server listen on TCP/IP port 1433. But it will not listen on
that port! Or any other TCP
/IP port!! There is no information in the ERRORLOG file. This file just tell
s me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there w
ere some security settings on that port. And my application had no problem i
n listening on port 1433.After looking in the Event Viewer I found a solution to my problem: Windows
2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is n
ot updated with a Service Pack. MSDE without Service Pack is not very secure
to virusses like Slammer.|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.
MSDE taskbar utility icon
I used to have an icon on then notification area of the taskbar which I
could use to start and stop MSDE. It has recently disappeard and I don't
have a clue how to restore it to the taskbar.
Can anyone give me a hint what this little utility is and how to make it
appear on the taskbar.
Thanks much.
Hi Michael,
It's the Service Manager. Try running it from Start>Programs>MSDE>Service
Manager.
If it doesn't appear, it might be that you have network connections
disabled. Look in svrnetcn.exe.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Michael Appelmans" <mla@.zitinko.com> wrote in message
news:MPG.1b44e34cb08b40d89896aa@.news.microsoft.com ...
> I used to have an icon on then notification area of the taskbar which I
> could use to start and stop MSDE. It has recently disappeard and I don't
> have a clue how to restore it to the taskbar.
> Can anyone give me a hint what this little utility is and how to make it
> appear on the taskbar.
> Thanks much.
|||Hello,
You can also create a shortuc with the following command line in the start
menu (autostart)
"C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe" /n
"Greg Low (MVP)" <greglow@.lowell.com.au> a crit dans le message de
news:elpz3PkWEHA.2940@.TK2MSFTNGP09.phx.gbl...
> Hi Michael,
> It's the Service Manager. Try running it from Start>Programs>MSDE>Service
> Manager.
> If it doesn't appear, it might be that you have network connections
> disabled. Look in svrnetcn.exe.
> HTH,
> --
> Greg Low (MVP)
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Michael Appelmans" <mla@.zitinko.com> wrote in message
> news:MPG.1b44e34cb08b40d89896aa@.news.microsoft.com ...
>
|||I don't seem to have an MSDE entry in my Start > All Programs menu. Not=20
sure why. The service manager runs fine when I use the command line you=20
provided.
Thanks much.
Michael
In article <eGpLWznWEHA.4020@.TK2MSFTNGP09.phx.gbl>, fa097770
@.nospam.skynet.be says...
> Hello,
>=20
> You can also create a shortuc with the following command line in the star=
t
> menu (autostart)
> "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe" /n
>=20
>=20
> "Greg Low (MVP)" <greglow@.lowell.com.au> a =E9crit dans le message de
[vbcol=seagreen]
> news:elpz3PkWEHA.2940@.TK2MSFTNGP09.phx.gbl...
ce[vbcol=seagreen]
I[vbcol=seagreen]
n't[vbcol=seagreen]
it
>=20
>=20
>=20
|||Hello,
You can create a shortcut with the command line and after that move that
shortcut to the start menu.
"Michael Appelmans" <mla@.zitinko.com> a crit dans le message de
news:MPG.1b461a353834af939896ac@.news.microsoft.com ...
I don't seem to have an MSDE entry in my Start > All Programs menu. Not
sure why. The service manager runs fine when I use the command line you
provided.
Thanks much.
Michael
In article <eGpLWznWEHA.4020@.TK2MSFTNGP09.phx.gbl>, fa097770
@.nospam.skynet.be says...
> Hello,
> You can also create a shortuc with the following command line in the start
> menu (autostart)
> "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe" /n
>
> "Greg Low (MVP)" <greglow@.lowell.com.au> a crit dans le message de
[vbcol=seagreen]
> news:elpz3PkWEHA.2940@.TK2MSFTNGP09.phx.gbl...
Start>Programs>MSDE>Service[vbcol=seagreen]
I[vbcol=seagreen]
don't[vbcol=seagreen]
it
>
>
sql
could use to start and stop MSDE. It has recently disappeard and I don't
have a clue how to restore it to the taskbar.
Can anyone give me a hint what this little utility is and how to make it
appear on the taskbar.
Thanks much.
Hi Michael,
It's the Service Manager. Try running it from Start>Programs>MSDE>Service
Manager.
If it doesn't appear, it might be that you have network connections
disabled. Look in svrnetcn.exe.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Michael Appelmans" <mla@.zitinko.com> wrote in message
news:MPG.1b44e34cb08b40d89896aa@.news.microsoft.com ...
> I used to have an icon on then notification area of the taskbar which I
> could use to start and stop MSDE. It has recently disappeard and I don't
> have a clue how to restore it to the taskbar.
> Can anyone give me a hint what this little utility is and how to make it
> appear on the taskbar.
> Thanks much.
|||Hello,
You can also create a shortuc with the following command line in the start
menu (autostart)
"C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe" /n
"Greg Low (MVP)" <greglow@.lowell.com.au> a crit dans le message de
news:elpz3PkWEHA.2940@.TK2MSFTNGP09.phx.gbl...
> Hi Michael,
> It's the Service Manager. Try running it from Start>Programs>MSDE>Service
> Manager.
> If it doesn't appear, it might be that you have network connections
> disabled. Look in svrnetcn.exe.
> HTH,
> --
> Greg Low (MVP)
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Michael Appelmans" <mla@.zitinko.com> wrote in message
> news:MPG.1b44e34cb08b40d89896aa@.news.microsoft.com ...
>
|||I don't seem to have an MSDE entry in my Start > All Programs menu. Not=20
sure why. The service manager runs fine when I use the command line you=20
provided.
Thanks much.
Michael
In article <eGpLWznWEHA.4020@.TK2MSFTNGP09.phx.gbl>, fa097770
@.nospam.skynet.be says...
> Hello,
>=20
> You can also create a shortuc with the following command line in the star=
t
> menu (autostart)
> "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe" /n
>=20
>=20
> "Greg Low (MVP)" <greglow@.lowell.com.au> a =E9crit dans le message de
[vbcol=seagreen]
> news:elpz3PkWEHA.2940@.TK2MSFTNGP09.phx.gbl...
ce[vbcol=seagreen]
I[vbcol=seagreen]
n't[vbcol=seagreen]
it
>=20
>=20
>=20
|||Hello,
You can create a shortcut with the command line and after that move that
shortcut to the start menu.
"Michael Appelmans" <mla@.zitinko.com> a crit dans le message de
news:MPG.1b461a353834af939896ac@.news.microsoft.com ...
I don't seem to have an MSDE entry in my Start > All Programs menu. Not
sure why. The service manager runs fine when I use the command line you
provided.
Thanks much.
Michael
In article <eGpLWznWEHA.4020@.TK2MSFTNGP09.phx.gbl>, fa097770
@.nospam.skynet.be says...
> Hello,
> You can also create a shortuc with the following command line in the start
> menu (autostart)
> "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe" /n
>
> "Greg Low (MVP)" <greglow@.lowell.com.au> a crit dans le message de
[vbcol=seagreen]
> news:elpz3PkWEHA.2940@.TK2MSFTNGP09.phx.gbl...
Start>Programs>MSDE>Service[vbcol=seagreen]
I[vbcol=seagreen]
don't[vbcol=seagreen]
it
>
>
sql
MSDE subscription expiration
Hi,
I need help on changing the subscription expiration using MSDE, i would
like to know how can i do this, im not familiar with OSQL commands.
Thanks
Is there anyone out there who knows this? i know this is simple for
those who already knows how, all i need is a simple parameter commands
on how to set the subscription expiration on the MSDE. If only the
requirement is SQL enterprise manager then i wont be here on the first
place. Please help.
Thanks
|||Since this is the SQL Server MSDE group then guys here should know at
least what im talking about.
|||> Since this is the SQL Server MSDE group then guys here should know at
> least what im talking about.
And i demand an answer right now?
MSDE can be downloaded for free and no subscription is needed So what are
you talking about?
Cheers,
Erik
"Angelo" <oracle_sigma@.yahoo.com> schreef in bericht
news:1138340405.295057.256040@.g43g2000cwa.googlegr oups.com...
> Since this is the SQL Server MSDE group then guys here should know at
> least what im talking about.
>
|||Hi Erik,
Thanks for the reply, what i need is a command parameters on how to set
the subscription expiration on MSDE, cause everytime when we didnt
synchronize our handhelds let say 3 weeks, it occurs a subscription
expiration. Could you tell me how can i set this just using the MSDE
osql commands?
really appreciate for your help
|||Hi Erik,
To clarify it more, please click on the link or copy and paste
http://groups.google.com.ph/group/mi...899b6eb4ce9f3a
All they are talking about is how to set USING enterprise manager, the
question is how can i set it using MSDE?
Thanks,
Angelo
|||Hi Erik,
To clarify it more, please copy and paste
http://groups.google.com.ph/group/mi...899b6eb4ce9f3a
All they are talking about is how to set USING enterprise manager, the
question is how can i set it using MSDE?
Thanks,
Angelo
|||See if these two articles help
http://msdn.microsoft.com/library/de...plmon_92ge.asp
http://msdn.microsoft.com/library/de..._repl_9b5a.asp
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Angelo" <oracle_sigma@.yahoo.com> wrote in message
news:1138590558.961274.264570@.g49g2000cwa.googlegr oups.com...
> Hi Erik,
> To clarify it more, please click on the link or copy and paste
> http://groups.google.com.ph/group/mi...899b6eb4ce9f3a
> All they are talking about is how to set USING enterprise manager, the
> question is how can i set it using MSDE?
> Thanks,
> Angelo
>
|||Hi Roger,
Many thanks for the info, yes it help me in some ways also. Can you
take a look on the scripts below if this is the one that i have to do?
Can you specifically key in all the necessary things?
************************************************** *******
DECLARE @.publication AS sysname
SET @.publication = N'[my_publication]'
USE [my_database]
EXEC sp_changepublication @.publication = @.publication,
@.property = N'retention',
@.value = [my_value]
GO
************************************************** ************
now the requirement is
Database Name = ServerDB
Publication Name = Pubserver1
Days required = at least 30 days
************************************************** ************
Actually someone gave me this instructions and i have to run this
scripts using osql -E -XXX.sql
Thanks,
Angelo
|||Hi Roger,
Can you help me put all the names to its proper place also?
When you have MSDE, is it 336 hours its default retention period
subscription expiration? or it depends on the service pack that it is
currently installed?
Thanks
Angelo
I need help on changing the subscription expiration using MSDE, i would
like to know how can i do this, im not familiar with OSQL commands.
Thanks
Is there anyone out there who knows this? i know this is simple for
those who already knows how, all i need is a simple parameter commands
on how to set the subscription expiration on the MSDE. If only the
requirement is SQL enterprise manager then i wont be here on the first
place. Please help.
Thanks
|||Since this is the SQL Server MSDE group then guys here should know at
least what im talking about.
|||> Since this is the SQL Server MSDE group then guys here should know at
> least what im talking about.
And i demand an answer right now?
MSDE can be downloaded for free and no subscription is needed So what are
you talking about?
Cheers,
Erik
"Angelo" <oracle_sigma@.yahoo.com> schreef in bericht
news:1138340405.295057.256040@.g43g2000cwa.googlegr oups.com...
> Since this is the SQL Server MSDE group then guys here should know at
> least what im talking about.
>
|||Hi Erik,
Thanks for the reply, what i need is a command parameters on how to set
the subscription expiration on MSDE, cause everytime when we didnt
synchronize our handhelds let say 3 weeks, it occurs a subscription
expiration. Could you tell me how can i set this just using the MSDE
osql commands?
really appreciate for your help
|||Hi Erik,
To clarify it more, please click on the link or copy and paste
http://groups.google.com.ph/group/mi...899b6eb4ce9f3a
All they are talking about is how to set USING enterprise manager, the
question is how can i set it using MSDE?
Thanks,
Angelo
|||Hi Erik,
To clarify it more, please copy and paste
http://groups.google.com.ph/group/mi...899b6eb4ce9f3a
All they are talking about is how to set USING enterprise manager, the
question is how can i set it using MSDE?
Thanks,
Angelo
|||See if these two articles help
http://msdn.microsoft.com/library/de...plmon_92ge.asp
http://msdn.microsoft.com/library/de..._repl_9b5a.asp
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Angelo" <oracle_sigma@.yahoo.com> wrote in message
news:1138590558.961274.264570@.g49g2000cwa.googlegr oups.com...
> Hi Erik,
> To clarify it more, please click on the link or copy and paste
> http://groups.google.com.ph/group/mi...899b6eb4ce9f3a
> All they are talking about is how to set USING enterprise manager, the
> question is how can i set it using MSDE?
> Thanks,
> Angelo
>
|||Hi Roger,
Many thanks for the info, yes it help me in some ways also. Can you
take a look on the scripts below if this is the one that i have to do?
Can you specifically key in all the necessary things?
************************************************** *******
DECLARE @.publication AS sysname
SET @.publication = N'[my_publication]'
USE [my_database]
EXEC sp_changepublication @.publication = @.publication,
@.property = N'retention',
@.value = [my_value]
GO
************************************************** ************
now the requirement is
Database Name = ServerDB
Publication Name = Pubserver1
Days required = at least 30 days
************************************************** ************
Actually someone gave me this instructions and i have to run this
scripts using osql -E -XXX.sql
Thanks,
Angelo
|||Hi Roger,
Can you help me put all the names to its proper place also?
When you have MSDE, is it 336 hours its default retention period
subscription expiration? or it depends on the service pack that it is
currently installed?
Thanks
Angelo
MSDE subscription expiration
Hi Guys,
We have an application that uses MSDE and Handheld devices. The problem is some users forgot to synch their handhelds for almost a month now.
I'm using MSDE and could someone help me how to change or set the subscription expiration using the OSQL command parameters?
I assume that the default hours of expiration of the subscription is 336 hours since it is the default of SQL enterprise which anyway it doesnt count since my requirement is MSDE. Actually my requirement is i want to set it to 720 hours.
I'm not sure also of what is the default subscription expiration on the MSDE side using the latest service pack 4. Could you please help me also on how to view the subscription expiration?
I've been looking for a solution in the microsoft website and i don't have any luck finding one.
Thanks,
Angelo
Is there someone here who knows this? i already got a 100+ viewers and still no replies. Can anyone tell me instead where should i ask about this issue.MSDE Subscriber's database > 2GB
Hi all !
We have a database with publication on
SBS2003 Premium Edition,
and 4 subscribers on workstations in warehouses on:
- Windows XP Professional
- MSDE
The database is 1.6 GB now and growing
further. I should migrate from MSDE
to SQL Server 2000.
Which version of SQL has to be installed
at warehouses (on top of Win XP Prof)?
Do I have to break the replication before ?
Thanks,
Pagus
Paul,
what about Personal Edition + Win XP Pro ?
Win XP Pro is working OK with MSDE, I wouldn't like to
purchase Win Server product :-(
Pagus
On Mon, 6 Sep 2004 00:48:11 -0700, "Paul Ibison"
<Paul.Ibison@.Pygmalion.Com> wrote:
>Pagus,
>you'll need Standard or Enterprise Edition. The OSs=20
>required for these editions of sql server are:
>Windows Server 2003, Standard Edition1=20
>Windows Server 2003, Enterprise Edition1=20
>Windows Server 2003, Datacenter Edition1=20
>Windows=AE 2000 Server=20
>Windows 2000 Advanced Server=20
>Windows 2000 Datacenter Server=20
>Windows NT=AE Server version 4.0 with Service Pack 5 (SP5)=20
>or later=20
>Windows NT Server 4.0, Enterprise Edition, with SP5 or=20
>later=20
>HTH,
>Paul Ibison
>(The ONLY sql server 2000 replication book:
>http://www.nwsu.com/0974973602p.html)
>
|||Pagus,
you're quire right, subject to the following restrictions:
It includes a concurrent workload governor that limits
its scalability; performance degrades when more than five
Transact-SQL batches are executed concurrently.
It cannot act as a transactional replication publisher
(subscriber only).
Regards,
Paul Ibison
We have a database with publication on
SBS2003 Premium Edition,
and 4 subscribers on workstations in warehouses on:
- Windows XP Professional
- MSDE
The database is 1.6 GB now and growing
further. I should migrate from MSDE
to SQL Server 2000.
Which version of SQL has to be installed
at warehouses (on top of Win XP Prof)?
Do I have to break the replication before ?
Thanks,
Pagus
Paul,
what about Personal Edition + Win XP Pro ?
Win XP Pro is working OK with MSDE, I wouldn't like to
purchase Win Server product :-(
Pagus
On Mon, 6 Sep 2004 00:48:11 -0700, "Paul Ibison"
<Paul.Ibison@.Pygmalion.Com> wrote:
>Pagus,
>you'll need Standard or Enterprise Edition. The OSs=20
>required for these editions of sql server are:
>Windows Server 2003, Standard Edition1=20
>Windows Server 2003, Enterprise Edition1=20
>Windows Server 2003, Datacenter Edition1=20
>Windows=AE 2000 Server=20
>Windows 2000 Advanced Server=20
>Windows 2000 Datacenter Server=20
>Windows NT=AE Server version 4.0 with Service Pack 5 (SP5)=20
>or later=20
>Windows NT Server 4.0, Enterprise Edition, with SP5 or=20
>later=20
>HTH,
>Paul Ibison
>(The ONLY sql server 2000 replication book:
>http://www.nwsu.com/0974973602p.html)
>
|||Pagus,
you're quire right, subject to the following restrictions:
It includes a concurrent workload governor that limits
its scalability; performance degrades when more than five
Transact-SQL batches are executed concurrently.
It cannot act as a transactional replication publisher
(subscriber only).
Regards,
Paul Ibison
MSDE Subscriber names
I plan to set up merge replication and have laptops with an MSDE
subscription for replication. I want my application to use the database
name and wondered if I can (and should?) have the same database name on both
the laptop and the main publication. Thanks.
David
It helps to identify the subscriber database, but there is no real
requirement. All the subscribers should have the same database name if you
are publishing to multiple subscribers at once.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:%23KWrAVCpFHA.320@.TK2MSFTNGP09.phx.gbl...
> I plan to set up merge replication and have laptops with an MSDE
> subscription for replication. I want my application to use the database
> name and wondered if I can (and should?) have the same database name on
both
> the laptop and the main publication. Thanks.
> David
>
subscription for replication. I want my application to use the database
name and wondered if I can (and should?) have the same database name on both
the laptop and the main publication. Thanks.
David
It helps to identify the subscriber database, but there is no real
requirement. All the subscribers should have the same database name if you
are publishing to multiple subscribers at once.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"David Chase" <dlchase@.lifetimeinc.com> wrote in message
news:%23KWrAVCpFHA.320@.TK2MSFTNGP09.phx.gbl...
> I plan to set up merge replication and have laptops with an MSDE
> subscription for replication. I want my application to use the database
> name and wondered if I can (and should?) have the same database name on
both
> the laptop and the main publication. Thanks.
> David
>
MSDE stopps with code 1603
Hi!
When I tried to install MDSE on W2003 Server it stopped with error code
1603. I want to Install NAI ProtectionPilot 1.1 an Veritas Backup Exec 9.1
whic use that as well.
KB article dont match to my problem...
Thanks for helping
Marcel
hi Marcel,
Marcel Ksling wrote:
> Hi!
> When I tried to install MDSE on W2003 Server it stopped with error
> code 1603. I want to Install NAI ProtectionPilot 1.1 an Veritas
> Backup Exec 9.1 whic use that as well.
> KB article dont match to my problem...
> Thanks for helping
> Marcel
please have a look at http://tinyurl.com/apb8e to see if helps...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hello,
I have seen the exact same problem on both Windows XP PRO and a Windows 2003
Server.
MSDE2000 Release A will not always install again after it has been
un-installed. I have never seen this problem on my own development machine,
only on customers machines installing our product!
So my guess is that on my machine where ex. Visual Studio .NET is installed
something is eliminating the problem... but NOT on a standard Windows XP PRO
or Windoes 2003 Server!
My question: Is there a solution to the problem or not ?
I can see a lot of people have had the same problem...
Best regards
Per Clausen
"Andrea Montanari" wrote:
> hi Marcel,
> Marcel K?sling wrote:
> please have a look at http://tinyurl.com/apb8e to see if helps...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi,
Per Clausen wrote:
> Hello,
> I have seen the exact same problem on both Windows XP PRO and a
> Windows 2003 Server.
which both now have MDAC 2.8 sp 2 ...
> MSDE2000 Release A will not always install again after it has been
> un-installed. I have never seen this problem on my own development
> machine, only on customers machines installing our product!
uninstalling MSDE (often) does non properly clear MSDE related file system
and registry entries, and this often confuses users... a proper (and manual)
clean up is required, as indicated in
http://support.microsoft.com/default...b;en-us;320873
http://support.microsoft.com/default...;EN-US;Q290991
> So my guess is that on my machine where ex. Visual Studio .NET is
> installed something is eliminating the problem... but NOT on a
> standard Windows XP PRO or Windoes 2003 Server!
> My question: Is there a solution to the problem or not ?
> I can see a lot of people have had the same problem...
none that I'm aware of... but, for what is worth, I never had this kind of
problems on Win2k, XP (rtm/sp1/sp2) and Win2003 (rtm/sp1)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
Thank you for your reply. I guess we have to make a custom application to
fix the problem. It's just not easy when I can't reproduce the problem on my
own machine.
Best regards
Per Clausen
"Andrea Montanari" wrote:
> hi,
> Per Clausen wrote:
> which both now have MDAC 2.8 sp 2 ...
>
> uninstalling MSDE (often) does non properly clear MSDE related file system
> and registry entries, and this often confuses users... a proper (and manual)
> clean up is required, as indicated in
> http://support.microsoft.com/default...b;en-us;320873
> http://support.microsoft.com/default...;EN-US;Q290991
>
> none that I'm aware of... but, for what is worth, I never had this kind of
> problems on Win2k, XP (rtm/sp1/sp2) and Win2003 (rtm/sp1)
>
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||Hi,
For your information:
I have found a way to reproduce the MSDE re-installation problem.
If the value InstanceComponentSet.1 exist in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Component Set MSDE
will NOT install.
To make the MSDE install simply delete InstanceComponentSet.1 and everything
seems to work fine again.
Best regards
Per Clausen
CIM Electronics A/S
"Andrea Montanari" wrote:
> hi,
> Per Clausen wrote:
> which both now have MDAC 2.8 sp 2 ...
>
> uninstalling MSDE (often) does non properly clear MSDE related file system
> and registry entries, and this often confuses users... a proper (and manual)
> clean up is required, as indicated in
> http://support.microsoft.com/default...b;en-us;320873
> http://support.microsoft.com/default...;EN-US;Q290991
>
> none that I'm aware of... but, for what is worth, I never had this kind of
> problems on Win2k, XP (rtm/sp1/sp2) and Win2003 (rtm/sp1)
>
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi,
Per Clausen wrote:
> Hi,
> For your information:
> I have found a way to reproduce the MSDE re-installation problem.
> If the value InstanceComponentSet.1 exist in
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Component
> Set MSDE will NOT install.
> To make the MSDE install simply delete InstanceComponentSet.1 and
> everything seems to work fine again.
>
it's documented...
http://support.microsoft.com/default...b;en-us;320873
point 3..
3. If the following registry key points to the MSDE 2000 instance
ProductCode, remove the value InstanceComponentSet.x. For example,
InstanceComponentSet.1 has a value that matches the ProductCode of
Sqlrun01.msi:
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql
When I tried to install MDSE on W2003 Server it stopped with error code
1603. I want to Install NAI ProtectionPilot 1.1 an Veritas Backup Exec 9.1
whic use that as well.
KB article dont match to my problem...
Thanks for helping
Marcel
hi Marcel,
Marcel Ksling wrote:
> Hi!
> When I tried to install MDSE on W2003 Server it stopped with error
> code 1603. I want to Install NAI ProtectionPilot 1.1 an Veritas
> Backup Exec 9.1 whic use that as well.
> KB article dont match to my problem...
> Thanks for helping
> Marcel
please have a look at http://tinyurl.com/apb8e to see if helps...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hello,
I have seen the exact same problem on both Windows XP PRO and a Windows 2003
Server.
MSDE2000 Release A will not always install again after it has been
un-installed. I have never seen this problem on my own development machine,
only on customers machines installing our product!
So my guess is that on my machine where ex. Visual Studio .NET is installed
something is eliminating the problem... but NOT on a standard Windows XP PRO
or Windoes 2003 Server!
My question: Is there a solution to the problem or not ?
I can see a lot of people have had the same problem...
Best regards
Per Clausen
"Andrea Montanari" wrote:
> hi Marcel,
> Marcel K?sling wrote:
> please have a look at http://tinyurl.com/apb8e to see if helps...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi,
Per Clausen wrote:
> Hello,
> I have seen the exact same problem on both Windows XP PRO and a
> Windows 2003 Server.
which both now have MDAC 2.8 sp 2 ...
> MSDE2000 Release A will not always install again after it has been
> un-installed. I have never seen this problem on my own development
> machine, only on customers machines installing our product!
uninstalling MSDE (often) does non properly clear MSDE related file system
and registry entries, and this often confuses users... a proper (and manual)
clean up is required, as indicated in
http://support.microsoft.com/default...b;en-us;320873
http://support.microsoft.com/default...;EN-US;Q290991
> So my guess is that on my machine where ex. Visual Studio .NET is
> installed something is eliminating the problem... but NOT on a
> standard Windows XP PRO or Windoes 2003 Server!
> My question: Is there a solution to the problem or not ?
> I can see a lot of people have had the same problem...
none that I'm aware of... but, for what is worth, I never had this kind of
problems on Win2k, XP (rtm/sp1/sp2) and Win2003 (rtm/sp1)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
Thank you for your reply. I guess we have to make a custom application to
fix the problem. It's just not easy when I can't reproduce the problem on my
own machine.
Best regards
Per Clausen
"Andrea Montanari" wrote:
> hi,
> Per Clausen wrote:
> which both now have MDAC 2.8 sp 2 ...
>
> uninstalling MSDE (often) does non properly clear MSDE related file system
> and registry entries, and this often confuses users... a proper (and manual)
> clean up is required, as indicated in
> http://support.microsoft.com/default...b;en-us;320873
> http://support.microsoft.com/default...;EN-US;Q290991
>
> none that I'm aware of... but, for what is worth, I never had this kind of
> problems on Win2k, XP (rtm/sp1/sp2) and Win2003 (rtm/sp1)
>
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||Hi,
For your information:
I have found a way to reproduce the MSDE re-installation problem.
If the value InstanceComponentSet.1 exist in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Component Set MSDE
will NOT install.
To make the MSDE install simply delete InstanceComponentSet.1 and everything
seems to work fine again.
Best regards
Per Clausen
CIM Electronics A/S
"Andrea Montanari" wrote:
> hi,
> Per Clausen wrote:
> which both now have MDAC 2.8 sp 2 ...
>
> uninstalling MSDE (often) does non properly clear MSDE related file system
> and registry entries, and this often confuses users... a proper (and manual)
> clean up is required, as indicated in
> http://support.microsoft.com/default...b;en-us;320873
> http://support.microsoft.com/default...;EN-US;Q290991
>
> none that I'm aware of... but, for what is worth, I never had this kind of
> problems on Win2k, XP (rtm/sp1/sp2) and Win2003 (rtm/sp1)
>
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi,
Per Clausen wrote:
> Hi,
> For your information:
> I have found a way to reproduce the MSDE re-installation problem.
> If the value InstanceComponentSet.1 exist in
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Component
> Set MSDE will NOT install.
> To make the MSDE install simply delete InstanceComponentSet.1 and
> everything seems to work fine again.
>
it's documented...
http://support.microsoft.com/default...b;en-us;320873
point 3..
3. If the following registry key points to the MSDE 2000 instance
ProductCode, remove the value InstanceComponentSet.x. For example,
InstanceComponentSet.1 has a value that matches the ProductCode of
Sqlrun01.msi:
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql
MSDE startup problem
Hi
MSDE installed on one of our clients PC is having problems with startup.
What could cause such problems (error log below - computer, instance
and user database names are changed to protect user information)?
Client's OS is Windows ME.
Hilarion
2004-10-20 15:27:11.88 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows 4.90 (Build 3000: )
2004-10-20 15:27:11.88 server Copyright (C) 1988-2002 Microsoft Corporation.
2004-10-20 15:27:11.88 server All rights reserved.
2004-10-20 15:27:11.88 server Server Process ID is -1747957.
2004-10-20 15:27:11.88 server Logging SQL Server messages in file 'C:\PROGRAM FILES\Microsoft SQL
Server\MSSQL$INSTANCE_NAME\LOG\ERRORLOG'.
2004-10-20 15:27:11.90 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-10-20 15:27:11.95 server SQL Server configured for thread mode processing.
2004-10-20 15:27:11.95 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-10-20 15:27:11.97 spid3 Starting up database 'master'.
2004-10-20 15:27:12.42 spid5 Starting up database 'model'.
2004-10-20 15:27:12.47 server Using 'dbghelp.dll' version '4.0.5'
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
2004-10-20 15:27:12.54 server SqlDumpExceptionHandler: Process -2094925 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:12 spid 0
*
* Exception Address = 42CF2293 (ConnectionListen + 0000107E Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address FFFFFFFF
2004-10-20 15:27:12.54 spid3 Server name is 'COMPUTER_NAME\INSTANCE_NAME'.
* 0051739E Module(SQLSERVR+0011739E)
2004-10-20 15:27:12.62 spid8 Starting up database 'msdb* BFF79391 Module(KERNEL32+00019391) (HeapCreate+0000032E)
* BFF76E3A Module(KERNEL32+00016E3A) (VirtualQueryEx+00001774)
* BFF76D37 Module(KERNEL32+00016D37) (VirtualQueryEx+00001671)
2004-10-20 15:27:12.65 spid9 Starting up database 'MY_DATABASE'.
* 0070042B Module(SQLSERVR+0030042B) (GetIMallocForMsxml+00096397)
* ----
*Dump thread - spid = 1, PSS = 0x1a5ea098, EC = 0x1a5ea3c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:12 spid 1
*
* StackDump (all)
*
*
*
* Edi: C1A822E0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 018AFC08: 018AFED0 00982517 00000000 018AFC94 00517E27 000003E8
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 018AFB98: 018AFBD0 410721D6 00E013F0 1A5EA564 018AFBD0 000003E8
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 018AFB40: FFFFFFFF BFF831BC C1A822E0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 00517E27 Module(SQLSERVR+00117E27)
* 00517DB5 Module(SQLSERVR+00117DB5)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 2, PSS = 0x1a62a098, EC = 0x1a62a3c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 2
*
* StackDump (all)
*
*
*
* Edi: C1A827E0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
* Ecx: 019EFA4C: 019EFECC 00982517 00000000 019EFA74 004017CB FFFFFFFF
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 019EF9DC: 019EFA14 410721D6 00E01280 1A62A564 019EFA14 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 019EF984: FFFFFFFF BFF831BC C1A827E0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 00516B22 Module(SQLSERVR+00116B22)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 3, PSS = 0x1a628098, EC = 0x1a6283c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 3
*
* StackDump (all)
*
*
*
* Edi: C1A82A60:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 01A8F9F4: 01A8FEC8 0097E819 00000002 01A8FED4 005196A1 00000002
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 01A8F530: 01A8F568 410721D6 00E01110 01A8F59C 01A8F568 FFFFFFFF
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 01A8F4D8: FFFFFFFF BFF831BC C1A82A60 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 41072DD9 Module(UMS+00002DD9) (UmsEvent::WaitMultiple+00000019)
* 005196A1 Module(SQLSERVR+001196A1)
* 00518066 Module(SQLSERVR+00118066)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 4, PSS = 0x1a622098, EC = 0x1a6223c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 4
*
* StackDump (all)
*
*
*
* Edi: C1A82040:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
* Ecx: 0180FDC8: 0180FE94 00982517 00000000 0180FDF0 004017CB 00001388
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 0180FD58: 0180FD90 410721D6 00E02F90 1A622564 0180FD90 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 0180FD00: FFFFFFFF BFF831BC C1A82040 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 00516F4E Module(SQLSERVR+00116F4E)
* 00516CC4 Module(SQLSERVR+00116CC4)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 5, PSS = 0x1a630098, EC = 0x1a6303c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
2004-10-20 15:27:13.48 spid5 Clearing tempdb database.
kDump (all)
*
*
*
* Edi: C1A83E80:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 01C9F484: 011420B4 00200000 00100000 01C9F4CC 00483C40 00000001
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 01C9F3D4: 01C9F418 0040C9C9 000000D0 00012000 00000000 1A6B4000
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 01C9F35C: 011420B4 00200002 00200000 01C9F374 00415052 00000004
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 0040C9C9 Module(SQLSERVR+0000C9C9)
* 00485EFA Module(SQLSERVR+00085EFA)
* 00485FF5 Module(SQLSERVR+00085FF5)
* 00483C40 Module(SQLSERVR+00083C40)
* 01C9FBA2 Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 6, PSS = 0x1a634098, EC = 0x1a6343c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 6
*
* StackDump (all)
*
*
*
* Edi: C1A82CE0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 01B2FC50: 01B2FED0 00982517 00000000 01B2FC78 004017CB FFFFFFFF
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 01B2FBE0: 01B2FC18 410721D6 00E02C90 1A634564 01B2FC18 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 01B2FB88: FFFFFFFF BFF831BC C1A82CE0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 00517249 Module(SQLSERVR+00117249)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 7, PSS = 0x1a684098, EC = 0x1a6843c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 7
*
* StackDump (all)
*
*
*
* Edi: C1A82560:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 0194FC3C: 0194FED0 00982517 00000000 0194FC64 004017CB FFFFFFFF
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 0194FBCC: 0194FC04 410721D6 00E02E20 1A684564 0194FC04 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 0194FB74: FFFFFFFF BFF831BC C1A82560 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 0051876D Module(SQLSERVR+0011876D)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 8, PSS = 0x1a6b8098, EC = 0x1a6b83c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 8
*
* StackDump (all)
*
*
*
* Edi: C1A84670:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 0225E550: 0225E64C 0097E7BA FFFFFFFF 0225E58C 0040330A 1A6B2030
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 0225E4D4: 0225E504 00440F0C 1A6F2000 00002000 0009C000 00000000
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 0225E454: FFFFFFFF BFF831BC C1A84670 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 00440F0C Module(SQLSERVR+00040F0C)
* 00441154 Module(SQLSERVR+00041154)
* 0040330A Module(SQLSERVR+0000330A)
* 00403E2F Module(SQLSERVR+00003E2F)
* 00406528 Module(SQLSERVR+00006528)
* 004061CB Module(SQLSERVR+000061CB)
* 00405DF8 Module(SQLSERVR+00005DF8)
* 004F7294 Module(SQLSERVR+000F7294)
* 004050F7 Module(SQLSERVR+000050F7)
* 00409E39 Module(SQLSERVR+00009E39)
* 00409C49 Module(SQLSERVR+00009C49)
* 00515096 Module(SQLSERVR+00115096)
* 00514FB7 Module(SQLSERVR+00114FB7)
* 0050C0EB Module(SQLSERVR+0010C0EB)
* 005100FF Module(SQLSERVR+001100FF)
* 0050F152 Module(SQLSERVR+0010F152)
* 00519C2D Module(SQLSERVR+00119C2D)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 9, PSS = 0x1a6b0098, EC = 0x1a6b03c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 9
*
* StackDump (all)
*
*
*
* Edi: C1A848E0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 022FF05C: 022FF654 00980D9F 00000000 022FF660 0050FFC8 00000002
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 022FC784: 022FCBBC 00571383 022FE000 00001000 0037C000 00000000
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 022FC704: FFFFFFFF BFF831BC C1A848E0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 00571383 Module(SQLSERVR+00171383) (SQLExit+0004B903)
* 00571315 Module(SQLSERVR+00171315) (SQLExit+0004B895)
* 00571741 Module(SQLSERVR+00171741) (SQLExit+0004BCC1)
* 00511A3D Module(SQLSERVR+00111A3D)
* 0050FFC8 Module(SQLSERVR+0010FFC8)
* 0050F152 Module(SQLSERVR+0010F152)
* 00519C2D Module(SQLSERVR+00119C2D)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
2004-10-20 15:27:13.69 server SQL Server is aborting. Fatal exception c0000005 caught.
Seems like SQL Server craps out when trying to recover the model database. You can search the Net
for 3607, 3608 or 3609 and see which of these makes SQL server not recover model, see if you can get
SQL server started to see if you can restore a backup of your model database. If that doesn't help,
I suggest you open a case with MS Support...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hilarion" <hilarion@.noemail.nospam> wrote in message news:e6N5rMrtEHA.3088@.tk2msftngp13.phx.gbl...
> Hi
> MSDE installed on one of our clients PC is having problems with startup.
> What could cause such problems (error log below - computer, instance
> and user database names are changed to protect user information)?
> Client's OS is Windows ME.
> Hilarion
>
> 2004-10-20 15:27:11.88 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows 4.90 (Build 3000: )
> 2004-10-20 15:27:11.88 server Copyright (C) 1988-2002 Microsoft Corporation.
> 2004-10-20 15:27:11.88 server All rights reserved.
> 2004-10-20 15:27:11.88 server Server Process ID is -1747957.
> 2004-10-20 15:27:11.88 server Logging SQL Server messages in file 'C:\PROGRAM FILES\Microsoft
> SQL Server\MSSQL$INSTANCE_NAME\LOG\ERRORLOG'.
> 2004-10-20 15:27:11.90 server SQL Server is starting at priority class 'normal'(1 CPU
> detected).
> 2004-10-20 15:27:11.95 server SQL Server configured for thread mode processing.
> 2004-10-20 15:27:11.95 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock
> Owner Blocks.
> 2004-10-20 15:27:11.97 spid3 Starting up database 'master'.
> 2004-10-20 15:27:12.42 spid5 Starting up database 'model'.
> 2004-10-20 15:27:12.47 server Using 'dbghelp.dll' version '4.0.5'
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> 2004-10-20 15:27:12.54 server SqlDumpExceptionHandler: Process -2094925 generated fatal
> exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:12 spid 0
> *
> * Exception Address = 42CF2293 (ConnectionListen + 0000107E Line 0+00000000)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address FFFFFFFF
> 2004-10-20 15:27:12.54 spid3 Server name is 'COMPUTER_NAME\INSTANCE_NAME'.
> * 0051739E Module(SQLSERVR+0011739E)
> 2004-10-20 15:27:12.62 spid8 Starting up database 'msdb* BFF79391 Module(KERNEL32+00019391)
> (HeapCreate+0000032E)
> * BFF76E3A Module(KERNEL32+00016E3A) (VirtualQueryEx+00001774)
> * BFF76D37 Module(KERNEL32+00016D37) (VirtualQueryEx+00001671)
> 2004-10-20 15:27:12.65 spid9 Starting up database 'MY_DATABASE'.
> * 0070042B Module(SQLSERVR+0030042B) (GetIMallocForMsxml+00096397)
> * ----
> *Dump thread - spid = 1, PSS = 0x1a5ea098, EC = 0x1a5ea3c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:12 spid 1
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A822E0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 018AFC08: 018AFED0 00982517 00000000 018AFC94 00517E27 000003E8
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 018AFB98: 018AFBD0 410721D6 00E013F0 1A5EA564 018AFBD0 000003E8
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 018AFB40: FFFFFFFF BFF831BC C1A822E0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 00517E27 Module(SQLSERVR+00117E27)
> * 00517DB5 Module(SQLSERVR+00117DB5)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 2, PSS = 0x1a62a098, EC = 0x1a62a3c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 2
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A827E0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
> * Ecx: 019EFA4C: 019EFECC 00982517 00000000 019EFA74 004017CB FFFFFFFF
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 019EF9DC: 019EFA14 410721D6 00E01280 1A62A564 019EFA14 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 019EF984: FFFFFFFF BFF831BC C1A827E0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 00516B22 Module(SQLSERVR+00116B22)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 3, PSS = 0x1a628098, EC = 0x1a6283c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 3
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82A60:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 01A8F9F4: 01A8FEC8 0097E819 00000002 01A8FED4 005196A1 00000002
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 01A8F530: 01A8F568 410721D6 00E01110 01A8F59C 01A8F568 FFFFFFFF
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 01A8F4D8: FFFFFFFF BFF831BC C1A82A60 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 41072DD9 Module(UMS+00002DD9) (UmsEvent::WaitMultiple+00000019)
> * 005196A1 Module(SQLSERVR+001196A1)
> * 00518066 Module(SQLSERVR+00118066)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 4, PSS = 0x1a622098, EC = 0x1a6223c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 4
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82040:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
> * Ecx: 0180FDC8: 0180FE94 00982517 00000000 0180FDF0 004017CB 00001388
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 0180FD58: 0180FD90 410721D6 00E02F90 1A622564 0180FD90 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 0180FD00: FFFFFFFF BFF831BC C1A82040 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 00516F4E Module(SQLSERVR+00116F4E)
> * 00516CC4 Module(SQLSERVR+00116CC4)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 5, PSS = 0x1a630098, EC = 0x1a6303c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> 2004-10-20 15:27:13.48 spid5 Clearing tempdb database.
> kDump (all)
> *
> *
> *
> * Edi: C1A83E80:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 01C9F484: 011420B4 00200000 00100000 01C9F4CC 00483C40 00000001
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 01C9F3D4: 01C9F418 0040C9C9 000000D0 00012000 00000000 1A6B4000
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 01C9F35C: 011420B4 00200002 00200000 01C9F374 00415052 00000004
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 0040C9C9 Module(SQLSERVR+0000C9C9)
> * 00485EFA Module(SQLSERVR+00085EFA)
> * 00485FF5 Module(SQLSERVR+00085FF5)
> * 00483C40 Module(SQLSERVR+00083C40)
> * 01C9FBA2 Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 6, PSS = 0x1a634098, EC = 0x1a6343c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 6
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82CE0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 01B2FC50: 01B2FED0 00982517 00000000 01B2FC78 004017CB FFFFFFFF
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 01B2FBE0: 01B2FC18 410721D6 00E02C90 1A634564 01B2FC18 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 01B2FB88: FFFFFFFF BFF831BC C1A82CE0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 00517249 Module(SQLSERVR+00117249)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 7, PSS = 0x1a684098, EC = 0x1a6843c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 7
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82560:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 0194FC3C: 0194FED0 00982517 00000000 0194FC64 004017CB FFFFFFFF
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 0194FBCC: 0194FC04 410721D6 00E02E20 1A684564 0194FC04 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 0194FB74: FFFFFFFF BFF831BC C1A82560 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 0051876D Module(SQLSERVR+0011876D)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 8, PSS = 0x1a6b8098, EC = 0x1a6b83c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 8
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A84670:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 0225E550: 0225E64C 0097E7BA FFFFFFFF 0225E58C 0040330A 1A6B2030
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 0225E4D4: 0225E504 00440F0C 1A6F2000 00002000 0009C000 00000000
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 0225E454: FFFFFFFF BFF831BC C1A84670 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 00440F0C Module(SQLSERVR+00040F0C)
> * 00441154 Module(SQLSERVR+00041154)
> * 0040330A Module(SQLSERVR+0000330A)
> * 00403E2F Module(SQLSERVR+00003E2F)
> * 00406528 Module(SQLSERVR+00006528)
> * 004061CB Module(SQLSERVR+000061CB)
> * 00405DF8 Module(SQLSERVR+00005DF8)
> * 004F7294 Module(SQLSERVR+000F7294)
> * 004050F7 Module(SQLSERVR+000050F7)
> * 00409E39 Module(SQLSERVR+00009E39)
> * 00409C49 Module(SQLSERVR+00009C49)
> * 00515096 Module(SQLSERVR+00115096)
> * 00514FB7 Module(SQLSERVR+00114FB7)
> * 0050C0EB Module(SQLSERVR+0010C0EB)
> * 005100FF Module(SQLSERVR+001100FF)
> * 0050F152 Module(SQLSERVR+0010F152)
> * 00519C2D Module(SQLSERVR+00119C2D)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 9, PSS = 0x1a6b0098, EC = 0x1a6b03c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 9
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A848E0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 022FF05C: 022FF654 00980D9F 00000000 022FF660 0050FFC8 00000002
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 022FC784: 022FCBBC 00571383 022FE000 00001000 0037C000 00000000
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 022FC704: FFFFFFFF BFF831BC C1A848E0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 00571383 Module(SQLSERVR+00171383) (SQLExit+0004B903)
> * 00571315 Module(SQLSERVR+00171315) (SQLExit+0004B895)
> * 00571741 Module(SQLSERVR+00171741) (SQLExit+0004BCC1)
> * 00511A3D Module(SQLSERVR+00111A3D)
> * 0050FFC8 Module(SQLSERVR+0010FFC8)
> * 0050F152 Module(SQLSERVR+0010F152)
> * 00519C2D Module(SQLSERVR+00119C2D)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> 2004-10-20 15:27:13.69 server SQL Server is aborting. Fatal exception c0000005 caught.
>
|||Hi
The problem is solved. The client had his network card damaged
and apparently this caused problems (or something related
to the card configuration) cause after replacing it the
server started up.
I'm curious what is so important in network configuration
that could disable SQL server startup?
Hilarion
|||> Tibor Karaszi, SQL Server MVP
Thanks for your time anyway.
Hilarion
|||Hi Hilarion,
It's great to hear that it was resolved by replacing the damaged network
card. SQL Server startup need configure net library and it is entirely
possible to cause the access violation when it fails based on my experience
Anyway, to find out the root cause of this issue we may need to analyze
memory dumps, this work has to be done by contacting Microsoft Product
Support Services.
Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
MSDE installed on one of our clients PC is having problems with startup.
What could cause such problems (error log below - computer, instance
and user database names are changed to protect user information)?
Client's OS is Windows ME.
Hilarion
2004-10-20 15:27:11.88 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows 4.90 (Build 3000: )
2004-10-20 15:27:11.88 server Copyright (C) 1988-2002 Microsoft Corporation.
2004-10-20 15:27:11.88 server All rights reserved.
2004-10-20 15:27:11.88 server Server Process ID is -1747957.
2004-10-20 15:27:11.88 server Logging SQL Server messages in file 'C:\PROGRAM FILES\Microsoft SQL
Server\MSSQL$INSTANCE_NAME\LOG\ERRORLOG'.
2004-10-20 15:27:11.90 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-10-20 15:27:11.95 server SQL Server configured for thread mode processing.
2004-10-20 15:27:11.95 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-10-20 15:27:11.97 spid3 Starting up database 'master'.
2004-10-20 15:27:12.42 spid5 Starting up database 'model'.
2004-10-20 15:27:12.47 server Using 'dbghelp.dll' version '4.0.5'
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
2004-10-20 15:27:12.54 server SqlDumpExceptionHandler: Process -2094925 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:12 spid 0
*
* Exception Address = 42CF2293 (ConnectionListen + 0000107E Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address FFFFFFFF
2004-10-20 15:27:12.54 spid3 Server name is 'COMPUTER_NAME\INSTANCE_NAME'.
* 0051739E Module(SQLSERVR+0011739E)
2004-10-20 15:27:12.62 spid8 Starting up database 'msdb* BFF79391 Module(KERNEL32+00019391) (HeapCreate+0000032E)
* BFF76E3A Module(KERNEL32+00016E3A) (VirtualQueryEx+00001774)
* BFF76D37 Module(KERNEL32+00016D37) (VirtualQueryEx+00001671)
2004-10-20 15:27:12.65 spid9 Starting up database 'MY_DATABASE'.
* 0070042B Module(SQLSERVR+0030042B) (GetIMallocForMsxml+00096397)
* ----
*Dump thread - spid = 1, PSS = 0x1a5ea098, EC = 0x1a5ea3c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:12 spid 1
*
* StackDump (all)
*
*
*
* Edi: C1A822E0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 018AFC08: 018AFED0 00982517 00000000 018AFC94 00517E27 000003E8
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 018AFB98: 018AFBD0 410721D6 00E013F0 1A5EA564 018AFBD0 000003E8
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 018AFB40: FFFFFFFF BFF831BC C1A822E0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 00517E27 Module(SQLSERVR+00117E27)
* 00517DB5 Module(SQLSERVR+00117DB5)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 2, PSS = 0x1a62a098, EC = 0x1a62a3c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 2
*
* StackDump (all)
*
*
*
* Edi: C1A827E0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
* Ecx: 019EFA4C: 019EFECC 00982517 00000000 019EFA74 004017CB FFFFFFFF
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 019EF9DC: 019EFA14 410721D6 00E01280 1A62A564 019EFA14 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 019EF984: FFFFFFFF BFF831BC C1A827E0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 00516B22 Module(SQLSERVR+00116B22)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 3, PSS = 0x1a628098, EC = 0x1a6283c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 3
*
* StackDump (all)
*
*
*
* Edi: C1A82A60:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 01A8F9F4: 01A8FEC8 0097E819 00000002 01A8FED4 005196A1 00000002
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 01A8F530: 01A8F568 410721D6 00E01110 01A8F59C 01A8F568 FFFFFFFF
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 01A8F4D8: FFFFFFFF BFF831BC C1A82A60 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 41072DD9 Module(UMS+00002DD9) (UmsEvent::WaitMultiple+00000019)
* 005196A1 Module(SQLSERVR+001196A1)
* 00518066 Module(SQLSERVR+00118066)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 4, PSS = 0x1a622098, EC = 0x1a6223c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 4
*
* StackDump (all)
*
*
*
* Edi: C1A82040:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
* Ecx: 0180FDC8: 0180FE94 00982517 00000000 0180FDF0 004017CB 00001388
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 0180FD58: 0180FD90 410721D6 00E02F90 1A622564 0180FD90 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 0180FD00: FFFFFFFF BFF831BC C1A82040 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 00516F4E Module(SQLSERVR+00116F4E)
* 00516CC4 Module(SQLSERVR+00116CC4)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 5, PSS = 0x1a630098, EC = 0x1a6303c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
2004-10-20 15:27:13.48 spid5 Clearing tempdb database.
kDump (all)
*
*
*
* Edi: C1A83E80:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 01C9F484: 011420B4 00200000 00100000 01C9F4CC 00483C40 00000001
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 01C9F3D4: 01C9F418 0040C9C9 000000D0 00012000 00000000 1A6B4000
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 01C9F35C: 011420B4 00200002 00200000 01C9F374 00415052 00000004
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 0040C9C9 Module(SQLSERVR+0000C9C9)
* 00485EFA Module(SQLSERVR+00085EFA)
* 00485FF5 Module(SQLSERVR+00085FF5)
* 00483C40 Module(SQLSERVR+00083C40)
* 01C9FBA2 Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 6, PSS = 0x1a634098, EC = 0x1a6343c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 6
*
* StackDump (all)
*
*
*
* Edi: C1A82CE0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 01B2FC50: 01B2FED0 00982517 00000000 01B2FC78 004017CB FFFFFFFF
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 01B2FBE0: 01B2FC18 410721D6 00E02C90 1A634564 01B2FC18 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 01B2FB88: FFFFFFFF BFF831BC C1A82CE0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 00517249 Module(SQLSERVR+00117249)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 7, PSS = 0x1a684098, EC = 0x1a6843c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 7
*
* StackDump (all)
*
*
*
* Edi: C1A82560:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 0194FC3C: 0194FED0 00982517 00000000 0194FC64 004017CB FFFFFFFF
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 0194FBCC: 0194FC04 410721D6 00E02E20 1A684564 0194FC04 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 0194FB74: FFFFFFFF BFF831BC C1A82560 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 0051876D Module(SQLSERVR+0011876D)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 8, PSS = 0x1a6b8098, EC = 0x1a6b83c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 8
*
* StackDump (all)
*
*
*
* Edi: C1A84670:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 0225E550: 0225E64C 0097E7BA FFFFFFFF 0225E58C 0040330A 1A6B2030
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 0225E4D4: 0225E504 00440F0C 1A6F2000 00002000 0009C000 00000000
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 0225E454: FFFFFFFF BFF831BC C1A84670 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 00440F0C Module(SQLSERVR+00040F0C)
* 00441154 Module(SQLSERVR+00041154)
* 0040330A Module(SQLSERVR+0000330A)
* 00403E2F Module(SQLSERVR+00003E2F)
* 00406528 Module(SQLSERVR+00006528)
* 004061CB Module(SQLSERVR+000061CB)
* 00405DF8 Module(SQLSERVR+00005DF8)
* 004F7294 Module(SQLSERVR+000F7294)
* 004050F7 Module(SQLSERVR+000050F7)
* 00409E39 Module(SQLSERVR+00009E39)
* 00409C49 Module(SQLSERVR+00009C49)
* 00515096 Module(SQLSERVR+00115096)
* 00514FB7 Module(SQLSERVR+00114FB7)
* 0050C0EB Module(SQLSERVR+0010C0EB)
* 005100FF Module(SQLSERVR+001100FF)
* 0050F152 Module(SQLSERVR+0010F152)
* 00519C2D Module(SQLSERVR+00119C2D)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 9, PSS = 0x1a6b0098, EC = 0x1a6b03c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* ************************************************** *****************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 9
*
* StackDump (all)
*
*
*
* Edi: C1A848E0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 022FF05C: 022FF654 00980D9F 00000000 022FF660 0050FFC8 00000002
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 022FC784: 022FCBBC 00571383 022FE000 00001000 0037C000 00000000
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 022FC704: FFFFFFFF BFF831BC C1A848E0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* ************************************************** *****************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 00571383 Module(SQLSERVR+00171383) (SQLExit+0004B903)
* 00571315 Module(SQLSERVR+00171315) (SQLExit+0004B895)
* 00571741 Module(SQLSERVR+00171741) (SQLExit+0004BCC1)
* 00511A3D Module(SQLSERVR+00111A3D)
* 0050FFC8 Module(SQLSERVR+0010FFC8)
* 0050F152 Module(SQLSERVR+0010F152)
* 00519C2D Module(SQLSERVR+00119C2D)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
2004-10-20 15:27:13.69 server SQL Server is aborting. Fatal exception c0000005 caught.
Seems like SQL Server craps out when trying to recover the model database. You can search the Net
for 3607, 3608 or 3609 and see which of these makes SQL server not recover model, see if you can get
SQL server started to see if you can restore a backup of your model database. If that doesn't help,
I suggest you open a case with MS Support...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hilarion" <hilarion@.noemail.nospam> wrote in message news:e6N5rMrtEHA.3088@.tk2msftngp13.phx.gbl...
> Hi
> MSDE installed on one of our clients PC is having problems with startup.
> What could cause such problems (error log below - computer, instance
> and user database names are changed to protect user information)?
> Client's OS is Windows ME.
> Hilarion
>
> 2004-10-20 15:27:11.88 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows 4.90 (Build 3000: )
> 2004-10-20 15:27:11.88 server Copyright (C) 1988-2002 Microsoft Corporation.
> 2004-10-20 15:27:11.88 server All rights reserved.
> 2004-10-20 15:27:11.88 server Server Process ID is -1747957.
> 2004-10-20 15:27:11.88 server Logging SQL Server messages in file 'C:\PROGRAM FILES\Microsoft
> SQL Server\MSSQL$INSTANCE_NAME\LOG\ERRORLOG'.
> 2004-10-20 15:27:11.90 server SQL Server is starting at priority class 'normal'(1 CPU
> detected).
> 2004-10-20 15:27:11.95 server SQL Server configured for thread mode processing.
> 2004-10-20 15:27:11.95 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock
> Owner Blocks.
> 2004-10-20 15:27:11.97 spid3 Starting up database 'master'.
> 2004-10-20 15:27:12.42 spid5 Starting up database 'model'.
> 2004-10-20 15:27:12.47 server Using 'dbghelp.dll' version '4.0.5'
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> 2004-10-20 15:27:12.54 server SqlDumpExceptionHandler: Process -2094925 generated fatal
> exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:12 spid 0
> *
> * Exception Address = 42CF2293 (ConnectionListen + 0000107E Line 0+00000000)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address FFFFFFFF
> 2004-10-20 15:27:12.54 spid3 Server name is 'COMPUTER_NAME\INSTANCE_NAME'.
> * 0051739E Module(SQLSERVR+0011739E)
> 2004-10-20 15:27:12.62 spid8 Starting up database 'msdb* BFF79391 Module(KERNEL32+00019391)
> (HeapCreate+0000032E)
> * BFF76E3A Module(KERNEL32+00016E3A) (VirtualQueryEx+00001774)
> * BFF76D37 Module(KERNEL32+00016D37) (VirtualQueryEx+00001671)
> 2004-10-20 15:27:12.65 spid9 Starting up database 'MY_DATABASE'.
> * 0070042B Module(SQLSERVR+0030042B) (GetIMallocForMsxml+00096397)
> * ----
> *Dump thread - spid = 1, PSS = 0x1a5ea098, EC = 0x1a5ea3c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:12 spid 1
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A822E0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 018AFC08: 018AFED0 00982517 00000000 018AFC94 00517E27 000003E8
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 018AFB98: 018AFBD0 410721D6 00E013F0 1A5EA564 018AFBD0 000003E8
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 018AFB40: FFFFFFFF BFF831BC C1A822E0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 00517E27 Module(SQLSERVR+00117E27)
> * 00517DB5 Module(SQLSERVR+00117DB5)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 2, PSS = 0x1a62a098, EC = 0x1a62a3c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 2
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A827E0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
> * Ecx: 019EFA4C: 019EFECC 00982517 00000000 019EFA74 004017CB FFFFFFFF
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 019EF9DC: 019EFA14 410721D6 00E01280 1A62A564 019EFA14 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 019EF984: FFFFFFFF BFF831BC C1A827E0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 00516B22 Module(SQLSERVR+00116B22)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 3, PSS = 0x1a628098, EC = 0x1a6283c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 3
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82A60:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 01A8F9F4: 01A8FEC8 0097E819 00000002 01A8FED4 005196A1 00000002
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 01A8F530: 01A8F568 410721D6 00E01110 01A8F59C 01A8F568 FFFFFFFF
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 01A8F4D8: FFFFFFFF BFF831BC C1A82A60 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 41072DD9 Module(UMS+00002DD9) (UmsEvent::WaitMultiple+00000019)
> * 005196A1 Module(SQLSERVR+001196A1)
> * 00518066 Module(SQLSERVR+00118066)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 4, PSS = 0x1a622098, EC = 0x1a6223c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 4
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82040:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
> * Ecx: 0180FDC8: 0180FE94 00982517 00000000 0180FDF0 004017CB 00001388
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 0180FD58: 0180FD90 410721D6 00E02F90 1A622564 0180FD90 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 0180FD00: FFFFFFFF BFF831BC C1A82040 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 00516F4E Module(SQLSERVR+00116F4E)
> * 00516CC4 Module(SQLSERVR+00116CC4)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 5, PSS = 0x1a630098, EC = 0x1a6303c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> 2004-10-20 15:27:13.48 spid5 Clearing tempdb database.
> kDump (all)
> *
> *
> *
> * Edi: C1A83E80:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 01C9F484: 011420B4 00200000 00100000 01C9F4CC 00483C40 00000001
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 01C9F3D4: 01C9F418 0040C9C9 000000D0 00012000 00000000 1A6B4000
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 01C9F35C: 011420B4 00200002 00200000 01C9F374 00415052 00000004
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 0040C9C9 Module(SQLSERVR+0000C9C9)
> * 00485EFA Module(SQLSERVR+00085EFA)
> * 00485FF5 Module(SQLSERVR+00085FF5)
> * 00483C40 Module(SQLSERVR+00083C40)
> * 01C9FBA2 Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 6, PSS = 0x1a634098, EC = 0x1a6343c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 6
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82CE0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 01B2FC50: 01B2FED0 00982517 00000000 01B2FC78 004017CB FFFFFFFF
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 01B2FBE0: 01B2FC18 410721D6 00E02C90 1A634564 01B2FC18 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 01B2FB88: FFFFFFFF BFF831BC C1A82CE0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 00517249 Module(SQLSERVR+00117249)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 7, PSS = 0x1a684098, EC = 0x1a6843c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 7
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82560:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 0194FC3C: 0194FED0 00982517 00000000 0194FC64 004017CB FFFFFFFF
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 0194FBCC: 0194FC04 410721D6 00E02E20 1A684564 0194FC04 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 0194FB74: FFFFFFFF BFF831BC C1A82560 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 0051876D Module(SQLSERVR+0011876D)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 8, PSS = 0x1a6b8098, EC = 0x1a6b83c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 8
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A84670:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 0225E550: 0225E64C 0097E7BA FFFFFFFF 0225E58C 0040330A 1A6B2030
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 0225E4D4: 0225E504 00440F0C 1A6F2000 00002000 0009C000 00000000
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 0225E454: FFFFFFFF BFF831BC C1A84670 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 00440F0C Module(SQLSERVR+00040F0C)
> * 00441154 Module(SQLSERVR+00041154)
> * 0040330A Module(SQLSERVR+0000330A)
> * 00403E2F Module(SQLSERVR+00003E2F)
> * 00406528 Module(SQLSERVR+00006528)
> * 004061CB Module(SQLSERVR+000061CB)
> * 00405DF8 Module(SQLSERVR+00005DF8)
> * 004F7294 Module(SQLSERVR+000F7294)
> * 004050F7 Module(SQLSERVR+000050F7)
> * 00409E39 Module(SQLSERVR+00009E39)
> * 00409C49 Module(SQLSERVR+00009C49)
> * 00515096 Module(SQLSERVR+00115096)
> * 00514FB7 Module(SQLSERVR+00114FB7)
> * 0050C0EB Module(SQLSERVR+0010C0EB)
> * 005100FF Module(SQLSERVR+001100FF)
> * 0050F152 Module(SQLSERVR+0010F152)
> * 00519C2D Module(SQLSERVR+00119C2D)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 9, PSS = 0x1a6b0098, EC = 0x1a6b03c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * ************************************************** *****************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 9
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A848E0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 022FF05C: 022FF654 00980D9F 00000000 022FF660 0050FFC8 00000002
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 022FC784: 022FCBBC 00571383 022FE000 00001000 0037C000 00000000
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 022FC704: FFFFFFFF BFF831BC C1A848E0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * ************************************************** *****************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 00571383 Module(SQLSERVR+00171383) (SQLExit+0004B903)
> * 00571315 Module(SQLSERVR+00171315) (SQLExit+0004B895)
> * 00571741 Module(SQLSERVR+00171741) (SQLExit+0004BCC1)
> * 00511A3D Module(SQLSERVR+00111A3D)
> * 0050FFC8 Module(SQLSERVR+0010FFC8)
> * 0050F152 Module(SQLSERVR+0010F152)
> * 00519C2D Module(SQLSERVR+00119C2D)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> 2004-10-20 15:27:13.69 server SQL Server is aborting. Fatal exception c0000005 caught.
>
|||Hi
The problem is solved. The client had his network card damaged
and apparently this caused problems (or something related
to the card configuration) cause after replacing it the
server started up.
I'm curious what is so important in network configuration
that could disable SQL server startup?
Hilarion
|||> Tibor Karaszi, SQL Server MVP
Thanks for your time anyway.
Hilarion
|||Hi Hilarion,
It's great to hear that it was resolved by replacing the damaged network
card. SQL Server startup need configure net library and it is entirely
possible to cause the access violation when it fails based on my experience
Anyway, to find out the root cause of this issue we may need to analyze
memory dumps, this work has to be done by contacting Microsoft Product
Support Services.
Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
MSDE startup problem
Hi
MSDE installed on one of our clients PC is having problems with startup.
What could cause such problems (error log below - computer, instance
and user database names are changed to protect user information)?
Client's OS is Windows ME.
Hilarion
2004-10-20 15:27:11.88 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows 4.90 (Build 3000: )
2004-10-20 15:27:11.88 server Copyright (C) 1988-2002 Microsoft Corporation.
2004-10-20 15:27:11.88 server All rights reserved.
2004-10-20 15:27:11.88 server Server Process ID is -1747957.
2004-10-20 15:27:11.88 server Logging SQL Server messages in file 'C:\PROGRAM FILES\Microsoft SQL
Server\MSSQL$INSTANCE_NAME\LOG\ERRORLOG'.
2004-10-20 15:27:11.90 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-10-20 15:27:11.95 server SQL Server configured for thread mode processing.
2004-10-20 15:27:11.95 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-10-20 15:27:11.97 spid3 Starting up database 'master'.
2004-10-20 15:27:12.42 spid5 Starting up database 'model'.
2004-10-20 15:27:12.47 server Using 'dbghelp.dll' version '4.0.5'
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
2004-10-20 15:27:12.54 server SqlDumpExceptionHandler: Process -2094925 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:12 spid 0
*
* Exception Address = 42CF2293 (ConnectionListen + 0000107E Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address FFFFFFFF
2004-10-20 15:27:12.54 spid3 Server name is 'COMPUTER_NAME\INSTANCE_NAME'.
* 0051739E Module(SQLSERVR+0011739E)
2004-10-20 15:27:12.62 spid8 Starting up database 'msdb* BFF79391 Module(KERNEL32+00019391) (HeapCreate+0000032E)
* BFF76E3A Module(KERNEL32+00016E3A) (VirtualQueryEx+00001774)
* BFF76D37 Module(KERNEL32+00016D37) (VirtualQueryEx+00001671)
2004-10-20 15:27:12.65 spid9 Starting up database 'MY_DATABASE'.
* 0070042B Module(SQLSERVR+0030042B) (GetIMallocForMsxml+00096397)
* ----
*Dump thread - spid = 1, PSS = 0x1a5ea098, EC = 0x1a5ea3c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:12 spid 1
*
* StackDump (all)
*
*
*
* Edi: C1A822E0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 018AFC08: 018AFED0 00982517 00000000 018AFC94 00517E27 000003E8
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 018AFB98: 018AFBD0 410721D6 00E013F0 1A5EA564 018AFBD0 000003E8
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 018AFB40: FFFFFFFF BFF831BC C1A822E0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 00517E27 Module(SQLSERVR+00117E27)
* 00517DB5 Module(SQLSERVR+00117DB5)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 2, PSS = 0x1a62a098, EC = 0x1a62a3c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 2
*
* StackDump (all)
*
*
*
* Edi: C1A827E0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
* Ecx: 019EFA4C: 019EFECC 00982517 00000000 019EFA74 004017CB FFFFFFFF
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 019EF9DC: 019EFA14 410721D6 00E01280 1A62A564 019EFA14 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 019EF984: FFFFFFFF BFF831BC C1A827E0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 00516B22 Module(SQLSERVR+00116B22)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 3, PSS = 0x1a628098, EC = 0x1a6283c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 3
*
* StackDump (all)
*
*
*
* Edi: C1A82A60:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 01A8F9F4: 01A8FEC8 0097E819 00000002 01A8FED4 005196A1 00000002
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 01A8F530: 01A8F568 410721D6 00E01110 01A8F59C 01A8F568 FFFFFFFF
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 01A8F4D8: FFFFFFFF BFF831BC C1A82A60 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 41072DD9 Module(UMS+00002DD9) (UmsEvent::WaitMultiple+00000019)
* 005196A1 Module(SQLSERVR+001196A1)
* 00518066 Module(SQLSERVR+00118066)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 4, PSS = 0x1a622098, EC = 0x1a6223c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 4
*
* StackDump (all)
*
*
*
* Edi: C1A82040:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
* Ecx: 0180FDC8: 0180FE94 00982517 00000000 0180FDF0 004017CB 00001388
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 0180FD58: 0180FD90 410721D6 00E02F90 1A622564 0180FD90 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 0180FD00: FFFFFFFF BFF831BC C1A82040 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 00516F4E Module(SQLSERVR+00116F4E)
* 00516CC4 Module(SQLSERVR+00116CC4)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 5, PSS = 0x1a630098, EC = 0x1a6303c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
2004-10-20 15:27:13.48 spid5 Clearing tempdb database.
kDump (all)
*
*
*
* Edi: C1A83E80:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 01C9F484: 011420B4 00200000 00100000 01C9F4CC 00483C40 00000001
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 01C9F3D4: 01C9F418 0040C9C9 000000D0 00012000 00000000 1A6B4000
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 01C9F35C: 011420B4 00200002 00200000 01C9F374 00415052 00000004
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 0040C9C9 Module(SQLSERVR+0000C9C9)
* 00485EFA Module(SQLSERVR+00085EFA)
* 00485FF5 Module(SQLSERVR+00085FF5)
* 00483C40 Module(SQLSERVR+00083C40)
* 01C9FBA2 Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 6, PSS = 0x1a634098, EC = 0x1a6343c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 6
*
* StackDump (all)
*
*
*
* Edi: C1A82CE0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 01B2FC50: 01B2FED0 00982517 00000000 01B2FC78 004017CB FFFFFFFF
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 01B2FBE0: 01B2FC18 410721D6 00E02C90 1A634564 01B2FC18 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 01B2FB88: FFFFFFFF BFF831BC C1A82CE0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 00517249 Module(SQLSERVR+00117249)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 7, PSS = 0x1a684098, EC = 0x1a6843c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 7
*
* StackDump (all)
*
*
*
* Edi: C1A82560:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 0194FC3C: 0194FED0 00982517 00000000 0194FC64 004017CB FFFFFFFF
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 0194FBCC: 0194FC04 410721D6 00E02E20 1A684564 0194FC04 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 0194FB74: FFFFFFFF BFF831BC C1A82560 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 0051876D Module(SQLSERVR+0011876D)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 8, PSS = 0x1a6b8098, EC = 0x1a6b83c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 8
*
* StackDump (all)
*
*
*
* Edi: C1A84670:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 0225E550: 0225E64C 0097E7BA FFFFFFFF 0225E58C 0040330A 1A6B2030
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 0225E4D4: 0225E504 00440F0C 1A6F2000 00002000 0009C000 00000000
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 0225E454: FFFFFFFF BFF831BC C1A84670 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 00440F0C Module(SQLSERVR+00040F0C)
* 00441154 Module(SQLSERVR+00041154)
* 0040330A Module(SQLSERVR+0000330A)
* 00403E2F Module(SQLSERVR+00003E2F)
* 00406528 Module(SQLSERVR+00006528)
* 004061CB Module(SQLSERVR+000061CB)
* 00405DF8 Module(SQLSERVR+00005DF8)
* 004F7294 Module(SQLSERVR+000F7294)
* 004050F7 Module(SQLSERVR+000050F7)
* 00409E39 Module(SQLSERVR+00009E39)
* 00409C49 Module(SQLSERVR+00009C49)
* 00515096 Module(SQLSERVR+00115096)
* 00514FB7 Module(SQLSERVR+00114FB7)
* 0050C0EB Module(SQLSERVR+0010C0EB)
* 005100FF Module(SQLSERVR+001100FF)
* 0050F152 Module(SQLSERVR+0010F152)
* 00519C2D Module(SQLSERVR+00119C2D)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 9, PSS = 0x1a6b0098, EC = 0x1a6b03c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 9
*
* StackDump (all)
*
*
*
* Edi: C1A848E0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 022FF05C: 022FF654 00980D9F 00000000 022FF660 0050FFC8 00000002
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 022FC784: 022FCBBC 00571383 022FE000 00001000 0037C000 00000000
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 022FC704: FFFFFFFF BFF831BC C1A848E0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 00571383 Module(SQLSERVR+00171383) (SQLExit+0004B903)
* 00571315 Module(SQLSERVR+00171315) (SQLExit+0004B895)
* 00571741 Module(SQLSERVR+00171741) (SQLExit+0004BCC1)
* 00511A3D Module(SQLSERVR+00111A3D)
* 0050FFC8 Module(SQLSERVR+0010FFC8)
* 0050F152 Module(SQLSERVR+0010F152)
* 00519C2D Module(SQLSERVR+00119C2D)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
2004-10-20 15:27:13.69 server SQL Server is aborting. Fatal exception c0000005 caught.Seems like SQL Server craps out when trying to recover the model database. You can search the Net
for 3607, 3608 or 3609 and see which of these makes SQL server not recover model, see if you can get
SQL server started to see if you can restore a backup of your model database. If that doesn't help,
I suggest you open a case with MS Support...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hilarion" <hilarion@.noemail.nospam> wrote in message news:e6N5rMrtEHA.3088@.tk2msftngp13.phx.gbl...
> Hi
> MSDE installed on one of our clients PC is having problems with startup.
> What could cause such problems (error log below - computer, instance
> and user database names are changed to protect user information)?
> Client's OS is Windows ME.
> Hilarion
>
> 2004-10-20 15:27:11.88 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows 4.90 (Build 3000: )
> 2004-10-20 15:27:11.88 server Copyright (C) 1988-2002 Microsoft Corporation.
> 2004-10-20 15:27:11.88 server All rights reserved.
> 2004-10-20 15:27:11.88 server Server Process ID is -1747957.
> 2004-10-20 15:27:11.88 server Logging SQL Server messages in file 'C:\PROGRAM FILES\Microsoft
> SQL Server\MSSQL$INSTANCE_NAME\LOG\ERRORLOG'.
> 2004-10-20 15:27:11.90 server SQL Server is starting at priority class 'normal'(1 CPU
> detected).
> 2004-10-20 15:27:11.95 server SQL Server configured for thread mode processing.
> 2004-10-20 15:27:11.95 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock
> Owner Blocks.
> 2004-10-20 15:27:11.97 spid3 Starting up database 'master'.
> 2004-10-20 15:27:12.42 spid5 Starting up database 'model'.
> 2004-10-20 15:27:12.47 server Using 'dbghelp.dll' version '4.0.5'
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> 2004-10-20 15:27:12.54 server SqlDumpExceptionHandler: Process -2094925 generated fatal
> exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:12 spid 0
> *
> * Exception Address = 42CF2293 (ConnectionListen + 0000107E Line 0+00000000)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address FFFFFFFF
> 2004-10-20 15:27:12.54 spid3 Server name is 'COMPUTER_NAME\INSTANCE_NAME'.
> * 0051739E Module(SQLSERVR+0011739E)
> 2004-10-20 15:27:12.62 spid8 Starting up database 'msdb* BFF79391 Module(KERNEL32+00019391)
> (HeapCreate+0000032E)
> * BFF76E3A Module(KERNEL32+00016E3A) (VirtualQueryEx+00001774)
> * BFF76D37 Module(KERNEL32+00016D37) (VirtualQueryEx+00001671)
> 2004-10-20 15:27:12.65 spid9 Starting up database 'MY_DATABASE'.
> * 0070042B Module(SQLSERVR+0030042B) (GetIMallocForMsxml+00096397)
> * ----
> *Dump thread - spid = 1, PSS = 0x1a5ea098, EC = 0x1a5ea3c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:12 spid 1
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A822E0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 018AFC08: 018AFED0 00982517 00000000 018AFC94 00517E27 000003E8
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 018AFB98: 018AFBD0 410721D6 00E013F0 1A5EA564 018AFBD0 000003E8
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 018AFB40: FFFFFFFF BFF831BC C1A822E0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 00517E27 Module(SQLSERVR+00117E27)
> * 00517DB5 Module(SQLSERVR+00117DB5)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 2, PSS = 0x1a62a098, EC = 0x1a62a3c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 2
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A827E0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
> * Ecx: 019EFA4C: 019EFECC 00982517 00000000 019EFA74 004017CB FFFFFFFF
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 019EF9DC: 019EFA14 410721D6 00E01280 1A62A564 019EFA14 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 019EF984: FFFFFFFF BFF831BC C1A827E0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 00516B22 Module(SQLSERVR+00116B22)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 3, PSS = 0x1a628098, EC = 0x1a6283c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 3
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82A60:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 01A8F9F4: 01A8FEC8 0097E819 00000002 01A8FED4 005196A1 00000002
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 01A8F530: 01A8F568 410721D6 00E01110 01A8F59C 01A8F568 FFFFFFFF
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 01A8F4D8: FFFFFFFF BFF831BC C1A82A60 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 41072DD9 Module(UMS+00002DD9) (UmsEvent::WaitMultiple+00000019)
> * 005196A1 Module(SQLSERVR+001196A1)
> * 00518066 Module(SQLSERVR+00118066)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 4, PSS = 0x1a622098, EC = 0x1a6223c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 4
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82040:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
> * Ecx: 0180FDC8: 0180FE94 00982517 00000000 0180FDF0 004017CB 00001388
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 0180FD58: 0180FD90 410721D6 00E02F90 1A622564 0180FD90 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 0180FD00: FFFFFFFF BFF831BC C1A82040 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 00516F4E Module(SQLSERVR+00116F4E)
> * 00516CC4 Module(SQLSERVR+00116CC4)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 5, PSS = 0x1a630098, EC = 0x1a6303c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> 2004-10-20 15:27:13.48 spid5 Clearing tempdb database.
> kDump (all)
> *
> *
> *
> * Edi: C1A83E80:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 01C9F484: 011420B4 00200000 00100000 01C9F4CC 00483C40 00000001
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 01C9F3D4: 01C9F418 0040C9C9 000000D0 00012000 00000000 1A6B4000
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 01C9F35C: 011420B4 00200002 00200000 01C9F374 00415052 00000004
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 0040C9C9 Module(SQLSERVR+0000C9C9)
> * 00485EFA Module(SQLSERVR+00085EFA)
> * 00485FF5 Module(SQLSERVR+00085FF5)
> * 00483C40 Module(SQLSERVR+00083C40)
> * 01C9FBA2 Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 6, PSS = 0x1a634098, EC = 0x1a6343c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 6
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82CE0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 01B2FC50: 01B2FED0 00982517 00000000 01B2FC78 004017CB FFFFFFFF
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 01B2FBE0: 01B2FC18 410721D6 00E02C90 1A634564 01B2FC18 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 01B2FB88: FFFFFFFF BFF831BC C1A82CE0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 00517249 Module(SQLSERVR+00117249)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 7, PSS = 0x1a684098, EC = 0x1a6843c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 7
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82560:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 0194FC3C: 0194FED0 00982517 00000000 0194FC64 004017CB FFFFFFFF
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 0194FBCC: 0194FC04 410721D6 00E02E20 1A684564 0194FC04 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 0194FB74: FFFFFFFF BFF831BC C1A82560 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 0051876D Module(SQLSERVR+0011876D)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 8, PSS = 0x1a6b8098, EC = 0x1a6b83c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 8
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A84670:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 0225E550: 0225E64C 0097E7BA FFFFFFFF 0225E58C 0040330A 1A6B2030
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 0225E4D4: 0225E504 00440F0C 1A6F2000 00002000 0009C000 00000000
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 0225E454: FFFFFFFF BFF831BC C1A84670 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 00440F0C Module(SQLSERVR+00040F0C)
> * 00441154 Module(SQLSERVR+00041154)
> * 0040330A Module(SQLSERVR+0000330A)
> * 00403E2F Module(SQLSERVR+00003E2F)
> * 00406528 Module(SQLSERVR+00006528)
> * 004061CB Module(SQLSERVR+000061CB)
> * 00405DF8 Module(SQLSERVR+00005DF8)
> * 004F7294 Module(SQLSERVR+000F7294)
> * 004050F7 Module(SQLSERVR+000050F7)
> * 00409E39 Module(SQLSERVR+00009E39)
> * 00409C49 Module(SQLSERVR+00009C49)
> * 00515096 Module(SQLSERVR+00115096)
> * 00514FB7 Module(SQLSERVR+00114FB7)
> * 0050C0EB Module(SQLSERVR+0010C0EB)
> * 005100FF Module(SQLSERVR+001100FF)
> * 0050F152 Module(SQLSERVR+0010F152)
> * 00519C2D Module(SQLSERVR+00119C2D)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 9, PSS = 0x1a6b0098, EC = 0x1a6b03c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 9
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A848E0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 022FF05C: 022FF654 00980D9F 00000000 022FF660 0050FFC8 00000002
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 022FC784: 022FCBBC 00571383 022FE000 00001000 0037C000 00000000
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 022FC704: FFFFFFFF BFF831BC C1A848E0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 00571383 Module(SQLSERVR+00171383) (SQLExit+0004B903)
> * 00571315 Module(SQLSERVR+00171315) (SQLExit+0004B895)
> * 00571741 Module(SQLSERVR+00171741) (SQLExit+0004BCC1)
> * 00511A3D Module(SQLSERVR+00111A3D)
> * 0050FFC8 Module(SQLSERVR+0010FFC8)
> * 0050F152 Module(SQLSERVR+0010F152)
> * 00519C2D Module(SQLSERVR+00119C2D)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> 2004-10-20 15:27:13.69 server SQL Server is aborting. Fatal exception c0000005 caught.
>|||Hi
The problem is solved. The client had his network card damaged
and apparently this caused problems (or something related
to the card configuration) cause after replacing it the
server started up.
I'm curious what is so important in network configuration
that could disable SQL server startup?
Hilarion|||> Tibor Karaszi, SQL Server MVP
Thanks for your time anyway.
Hilarion|||Hi Hilarion,
It's great to hear that it was resolved by replacing the damaged network
card. SQL Server startup need configure net library and it is entirely
possible to cause the access violation when it fails based on my experience
Anyway, to find out the root cause of this issue we may need to analyze
memory dumps, this work has to be done by contacting Microsoft Product
Support Services.
Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
MSDE installed on one of our clients PC is having problems with startup.
What could cause such problems (error log below - computer, instance
and user database names are changed to protect user information)?
Client's OS is Windows ME.
Hilarion
2004-10-20 15:27:11.88 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows 4.90 (Build 3000: )
2004-10-20 15:27:11.88 server Copyright (C) 1988-2002 Microsoft Corporation.
2004-10-20 15:27:11.88 server All rights reserved.
2004-10-20 15:27:11.88 server Server Process ID is -1747957.
2004-10-20 15:27:11.88 server Logging SQL Server messages in file 'C:\PROGRAM FILES\Microsoft SQL
Server\MSSQL$INSTANCE_NAME\LOG\ERRORLOG'.
2004-10-20 15:27:11.90 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-10-20 15:27:11.95 server SQL Server configured for thread mode processing.
2004-10-20 15:27:11.95 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-10-20 15:27:11.97 spid3 Starting up database 'master'.
2004-10-20 15:27:12.42 spid5 Starting up database 'model'.
2004-10-20 15:27:12.47 server Using 'dbghelp.dll' version '4.0.5'
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
2004-10-20 15:27:12.54 server SqlDumpExceptionHandler: Process -2094925 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:12 spid 0
*
* Exception Address = 42CF2293 (ConnectionListen + 0000107E Line 0+00000000)
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address FFFFFFFF
2004-10-20 15:27:12.54 spid3 Server name is 'COMPUTER_NAME\INSTANCE_NAME'.
* 0051739E Module(SQLSERVR+0011739E)
2004-10-20 15:27:12.62 spid8 Starting up database 'msdb* BFF79391 Module(KERNEL32+00019391) (HeapCreate+0000032E)
* BFF76E3A Module(KERNEL32+00016E3A) (VirtualQueryEx+00001774)
* BFF76D37 Module(KERNEL32+00016D37) (VirtualQueryEx+00001671)
2004-10-20 15:27:12.65 spid9 Starting up database 'MY_DATABASE'.
* 0070042B Module(SQLSERVR+0030042B) (GetIMallocForMsxml+00096397)
* ----
*Dump thread - spid = 1, PSS = 0x1a5ea098, EC = 0x1a5ea3c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:12 spid 1
*
* StackDump (all)
*
*
*
* Edi: C1A822E0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 018AFC08: 018AFED0 00982517 00000000 018AFC94 00517E27 000003E8
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 018AFB98: 018AFBD0 410721D6 00E013F0 1A5EA564 018AFBD0 000003E8
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 018AFB40: FFFFFFFF BFF831BC C1A822E0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 00517E27 Module(SQLSERVR+00117E27)
* 00517DB5 Module(SQLSERVR+00117DB5)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 2, PSS = 0x1a62a098, EC = 0x1a62a3c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 2
*
* StackDump (all)
*
*
*
* Edi: C1A827E0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
* Ecx: 019EFA4C: 019EFECC 00982517 00000000 019EFA74 004017CB FFFFFFFF
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 019EF9DC: 019EFA14 410721D6 00E01280 1A62A564 019EFA14 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 019EF984: FFFFFFFF BFF831BC C1A827E0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 00516B22 Module(SQLSERVR+00116B22)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 3, PSS = 0x1a628098, EC = 0x1a6283c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 3
*
* StackDump (all)
*
*
*
* Edi: C1A82A60:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 01A8F9F4: 01A8FEC8 0097E819 00000002 01A8FED4 005196A1 00000002
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 01A8F530: 01A8F568 410721D6 00E01110 01A8F59C 01A8F568 FFFFFFFF
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 01A8F4D8: FFFFFFFF BFF831BC C1A82A60 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 41072DD9 Module(UMS+00002DD9) (UmsEvent::WaitMultiple+00000019)
* 005196A1 Module(SQLSERVR+001196A1)
* 00518066 Module(SQLSERVR+00118066)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 4, PSS = 0x1a622098, EC = 0x1a6223c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 4
*
* StackDump (all)
*
*
*
* Edi: C1A82040:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
* Ecx: 0180FDC8: 0180FE94 00982517 00000000 0180FDF0 004017CB 00001388
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 0180FD58: 0180FD90 410721D6 00E02F90 1A622564 0180FD90 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 0180FD00: FFFFFFFF BFF831BC C1A82040 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 00516F4E Module(SQLSERVR+00116F4E)
* 00516CC4 Module(SQLSERVR+00116CC4)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 5, PSS = 0x1a630098, EC = 0x1a6303c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
2004-10-20 15:27:13.48 spid5 Clearing tempdb database.
kDump (all)
*
*
*
* Edi: C1A83E80:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 01C9F484: 011420B4 00200000 00100000 01C9F4CC 00483C40 00000001
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 01C9F3D4: 01C9F418 0040C9C9 000000D0 00012000 00000000 1A6B4000
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 01C9F35C: 011420B4 00200002 00200000 01C9F374 00415052 00000004
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 0040C9C9 Module(SQLSERVR+0000C9C9)
* 00485EFA Module(SQLSERVR+00085EFA)
* 00485FF5 Module(SQLSERVR+00085FF5)
* 00483C40 Module(SQLSERVR+00083C40)
* 01C9FBA2 Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 6, PSS = 0x1a634098, EC = 0x1a6343c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 6
*
* StackDump (all)
*
*
*
* Edi: C1A82CE0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 01B2FC50: 01B2FED0 00982517 00000000 01B2FC78 004017CB FFFFFFFF
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 01B2FBE0: 01B2FC18 410721D6 00E02C90 1A634564 01B2FC18 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 01B2FB88: FFFFFFFF BFF831BC C1A82CE0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 00517249 Module(SQLSERVR+00117249)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 7, PSS = 0x1a684098, EC = 0x1a6843c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 7
*
* StackDump (all)
*
*
*
* Edi: C1A82560:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 0194FC3C: 0194FED0 00982517 00000000 0194FC64 004017CB FFFFFFFF
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 0194FBCC: 0194FC04 410721D6 00E02E20 1A684564 0194FC04 000007D0
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 0194FB74: FFFFFFFF BFF831BC C1A82560 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
* 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
* 004017CB Module(SQLSERVR+000017CB)
* 00401662 Module(SQLSERVR+00001662)
* 0051876D Module(SQLSERVR+0011876D)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 8, PSS = 0x1a6b8098, EC = 0x1a6b83c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 8
*
* StackDump (all)
*
*
*
* Edi: C1A84670:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 0225E550: 0225E64C 0097E7BA FFFFFFFF 0225E58C 0040330A 1A6B2030
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 0225E4D4: 0225E504 00440F0C 1A6F2000 00002000 0009C000 00000000
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 0225E454: FFFFFFFF BFF831BC C1A84670 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 00440F0C Module(SQLSERVR+00040F0C)
* 00441154 Module(SQLSERVR+00041154)
* 0040330A Module(SQLSERVR+0000330A)
* 00403E2F Module(SQLSERVR+00003E2F)
* 00406528 Module(SQLSERVR+00006528)
* 004061CB Module(SQLSERVR+000061CB)
* 00405DF8 Module(SQLSERVR+00005DF8)
* 004F7294 Module(SQLSERVR+000F7294)
* 004050F7 Module(SQLSERVR+000050F7)
* 00409E39 Module(SQLSERVR+00009E39)
* 00409C49 Module(SQLSERVR+00009C49)
* 00515096 Module(SQLSERVR+00115096)
* 00514FB7 Module(SQLSERVR+00114FB7)
* 0050C0EB Module(SQLSERVR+0010C0EB)
* 005100FF Module(SQLSERVR+001100FF)
* 0050F152 Module(SQLSERVR+0010F152)
* 00519C2D Module(SQLSERVR+00119C2D)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
*Dump thread - spid = 9, PSS = 0x1a6b0098, EC = 0x1a6b03c0
*Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 10/20/04 15:27:13 spid 9
*
* StackDump (all)
*
*
*
* Edi: C1A848E0:
* Esi: 00000001:
* Eax: 002A005C:
* Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
* Ecx: 022FF05C: 022FF654 00980D9F 00000000 022FF660 0050FFC8 00000002
* Edx: 00000100:
* Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
* Ebp: 022FC784: 022FCBBC 00571383 022FE000 00001000 0037C000 00000000
* SegCs: 0000019F:
* EFlags: 00000246:
* Esp: 022FC704: FFFFFFFF BFF831BC C1A848E0 FFFFFFFF 00000001 BFF8318C
* SegSs: 000001A7:
* *******************************************************************************
* ----
* Short Stack Dump
* BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
* 00571383 Module(SQLSERVR+00171383) (SQLExit+0004B903)
* 00571315 Module(SQLSERVR+00171315) (SQLExit+0004B895)
* 00571741 Module(SQLSERVR+00171741) (SQLExit+0004BCC1)
* 00511A3D Module(SQLSERVR+00111A3D)
* 0050FFC8 Module(SQLSERVR+0010FFC8)
* 0050F152 Module(SQLSERVR+0010F152)
* 00519C2D Module(SQLSERVR+00119C2D)
* 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
* 542868FF Module(UNKNOWN+00000000)
* ----
2004-10-20 15:27:13.69 server SQL Server is aborting. Fatal exception c0000005 caught.Seems like SQL Server craps out when trying to recover the model database. You can search the Net
for 3607, 3608 or 3609 and see which of these makes SQL server not recover model, see if you can get
SQL server started to see if you can restore a backup of your model database. If that doesn't help,
I suggest you open a case with MS Support...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Hilarion" <hilarion@.noemail.nospam> wrote in message news:e6N5rMrtEHA.3088@.tk2msftngp13.phx.gbl...
> Hi
> MSDE installed on one of our clients PC is having problems with startup.
> What could cause such problems (error log below - computer, instance
> and user database names are changed to protect user information)?
> Client's OS is Windows ME.
> Hilarion
>
> 2004-10-20 15:27:11.88 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows 4.90 (Build 3000: )
> 2004-10-20 15:27:11.88 server Copyright (C) 1988-2002 Microsoft Corporation.
> 2004-10-20 15:27:11.88 server All rights reserved.
> 2004-10-20 15:27:11.88 server Server Process ID is -1747957.
> 2004-10-20 15:27:11.88 server Logging SQL Server messages in file 'C:\PROGRAM FILES\Microsoft
> SQL Server\MSSQL$INSTANCE_NAME\LOG\ERRORLOG'.
> 2004-10-20 15:27:11.90 server SQL Server is starting at priority class 'normal'(1 CPU
> detected).
> 2004-10-20 15:27:11.95 server SQL Server configured for thread mode processing.
> 2004-10-20 15:27:11.95 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock
> Owner Blocks.
> 2004-10-20 15:27:11.97 spid3 Starting up database 'master'.
> 2004-10-20 15:27:12.42 spid5 Starting up database 'model'.
> 2004-10-20 15:27:12.47 server Using 'dbghelp.dll' version '4.0.5'
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> 2004-10-20 15:27:12.54 server SqlDumpExceptionHandler: Process -2094925 generated fatal
> exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:12 spid 0
> *
> * Exception Address = 42CF2293 (ConnectionListen + 0000107E Line 0+00000000)
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address FFFFFFFF
> 2004-10-20 15:27:12.54 spid3 Server name is 'COMPUTER_NAME\INSTANCE_NAME'.
> * 0051739E Module(SQLSERVR+0011739E)
> 2004-10-20 15:27:12.62 spid8 Starting up database 'msdb* BFF79391 Module(KERNEL32+00019391)
> (HeapCreate+0000032E)
> * BFF76E3A Module(KERNEL32+00016E3A) (VirtualQueryEx+00001774)
> * BFF76D37 Module(KERNEL32+00016D37) (VirtualQueryEx+00001671)
> 2004-10-20 15:27:12.65 spid9 Starting up database 'MY_DATABASE'.
> * 0070042B Module(SQLSERVR+0030042B) (GetIMallocForMsxml+00096397)
> * ----
> *Dump thread - spid = 1, PSS = 0x1a5ea098, EC = 0x1a5ea3c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:12 spid 1
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A822E0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 018AFC08: 018AFED0 00982517 00000000 018AFC94 00517E27 000003E8
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 018AFB98: 018AFBD0 410721D6 00E013F0 1A5EA564 018AFBD0 000003E8
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 018AFB40: FFFFFFFF BFF831BC C1A822E0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 00517E27 Module(SQLSERVR+00117E27)
> * 00517DB5 Module(SQLSERVR+00117DB5)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 2, PSS = 0x1a62a098, EC = 0x1a62a3c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 2
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A827E0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
> * Ecx: 019EFA4C: 019EFECC 00982517 00000000 019EFA74 004017CB FFFFFFFF
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 019EF9DC: 019EFA14 410721D6 00E01280 1A62A564 019EFA14 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 019EF984: FFFFFFFF BFF831BC C1A827E0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 00516B22 Module(SQLSERVR+00116B22)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 3, PSS = 0x1a628098, EC = 0x1a6283c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 3
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82A60:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 01A8F9F4: 01A8FEC8 0097E819 00000002 01A8FED4 005196A1 00000002
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 01A8F530: 01A8F568 410721D6 00E01110 01A8F59C 01A8F568 FFFFFFFF
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 01A8F4D8: FFFFFFFF BFF831BC C1A82A60 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 41072DD9 Module(UMS+00002DD9) (UmsEvent::WaitMultiple+00000019)
> * 005196A1 Module(SQLSERVR+001196A1)
> * 00518066 Module(SQLSERVR+00118066)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 4, PSS = 0x1a622098, EC = 0x1a6223c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 4
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82040:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161516
> * Ecx: 0180FDC8: 0180FE94 00982517 00000000 0180FDF0 004017CB 00001388
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 0180FD58: 0180FD90 410721D6 00E02F90 1A622564 0180FD90 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 0180FD00: FFFFFFFF BFF831BC C1A82040 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 00516F4E Module(SQLSERVR+00116F4E)
> * 00516CC4 Module(SQLSERVR+00116CC4)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 5, PSS = 0x1a630098, EC = 0x1a6303c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> 2004-10-20 15:27:13.48 spid5 Clearing tempdb database.
> kDump (all)
> *
> *
> *
> * Edi: C1A83E80:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 01C9F484: 011420B4 00200000 00100000 01C9F4CC 00483C40 00000001
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 01C9F3D4: 01C9F418 0040C9C9 000000D0 00012000 00000000 1A6B4000
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 01C9F35C: 011420B4 00200002 00200000 01C9F374 00415052 00000004
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 0040C9C9 Module(SQLSERVR+0000C9C9)
> * 00485EFA Module(SQLSERVR+00085EFA)
> * 00485FF5 Module(SQLSERVR+00085FF5)
> * 00483C40 Module(SQLSERVR+00083C40)
> * 01C9FBA2 Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 6, PSS = 0x1a634098, EC = 0x1a6343c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 6
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82CE0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 01B2FC50: 01B2FED0 00982517 00000000 01B2FC78 004017CB FFFFFFFF
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 01B2FBE0: 01B2FC18 410721D6 00E02C90 1A634564 01B2FC18 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 01B2FB88: FFFFFFFF BFF831BC C1A82CE0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 00517249 Module(SQLSERVR+00117249)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 7, PSS = 0x1a684098, EC = 0x1a6843c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 7
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A82560:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 0194FC3C: 0194FED0 00982517 00000000 0194FC64 004017CB FFFFFFFF
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 0194FBCC: 0194FC04 410721D6 00E02E20 1A684564 0194FC04 000007D0
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 0194FB74: FFFFFFFF BFF831BC C1A82560 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 410721D6 Module(UMS+000021D6) (UmsScheduler::Suspend+00000066)
> * 00879042 Module(SQLSERVR+00479042) (GetOSErrString+0000230F)
> * 004017CB Module(SQLSERVR+000017CB)
> * 00401662 Module(SQLSERVR+00001662)
> * 0051876D Module(SQLSERVR+0011876D)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 8, PSS = 0x1a6b8098, EC = 0x1a6b83c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 8
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A84670:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 0225E550: 0225E64C 0097E7BA FFFFFFFF 0225E58C 0040330A 1A6B2030
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 0225E4D4: 0225E504 00440F0C 1A6F2000 00002000 0009C000 00000000
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 0225E454: FFFFFFFF BFF831BC C1A84670 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 00440F0C Module(SQLSERVR+00040F0C)
> * 00441154 Module(SQLSERVR+00041154)
> * 0040330A Module(SQLSERVR+0000330A)
> * 00403E2F Module(SQLSERVR+00003E2F)
> * 00406528 Module(SQLSERVR+00006528)
> * 004061CB Module(SQLSERVR+000061CB)
> * 00405DF8 Module(SQLSERVR+00005DF8)
> * 004F7294 Module(SQLSERVR+000F7294)
> * 004050F7 Module(SQLSERVR+000050F7)
> * 00409E39 Module(SQLSERVR+00009E39)
> * 00409C49 Module(SQLSERVR+00009C49)
> * 00515096 Module(SQLSERVR+00115096)
> * 00514FB7 Module(SQLSERVR+00114FB7)
> * 0050C0EB Module(SQLSERVR+0010C0EB)
> * 005100FF Module(SQLSERVR+001100FF)
> * 0050F152 Module(SQLSERVR+0010F152)
> * 00519C2D Module(SQLSERVR+00119C2D)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> *Dump thread - spid = 9, PSS = 0x1a6b0098, EC = 0x1a6b03c0
> *Stack Dump being sent to C:\PROGRAM FILES\Microsoft SQL
> Server\MSSQL$INSTANCE_NAME\log\SQLDump0220.txt
> * *******************************************************************************
> *
> * BEGIN STACK DUMP:
> * 10/20/04 15:27:13 spid 9
> *
> * StackDump (all)
> *
> *
> *
> * Edi: C1A848E0:
> * Esi: 00000001:
> * Eax: 002A005C:
> * Ebx: 00E000B0: 41076144 00000000 00000009 00000000 13121110 17161512
> * Ecx: 022FF05C: 022FF654 00980D9F 00000000 022FF660 0050FFC8 00000002
> * Edx: 00000100:
> * Eip: BFF8A127: 0000C03D 75F08B00 B317E805 C68BFFFE 000CC25E 286A056A
> * Ebp: 022FC784: 022FCBBC 00571383 022FE000 00001000 0037C000 00000000
> * SegCs: 0000019F:
> * EFlags: 00000246:
> * Esp: 022FC704: FFFFFFFF BFF831BC C1A848E0 FFFFFFFF 00000001 BFF8318C
> * SegSs: 000001A7:
> * *******************************************************************************
> * ----
> * Short Stack Dump
> * BFF8A127 Module(KERNEL32+0002A127) (CancelWaitableTimer+0000011F)
> * 00571383 Module(SQLSERVR+00171383) (SQLExit+0004B903)
> * 00571315 Module(SQLSERVR+00171315) (SQLExit+0004B895)
> * 00571741 Module(SQLSERVR+00171741) (SQLExit+0004BCC1)
> * 00511A3D Module(SQLSERVR+00111A3D)
> * 0050FFC8 Module(SQLSERVR+0010FFC8)
> * 0050F152 Module(SQLSERVR+0010F152)
> * 00519C2D Module(SQLSERVR+00119C2D)
> * 41075002 Module(UMS+00005002) (UmsThreadScheduler::Context+00000532)
> * 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)
> * 542868FF Module(UNKNOWN+00000000)
> * ----
> 2004-10-20 15:27:13.69 server SQL Server is aborting. Fatal exception c0000005 caught.
>|||Hi
The problem is solved. The client had his network card damaged
and apparently this caused problems (or something related
to the card configuration) cause after replacing it the
server started up.
I'm curious what is so important in network configuration
that could disable SQL server startup?
Hilarion|||> Tibor Karaszi, SQL Server MVP
Thanks for your time anyway.
Hilarion|||Hi Hilarion,
It's great to hear that it was resolved by replacing the damaged network
card. SQL Server startup need configure net library and it is entirely
possible to cause the access violation when it fails based on my experience
Anyway, to find out the root cause of this issue we may need to analyze
memory dumps, this work has to be done by contacting Microsoft Product
Support Services.
Thank you for your patience and corperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
Subscribe to:
Posts (Atom)