AutomationTool: Troubleshooting
Summary
Your AutomationTool is properly set up, but it seems to not sync your systems?
This is a 50 seconds video of how a successful connection should looks like:
Error
-------------------------
AppVersion: 19.2.1.0 - Branch: - ChangeSet: 25046 - ReleaseDate: 2019.7.8
2019.08.12|15:14:21
Cannot start service SyncService on computer '.'.
-------------------------WorkingPath: C:\PerformerSuite
-------------------------
AppVersion: 19.2.0.0 - Branch: - ChangeSet: 24763 - ReleaseDate: 2019.5.31
2019.08.12|13:07:13
Database connect: DbVersionDiffers
-------------------------If you feel something is wrong you can check the log file for errors:
PerformerSuiteSyncService.log (C:\PerformerSuite\Services\logfile)
Cause - Unknown
To reproduce and fix your issues, we need to know why your services stop responding on your machine.
Start services.msc (on the machine that is running the services) if both services are currently running
Check the Recovery Properties for both services to automatically restart the service
Start eventvwr (on the machine that is running the services) and check for Application Error for PerformerSuiteServices.exe
Cause - Authorization
There is a connection issue between the AutomationTool to the Performer Suite DB.
In most cases, it is missing write permission on the DB or a firewall blocking the connections.
Solution - Authorization
1) SQL Authorization
Go to: "Change connection"
Check: "Use SQL Authorization" (Windows Authorization does not work)
Check the PerformerSuiteSyncService.log for any error. (C:\PerformerSuite\Services\logfile)
Do you see the error "Database connect: DbVersionTableDoesntExist"?
If yes: Give your DB-User write-rights to the table DbVersion.Make sure the SyncService grabs all the changes, by doing the following steps:
"Stop sync service"
"Uninstall sync service"
"Install sync service" again
"Start sync service" again.
Done. Schedule the next sync to the next 5min to run the sync test.
Check the PerformerSuiteService.log for sync-lines (C:\PerformerSuite\Services\logfile):
Check the Performer Suite itself for the correct Sync timestamp:
2) Compare DB connections
Double-check, if the following two connections are identical:
AutomationTool: Mouse-over to see the tooltip showing the DB the AutomationTool is connected to.
Performer Suite: Mouse-over to see the tooltip showing the DB the Performer Suite is connected to.
Cause - Windows Authorization
In rare cases, the right-click, and "open as administrator" is not enough to be able to install the Services.
Solution - Windows Authorization
Log into Windows directly as an Administrator and install the Performer Suite services through the AutomationTool.
Cause - DB outdated
Your AutomationTool is outdated.
The AutomationTool tries to connect to an incompatible version of your Performer Suite DB.
Solution - DB outdated
Update your AutomationTool to the same version as the Performer Suite DB.
Possible further error
-------------------------
AppVersion: 19.3.0.0 Beta - Branch: Beta - ChangeSet: 25624 - ReleaseDate: 2019.9.18
2019.09.18|15:31:04
System.InvalidOperationException
Message:
Exception occurred while initializing the installation:
System.IO.FileNotFoundException: Could not load file or assembly 'file:///C:\Docu Performer\SyncService\DocuPerformerSyncService.exe' or one of its dependencies. The system cannot find the file specified..
Additional details:
at System.Configuration.Install.ManagedInstallerClass.InstallHelper(String[] args)
at ProjectB.AutomationTool.MainForm.UninsallOldSyncService()
at ProjectB.AutomationTool.MainForm.OnInstallServicesButtonClick(Object sender, EventArgs e)
--------------------------------------------------
AppVersion: 19.3.0.0 Beta - Branch: Beta - ChangeSet: 25624 - ReleaseDate: 2019.9.18
2019.09.18|16:09:43
System.InvalidOperationException
Message:
The installation failed, and the rollback has been performed.
Additional details:
at System.Configuration.Install.ManagedInstallerClass.InstallHelper(String[] args)
at ProjectB.AutomationTool.MainForm.OnInstallServicesButtonClick(Object sender, EventArgs e)
InnerException
The specified service already exists
at System.ServiceProcess.ServiceInstaller.Install(IDictionary stateSaver)
at System.Configuration.Install.Installer.Install(IDictionary stateSaver)
at System.Configuration.Install.Installer.Install(IDictionary stateSaver)
at System.Configuration.Install.AssemblyInstaller.Install(IDictionary savedState)
at System.Configuration.Install.Installer.Install(IDictionary stateSaver)
at System.Configuration.Install.TransactedInstaller.Install(IDictionary savedState)
--------------------------------------------------
AppVersion: 19.3.0.0 Beta - Branch: Beta - ChangeSet: 25624 - ReleaseDate: 2019.9.18
2019.09.18|16:07:40
System.InvalidOperationException
Message:
Cannot start service ScenarioGenerationService on computer '.'.
Additional details:
at System.ServiceProcess.ServiceController.Start(String[] args)
at ProjectB.AutomationTool.ServiceHelper.StartService(String serviceName)
at ProjectB.AutomationTool.ServiceHelper.StartServices(List`1 serviceNames)
at ProjectB.AutomationTool.MainForm.OnStartServicesButtonClick(Object sender, EventArgs e)
InnerException
An instance of the service is already running
-------------------------
Feel free to create a ticket in our Help Desk and attach both log files, if you need any support.
Thank you!
PerformerSuiteService.log (C:\PerformerSuite\Services\logfile)
PerformerSuite.log ( C:\Users\<USER>\Documents\PerformerSuite\Log )