Collaboration linked database alias is incorrect...

Question

but it is not.
Anyone run into this? My log shows this, note the failed message and subsequent connection is working lines.:
2010-01-04 10:08:58,845 INFO - Finished Loading Databases
2010-01-04 10:08:58,860 INFO - Setting Transaction Isolation Level
2010-01-04 10:08:58,860 INFO - Isolation level is read uncommitted
2010-01-04 10:08:58,860 INFO - Finished Setting Transaction Isolation Level
2010-01-04 10:08:58,860 INFO - Testing Database Connections
2010-01-04 10:08:58,891 INFO - JDBC Driver Version:SQLServer 3.40.6 (012712.007203.008710)
2010-01-04 10:08:58,891 INFO - Connected to database:collaboration
2010-01-04 10:08:58,954 INFO - plumdbname.plumdbusername. linked database alias failed failed retrying linked database alias
2010-01-04 10:08:58,970 INFO - Adding plumdbname.. as linked datbase alias
2010-01-04 10:08:58,970 INFO - Connection to linked database is working
2010-01-04 10:08:58,970 INFO - Finished Testing Database Connections
2010-01-04 10:08:58,970 ERROR - Linked Database Alias is incorrect check database.xml
2010-01-04 10:08:58,970 ERROR - Collaboration Server failed to start.

Answer 1

This might be a role grant problem. Is the databasename.dbo set correctly for the collab product?
If you can repro in a test environment...you could also try these steps below to see if they help. Technical support has also had some experience working on this problem, so you can consider opening a case with them.
Ryan
1/ Grant the portal database user Read access to the tables in the Collaboration database by executing the following script against the collaboration database using the collaboration database user:
install_dir\ptcollab\<version>\sql\<dbtype>\collaboration-server-portal-role-grant.sql script.
2/ Examine the collaboration views in the Portal database, and verify the table owner. To accomplish this, expand portal database, views, and then look for the <username> in the views:
<USERNAME>.CSVPORTALGATEWAYDATA
<USERNAME>.CSVPREFERENCE
<USERNAME>.CSROLEMEMBERSHIP
If it is something other than the portal database user (for example DBO instead of the portal db user), then follow these steps:
* Open the following script: install_dir\ptcollab\<version>\sql\<dbtype>\portal-collaboration-server-data.sql script
* Search for "collabdbuser" and change this to the user that owns the above views (ie. change to dbo).
* Run this script against your portal database using the portal database user.
3/ Run the following script against the portal database using the portal database user:
install_dir\ptcollab\<version>\sql\<dbtype>\portal-server-portal-role-grant.sql script.
Note: Some of the above scripts may fail to run with a message that the data already exists. This is okay.