The most enigmatic error in SageCRM is probably “You may need to recreate views manually.” There are several reasons why this can appear. Before making any changes to SQL Server, make sure to back up the database. Before making any changes to the Registry, back it up.
The “sa” User Password Has Been Changed
If the sa password has been changed in SQL Server and not in SageCRM, it will need to be changed in SageCRM. If the sa password is not known, it will need to be changed in SQL.
The Database is Not Running
Or, If the database is already running, stop and start the database service and retry.
There is a Mismatch Between SageCRM Versions
This can happen if an earlier version database is restored to the current version.
SageCRM is Trying to Connect to the Wrong Database
Go to HKEY_LOCAL_MACHINE\SOFTWARE\eware\config. Click on the CRM beneath that and see the right panel. Make sure that the default databaseserver matches your database name exactlty. If it does not, then change it manually. Run an IISRESET and logon again.
The vsentinel View Needs to Be Dropped
Look for a view in SQL server called “vsentinel”. Drop the view and then perform an IIS reset. This will recreate the views.
APR
2008







About the Author
Steve Chipman is the founder and president of Lexnet Consulting Group, which is based in the San Francisco Bay Area. Lexnet provides CRM implementation and integration services throughout the United States and Canada.