Search

Starting SQL Server from command line with incorrect instance name gives empy error message by Erland Sommarskog

Closed
as Fixed Help for as Fixed

2
0
Sign in
 to vote
Type: Bug
ID: 489789
Opened: 9/14/2009 12:17:04 PM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
If you start SQL Server 2008 from the command line, and do not specify the instance name correctly with -S all you get in reward is an empty message box. With SQL 2005, you also get a message box, but with an error message. (Saying that that the SQL Server installation is corrupt or has been tampered with.)

I don't if this is a localisation issue, but I'm running with Swedish for my regional settings.
Details (expand)
Product Language
English

Version

SQL Server 2008 SP1

Category

SQL Engine

Operating System

Windows Vista 64-bit SP1
Operating System Language
US English
Steps to Reproduce
"C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn" /SNOSUCHINSTANCE
Actual Results
Empty message box.
Expected Results
Message box

Platform

X64
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 8/31/2010 at 7:04 PM
Update: This will be fully resolved in CTP2.
Posted by Microsoft on 8/31/2010 at 7:03 PM
Update: this will be fully resolved in CTP2.
Posted by Microsoft on 8/31/2010 at 7:03 PM
Update: this will be fully resolved in CTP2.
Posted by Microsoft on 8/31/2010 at 7:01 PM
Update: this will be fully resolved in CTP2.
Posted by Microsoft on 5/21/2010 at 8:28 AM
This appears to be resolved in SQL11 CTP1 - error "Error getting instance ID from name" is returned now.
Posted by Microsoft on 9/18/2009 at 7:58 AM
Thank you Erland, we will look into what caused the change in behavior.
Sign in to post a workaround.
© 2012 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement