[Greg Wahl]

?We are currently setup where our database is in a cluster so that our data is mirrored to a backup server.  Here recently, I am having to execute the wfDeployClrAssemblies script when we do failover to our backup server.  I then have to run that script again when we fail back over to our production server.

Can anyone explain why we would need to keep running this if our production server and backup server should be one and the same?

——————————
Greg Wahl
Senior Database Administrator
Owensboro Municipal Utilities
Owensboro KY
——————————

[Jo deRuiter]

?Hi

This could be a myriad of issues.

How did you deploy GP in the cluster, etc.

How often are you having to failover to backup?

Does your company use workflows in GP?

——————————
Regards,

Jo deRuiter
“That GP Red Head”
Senior Financial Systems Consultant
Advanced Credentialed Professional-Dynamics GP
Heartland Business Systems, LLC
Milwaukee, WI
770-906-4504 (Cell)
——————————
——————————————-

[Thaddeus Suter]

If workflow is installed (whether you use it or not) then anytime you move your databases  (change the SQL instance), you will have to run this statement exec wfDeployCLRAssemblies in order to refresh the assemblies.
You should add this step to your recovery procedures from a backup server.

——————————
Thaddeus Suter
Retus, Inc
HELOTES TX
——————————
——————————————-

[Derek Albaugh]

Greg,

Along with what has been mentioned, I’m curious as to whether you’re seeing an error message or anything, or why you ‘have’ to run the wfDeployClrAssemblies procedure?

As mentioned already here, this procedure is mainly just dropping and re-creating the stored procedures, assemblies and functions used by our new Workflow functionality that was introduced in GP 2013 R2 and continued through the most recent versions.

It actually won’t hurt anything to run this procedure, I was just curious if you’re getting a type of error or anything after failover.

Thanks,

——————————
Derek Albaugh
Sr. Support Engineer
Microsoft
Moorhead MN
——————————
——————————————-