![]() | |
![]() |
| | Thread Tools | Display Modes |
#31
| |||
| |||
|
|
point, there is an object that has a contract to fulfil, which it cannot do without querying the universe. I found the other day, that when you script a database, the script wizard goes querying information for each database. And if a datbase is offline because it's set to auto-close... |
|
Well, at least you are admin so that you can continue. If you are a customer at a web host, you are slapped in the face badly, and is told to keep out. |
#32
| |||
| |||
|
|
point, there is an object that has a contract to fulfil, which it cannot do without querying the universe. I found the other day, that when you script a database, the script wizard goes querying information for each database. And if a datbase is offline because it's set to auto-close... |
|
Well, at least you are admin so that you can continue. If you are a customer at a web host, you are slapped in the face badly, and is told to keep out. |
#33
| |||
| |||
|
|
point, there is an object that has a contract to fulfil, which it cannot do without querying the universe. I found the other day, that when you script a database, the script wizard goes querying information for each database. And if a datbase is offline because it's set to auto-close... |
|
Well, at least you are admin so that you can continue. If you are a customer at a web host, you are slapped in the face badly, and is told to keep out. |
#34
| |||
| |||
|
|
point, there is an object that has a contract to fulfil, which it cannot do without querying the universe. I found the other day, that when you script a database, the script wizard goes querying information for each database. And if a datbase is offline because it's set to auto-close... |
|
Well, at least you are admin so that you can continue. If you are a customer at a web host, you are slapped in the face badly, and is told to keep out. |
#35
| |||
| |||
|
|
point, there is an object that has a contract to fulfil, which it cannot do without querying the universe. I found the other day, that when you script a database, the script wizard goes querying information for each database. And if a datbase is offline because it's set to auto-close... |
|
Well, at least you are admin so that you can continue. If you are a customer at a web host, you are slapped in the face badly, and is told to keep out. |
#36
| |||
| |||
|
|
point, there is an object that has a contract to fulfil, which it cannot do without querying the universe. I found the other day, that when you script a database, the script wizard goes querying information for each database. And if a datbase is offline because it's set to auto-close... |
|
Well, at least you are admin so that you can continue. If you are a customer at a web host, you are slapped in the face badly, and is told to keep out. |
#37
| |||
| |||
|
|
point, there is an object that has a contract to fulfil, which it cannot do without querying the universe. I found the other day, that when you script a database, the script wizard goes querying information for each database. And if a datbase is offline because it's set to auto-close... |
|
Well, at least you are admin so that you can continue. If you are a customer at a web host, you are slapped in the face badly, and is told to keep out. |
#38
| |||
| |||
|
|
I installed a SQL Server 2008 Express today on my local machine, and after a successful local installation, I tried to connect (from the SQL Server 2008 Management Studio) to an instance of SQL Server 2005 Express on a network server. It connected successfully but it failed when loading the databases list (i.e. expanding the Databases node) with error 916, indicating that my account didn't have permission on the Report Services Temp Database. I resolved this by logging in with Administrator on the server and adding a user mapping for all Domain Users to that database, keeping only Public as permission, so not giving actually any new permissions for the database (my account is a domain user). After that it loaded fine. Anyway, other databases seemed to have the exact same configuration as the temporary database of Reporting Services 2005 but didn't fail like that, so I don't have an explanation for the issue, just the workaround above. To be sure that this doesn't happen again I added the same user mapping on all other databases on the server so that all domain users can browse the databases themselves without having permission to read/write any tables. I think this is a bug in the new SQL Server 2008 Management Studio as 2005 Management Studio didn't have this problem. Update: I found out that the database with problems had a database state (in Properties/Options) of NORMAL | SHUTDOWN. I found that when a database is in SHUTDOWN state, the problem occurs. To temporarily resolve the issue you just need to issue a query on the database and its state will become NORMAL (without SHUTDOWN) and then SQL Server 2008 Management Studio will browse the databases correctly. But it's probably only a matter of time until SHUTDOWN state becomes applied again. If anyone has a better understanding or resolution for this issue, please let me (and all others) know. Sorin Dolha, DlhSoft |
#39
| |||
| |||
|
|
Try the following... it worked for me. http://blog.cpugeni.com/archive/2008...management-stu dio-2008-error-916.aspx |
![]() |
| Thread Tools | |
| Display Modes | |
| |