| MyAssistant tasks run, but never complete. (multiple causes) |
Cause | MyAssistant Tasks can fail to finish running for one or more of the following reasons: - The ISDAdminTaskService service is not running or needs to be restarted on the MyAssistant Server
- Antivirus or Firewall is disabling or killing the ISDAdminSenderService
- The ISDAdminTaskService does not have sufficient permissions to run
- The Windows services ISDAdminTaskService and ISDAdminSenderService run as a Local System account by default on the MyAssistant Server. The Local System account may not always have the permissions required for the MyAssistant software to run properly.
- MyAssistant Server is not activated or cannot reactivate
- MyAssistant attempts to contact the entitlements about every 30 days. If the attempt fails due to any number of reasons (such as a firewall, proxy server, or antivirus software), MyAssistant deactivates.
- The MyAssistant Drive Mapper must be upgraded
- This will be indicated by errors that will be found in the Event Viewer on the MyAssistant Server.
- Insufficient permissions to the registry
- Event Viewer may show this error:
Source: ApplicationCoreServices.Security.ActivationHelper.UpdateReportingStatistics Process ID: 2992 Unable to update service statistics: invalid activation data. System.UnauthorizedAccessException: Access to the registry key HKEY_LOCAL_MACHINE\Software\Innovative Software Design\My Assistant\Setup Information' is denied. - There are multiple MyAssistant servers currently active.
- This is typically caused by a performing a migration and not disabling MyAssistant on the old server.
- The ntdbsmgr process on the server is using too many resources and interfering with MyAssistant's communication with Pervasive.
- This will be specific to versions 16.1 and higher.
- This is due to the Actian/Pervasive engine not being configured with the most optimal settings.
- Regional settings on the server are incorrect. Windows Regional settings is set to USA and CRE install is configured for Canada, or vice versa
- You may receive the following error message in the System Information log:
"An error occurred while updating the server statistics System.ArgumentOutOfRangeException: The added or subtracted value results in an un-representable DateTime. Parameter name: value at System.DateTime.AddTicks(Int64 value) at System.DateTime.Add(Double value, Int32 scale) at TaskCommand.TaskCommand.Execute(ObjectstaticData)" |
Resolution | [BCB:3:Network warning:ECB] - Start or Restart the ISDAdminTaskService on the server:
- For all versions:
- Log on to the MyAssistant server as a Windows administrator.
- Click the Windows Start button and type Services into the Search bar.
- Select the Windows Services program from the list of results.
- Locate ISDAdminTaskService.
- Right-click on the service and select Restart.
Note: If you receive a 1053 error, see Error: "1053: The service did not respond..." when starting the ISDAdminTaskService for MyAssistant - Try to re-run the task.
- For only versions 20.3.5 and later:
- Launch the MyAssistant Designer.
- Go to File, Restart Run and Send.
- Click OK to pop up message and wait the suggested time.
- Set anti-virus or firewall exclusions for MyAssistant files:
- Update the ISDAdminTaskService and ISDAdminSenderService to run as a Windows domain administrator:
- Log on to the MyAssistant server as a Windows administrator.
- Click the Windows Start button and type Services into the Search bar.
- Select the Windows Services program from the list of results.
- Locate the ISDAdminTaskService and ISDAdminSenderService and double-click on each to open the properties window.
- Click the Log On tab.
- In the This account field, if you know the domain, type in an administrator account, such as MyDomain\Administrator where MyDomain is whatever your network domain is. This account cannot be a local administrator account, and must belong to the domain. If you know the domain and type in the correct [domain]\[username] account, skip the remaining steps and simply click OK and restart both ISD services.
- If you do not know what the domain is, click Browse.
- In the next window, click Locations, Entire Directory.
- Highlight your domain.
- Click OK.
- In the Enter the object name to select window, type in the username and click Check Names.
- Select the correct username if prompted.
- Click OK twice.
- Restart both ISD services.
- Reactivate the MyAssistant Server:
- Log on the server as the Windows user who originally activated the MyAssistant Server.
Note: When you activate any license key, it is linked to that Computer name and Windows user login. You must remember which login you used to perform this step. If you do not know, contact Sage Support. - Launch MyAssistant Configuration Manager.
- Click on Reactivate or Activate if given the button to do so. If this fails, contact Sage Support.
- Upgrade the MyAssistant Drive Mapper:
Note: These steps require knowledge of your network and file locations, and should be performed by a Windows user with Administrative rights to your server. - Log on to the MyAssistant server with a Windows user that has Administrator or Unlimited privileges.
- Stop the ISDAdminTaskService and ISDAdminSenderService services from Window Services.
- Open the Tools folder from the extracted MyAssistant installation files. This will be a location you selected when saving the install files. There is no default location.
- Open the DriveMapperCommand.config file with a text editor.
- Replace the drive letter and UNC path with your mapped network drives used for reporting and file locations.
- Using Windows Explorer, copy the InnovativeSoftwareDesign.MyAssistant.DriveMapperCommand.dll file and the DriveMapperCommand.config file.
- Paste both files in the following locations:
- C:\Program Files (x86)\Innovative Software Design\MyAssistant
- C:\Program Files (x86)\Innovative Software Design\MyAssistant\Sender Service
- C:\Program Files (x86)\Innovative Software Design\MyAssistant\Task Service
Note: The default location for MyAssistant installation is "C:\Program Files (x86)\Innovative Software Design\MyAssistant". Use your custom location if you changed the path during installation. - Start the ISDAdminTaskService and ISDAdminSenderService from Windows Services.
- The MyAssistant Drive Mapper tool is now upgraded.
- Modify permissions to registry key:
- Give full permissions to the HKEY_LOCAL_MACHINE\Software\Wow6432Node\Innovative Software Design\ registry key to the groups for the MyAssistant operators and Service accounts.
- Restart the ISDAdminTaskService and ISDAdminSenderService services.
- Disable old server and update workstation configuration:
- Connect to old server.
- Launch Windows Services.
- Stop the ISDAdminSender, ISDAdminTask and SQL Server (ISD) services.
- Disable all three services by right-clicking and selecting Properties.
- Launch MyAssistant Designer on the workstation.
- You should be prompted to correct the SQL Server name. Click OK to this message and it will launch the user configuration.
- Update the server name.
- Click OK to save settings.
- Change the Actian/Pervasive engine settings:
- See The ntdbsmgr.exe or PSQL Component processes are using too many resources. for the recommended settings.
- Changing these settings will require a restart of the Actian/Pervasive engine, so all users should be out of Sage 300 Construction and Real Estate.
- After the Actian/Pervasive engine is restarted, restart both ISD services.
- Change the Windows Regional Settings on the server to match the 300CRE installation:
|
|