Issues to Lookout for When Moving or Upgrading Scribe

Recently during a client’s Microsoft Dynamics CRM & Dynamics GP systems upgrade, KTL Solutions also had to upgrade Scribe, move the application server, and move the SQL database for Scribe. In this process, we came across an issue which I have described below. Scribe provides steps for each of the operations with moving the SCRIBEINTERNAL database as well as moving the Scribe components to a new server. The order in which you perform these steps is important because backing up the Scribe database too early can cause issues for you later when you are in the process of setting up the Scribe services

The Scribe registration process creates a unique SiteKey for the server install of Scribe. One of the steps as part of the move is to unregister the Scribe registration; you have to make sure that this process is done before taking the backup of the ScribeInternal database to restore on a new SQL server. If the site-key key name in the KSYNC table of SCRIBEINTERNAL database is not removed, then that can cause issues in the new environment. You will be able to start all the Scribe services except the Admin service, and won’t be able to open the Scribe Console MMC application. The error that is logged in the Windows event viewer is “Invalid Site Key.”
If you run the following query it will give you the results of the SiteKey in the SCRIBEINTERNAL database:

 where KEYNAME='SiteKey'

The KeyValue for SiteKey is autogenerated when the Scribe registration process is completed. If this site key already exists then it is not updated and no matter how many times you re-register it will remain there while the Scribe Admin service will not start.

Scribe has provided an alternative solution for this issue. In the Scribe Program files folder, there exists a ClearScribeLicense.sql SQL query file which once ran against the SCRIBEINTERNAL database it will remove the Site Key key name along with other rows from the KSYNC table. I would recommend running the complete SQL query in this file vs. running individual statements. Once this is done, then you will have to go through the Scribe registration process again which should then create a new Site Key value and then the Scribe Admin service would start without any hiccups.

I hope the above detail helps you if you stumble across a similar issue with your Scribe database or server components move. If you have any questions, please notify KTL Solutions by emailing or by calling 301-360-0001.

DAVE VORA | Senior Business Software Consultant/ CRM Lead

Dave is responsible for leading KTL’s CRM consultants, assuring that our solution scoping, architecting and delivery meet and exceed customer expectations. Dave has built lasting relationships with clients by understanding their business needs and providing value by leveraging their existing resources. Along with his consulting team, he has delivered effective solutions beyond traditional CRM constraints. Dave has more than eight years of experience in implementing business software for a variety of industries, including service, government, distribution, not-for-profit and manufacturing.  He graduated with a Bachelor of Science Degree in Computer Science and also a specialization in Management from University of California at Irvine.  His experience includes helping companies embrace technology to fulfill their organizational needs and creating innovative solutions using CRM, GP, Scribe and other Microsoft products.

Share this post

Related Posts

Checking Your CMMC Progress

Written by Alec Toloczko With Cybersecurity Maturity Model Certification (CMMC) requirements on the horizon, it’s crucial for organizations handling Controlled Unclassified Information (CUI) to adhere

Read More »