INFO: MSMQ Setup Error: "Unable to Resize Master Database" (256022)

SUMMARY

When installing a Microsoft Message Queue Server (MSMQ) Primary Enterprise Controller (PEC), Primary Site Controller (PSC), Backup Site Controller (BSC) or Independent Client (IC) to a SQL 7.0 server, you may receive the following error message:

"unable to resize master database device kernel error code = 0x1"

Issues in either the SQL 7.0 server configuration or the Microsoft Open Database Connectivity (ODBC) cause this error message.

MORE INFORMATION

Verify the following items:

From the SQL 7.0 server program group, click Server Network Utility. Verify that Named Pipes, TCP\IP, and MultiProtocol are the selected defaults.

NOTE: The default settings must be listed in the following order:
- Named Pipes
- TCP\IP
- MultiProtocol
From the SQL 7.0 server program group, click Client Network Utility, and then verify that the default protocol is Named Pipes. MSMQ Setup runs as a secured client process that requires Named Pipes to be the default Client protocol.
Check your permissions to verify that the account you are logged on with has the proper authority to create a database. By default, the MSMQ service runs under the Local System account. Verify that this account is enabled.

NOTE: You must stop and re-start the Microsoft SQL Server (MSSQL) service from the Services applet in the Control Panel after you make any security or network libraries changes.
MSMQ Servers require a System data source names (DSN) ODBC connection to SQL 7.0 server. The DSN is created during the MSMQ Setup process. The DSN uses either Windows NT or SQL level security for the connection. By default, the necessary security settings are correct. If you install a PEC, PSC, or a BSC for the first time, the DSN is created before the Message Queue Information Store (MQIS) database is created.

The error message that you receive implies that the DSN is operable, and that the error is driven by the SQL 7.0 server after the connection through the DSN is made. This error message is displayed because either the DSN existed from a prior MSMQ Server configuration where both the MSMQ and the MQIS were removed, but the DSN was not, or if the SQL security was changed during an upgrade from SQL 6.5 or for some other circumstance. If you remove the MQIS DSN from the System DSN tab in the ODBC program, it forces the recreation of the DSN to match the security settings currently specified in SQL 7.0.