INF: SQL Server Shuts Down When Master Database Is Reloaded

ID Number: Q59902

1.10 1.11 4.20

0S/2

Summary:

When the master database is reloaded from a dump, SQL Server will shut

itself down automatically, forcing the user to restart SQL Server to

implement the new master database. This is similar to the way changes

take effect in CONFIG.SYS (although the operating system will not

automatically reboot when CONFIG.SYS is changed). Any time you make

changes to your CONFIG.SYS file, you must reboot your computer so

these modifications will take affect.

When SQL Server shuts itself down, two messages are displayed: one

message in the session running the console and the other message in

the session running ISQL.

The message displayed in the session running the console is as

follows:

Operating System Error:

Read failed with EOF on network pipe.

DB-Library: Unexpected EOF from SQL Server.

The following message is displayed in the session running ISQL:

DB-Library: Unexpected EOF from SQL Server.

These messages indicate that the named-pipe connection has been

broken, which is true, because SQL Server has just shut itself down.

At this point, SQL Server should be restarted, and any other required

databases reloaded.

Additional reference words: Dumping and Loading