Sage CRM was installed 3 months back on our server for internal use and was working fine. Now our network administrators had changed password for SA account for security purpose and trying to logon to Sage CRM and get You May Need to Recreate Views Manually. (He was simply not aware that Sage CRM had used SA account for connecting to Sage CRM database.)
New Stuff: Adding new fields on Web Order Item Entry screen
There are several reasons for this error message to be appearing. I will consolidate all of them with Cause and their Resolutions in this post.
Cause 1: Sage CRM database user password has been changed
If Sage CRM database password is changed in Microsoft SQL server and not in Sage CRM then resetting the password in Sage CRM resolves an issue by navigating to Administration | System | Database.
If you are unable to login to Sage CRM, user can change it from registry by navigating to below path and changing the DatabasePassword node.
For 32-bit server:
In Registry Editor navigate to HKEY_LOCAL_MACHINE | SOFTWARE | eWare | Config | <<CRM Instance>>
For 64-bit server:
In Registry Editor navigate to HKEY_LOCAL_MACHINE | SOFTWARE | Wow6432Node | eWare | Config | <<CRM Instance>>
1. Make sure you have backed up registry before making any changes.
2. When password is changed from registry, it doesn’t remains encrypted. To encrypt it, you need to change it by navigating to Administration | System | Database, once you are able to login in Sage CRM.
Cause 2: Configuration on Sage CRM database server
On Sage CRM database server
1) If TCP/IP protocol is disabled.
2) Microsoft SQL server Browser is not running.
Cause 3: vSentinel View Needs to be dropped
Dropping of vSentinel view recreates all views based on its definition stored in metadata.
Cause 4: Existence of vGroupEntities and vGroupLookup views
Kindly check if the views vGroupEntities and vGroupLookup exists in your CRM database. We have documented the same here.
Cause 5: Sage CRM is trying to connect wrong database
Kindly check if Sage CRM is pointing to the correct database. User can check the same from registry by navigating to path mentioned in Cause 1 and checking the DefaultDatabase node.
Cause 6: Mismatch between Sage CRM Versions
It can also happen when there is a mismatch between Sage CRM version and its database.
If you do not find your solution in the above listed, just don’t get panic and check both SQL and System logs which gets created in Sage CRM logs folder. It will probably point you to the origin of an error. Sage CRM logs are located under below path on Sage CRM server.
C:\Program Files\Sage\CRM\<<CRM Instance>>\Logs\
Greytrix a globally recognized Premier Sage Gold Development Partner is a one stop solution provider for Sage ERP and Sage CRM needs. Being recognized and rewarded for multi-man years of experience, we bring complete end-to-end assistance for your technical consultations, product customizations, data migration, system integrations, third party add-on development and implementation expertise.
Greytrix has some unique integration solutions for Sage CRM with Sage ERPs (Sage Enterprise Management (Sage X3), Sage Intacct, Sage 100, Sage 500 and Sage 300).We also offer best-in-class Sage ERP and Sage CRM customization and development services to Business Partners, End Users and Sage PSG worldwide. Greytrix helps in migrating of Sage CRM from Salesforce | ACT! | SalesLogix | Goldmine | Sugar CRM | Maximizer. Our Sage CRM Product Suite includes Greytrix Business Manager, Sage CRM Project Manager, Sage CRM Resource Planner, Sage CRM Contract Manager, Sage CRM Event Manager, Sage CRM Budget Planner, Gmail Integration, Sage CRM Mobile Service Signature and Sage CRM CTI Framework.
For more information on our integration solutions, please contact us at email@example.com. We will be glad to assist you.