From time
to time, customers receive the following error in conjunction with LOGbinder,
we've even had it in our lab environment. We are trying to get to the bottom of
the issue, and we need your help--even if you haven't had the problem yourself.
"Unable to configure SharePoint export. Details: Cannot open database
"WSS_Content" requested by the login. The login failed. Login failed for user
'SHAREPOINTSERVER\logbinderaccount'. SQL Database 'WSS_Content' on SQL Server
instance 'SHAREPOINTSERVER\OfficeServers' not found. Additional error
information from SQL Server is included below. Cannot open database
"WSS_Content" requested by the login. The login failed. Login failed for user
'SHAREPOINTSERVER\logbinderaccount'."
Through our research so far, we find it is a common error with SharePoint,
occurring most often (a) in conjunction with an upgrade or (b) when SharePoint is
accessed via a console application or service. The second scenario applies to
LOGbinder SP. And this error occurs even though the account is a SharePoint farm
administrator, with all privileges being assigned correctly.
The workaround is to add the account manually as a user to the SQL database
WSS_Content, assigning permissions as database owner (db_owner database role).
This works most of the time. However, we would like to get some more definitive
answers on this issue. To do that, could you answer the following questions?
If you have had the error:
- Did it occur in your test or production environment?
- What did you do to work around the error?
If you have NOT had the error:
- For the account you use to run the LOGbinder agent, what SharePoint groups
does it belong to?
- Is the account a domain account or a local user account?
- To what domain groups does it belong?
- What local groups?
- If you have a multi-server SharePoint farm, from which server is LOgbinder
running? (database, front-end, application, etc.)
You may send your response to support@logbinder.com. Any information
you provide will be kept strictly confidential. Thank you.