Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
b8538230
Starting Member
16 Posts |
 Posted - 2012-02-24 : 11:50:37
|
I wanted to speed up my ssms startup so it would automatically log in to the server I use most, So I changed the shortcut to read:"C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe" -nosplash -E -S torsq003However, when I try to start up with these options, I get the error message:quote:
Failed to create SQL Server script.Additional information:Object reference is not set to an instance of an object (AppIDPackage)
I have to confess that I don't understand the error message or what to do to get my startup options accepted.What should I do? |
|
|
b8538230
Starting Member
16 Posts |
Posted - 2012-02-29 : 13:51:52
|
| Still looking for an answer on this one |
 |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-02-29 : 14:41:24
|
| looks like a .NET error------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
b8538230
Starting Member
16 Posts |
Posted - 2012-02-29 : 14:54:45
|
| OK -- so does that mean there's no fix or workaround? |
|
|
|
b8538230
Starting Member
16 Posts |
Posted - 2012-03-02 : 09:06:39
|
Here's some more info on this problem. Consider:C:\>cd \tmpC:\tmp>dir *sql Volume in drive C is WinXPSP3 Volume Serial Number is AEFC-C3CF Directory of C:\tmp01/16/2012 02:38 PM 583 compare.sql 1 File(s) 583 bytes 0 Dir(s) 79,500,034,048 bytes freeC:\tmp>ssms compare.sql:: The above command works and prompts for server logon upon startup. "compare.sql" is loaded into the editor.C:\tmp>ssms -S torsq003 -E compare.sql:: The above works and automatically logs in to the server using Windows Auth. "compare.sql" is loaded into the editor.C:\tmp>ssms -S torsq003 -E:: The above command starts ssms, does not log into the server and throws the error message:quote:
Failed to create SQL Server script.Additional information:Object reference is not set to an instance of an object (AppIDPackage)
So, it looks like a bug in the ssms command. The command description says that the scriptfile is optional. I tried to find a bug report on this, but haven't been successful on that count so far.Does anyone have a reference for an official bug report? |
|
|
|
b8538230
Starting Member
16 Posts |
Posted - 2012-03-07 : 13:47:28
|
| Replying to my own reply to bump this in the list. Just in case anyone has seen this or knows a workaround. |
|
|
|
|
|
|
ssms startup options?