When you are developing or implementing a CRM system, you will almost certainly stumble across this error from time to time. It is one of those worrying ones that doesn't give you the information you need to diagnose the problem, but luckily, there are a few likely causes you are welcome to try before picking up the phone and calling us for support.
Firstly, odds are this problem is caused by a problem connecting to the database. Open up the registry by going to run and typing "regedit" and look for the following keys
HKEY_Localmachine\Software\Eware
In there, you will find the registry keys for the Database Server and Database Name. Ensure these are correct. It may be that the system cannot login due to the SQL login being incorrect, or having an incorrect password, and it is well worth blanking out the password in both the registry and in SQL to resolve this (I have described this procedure in another post).
Once you have removed all possibility of the problem being related to the login, then things get a little trickier. It is worth dropping the vSentinel view in the database via SQL enterprise Manager, as this will force CRM to recreate all the views as the error suggests.
If all else fails at this point, it's time to call support.
Visit Centurion for more expert advice
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment