Technical FAQs

Ask a Question

PME installation is not creating the Windows scheduled tasks

When PME/PME4DC/PME4HC is being installed, the installer does not create Windows scheduled tasks. Rerunning the PME installer in configure mode does not create the scheduled tasks either.

Product Line
Power Monitoring Expert 7.2.x
Power Monitoring Expert 8.0

PME/PME4HC/PME4DC Installation

Domain security policies may be blocking the creation of Windows scheduled tasks with security options "Run whether user is logged on or not"


1. Before the start of this procedure, it is recommended that the server gets removed from the domain.

2. Once the server has been removed from domain, click on "Import Task" from the Actions pane within the Windows Task Scheduler.

3. Select each task from the files in the attached zip.
  • ApplicationModules - Backup
  • ApplicationModules - Maintenance
  • ApplicationModules - Trim
  • ION_Data - Archive
  • ION_Data - Backup
  • ION_Data - Maintenance
  • ION_Network - Backup
  • ION_Network - Maintenance
  • ION_SystemLog - Maintenance
  • ION_SystemLog - Trim
  • ION_Data - Size Notification (Only for SQL Express edition)
4. In order to import these scheduled tasks the task scheduler will need user account information for the "IONMaintenance" user. 

5. The "IONMaintenance" user's password can be modified without affecting the operations of the software by following the below steps:
      i.  Open control panel-->Administrative Tools-->Computer Management.
      ii. From the left side of the pane expand "Local Users and Groups". Click on the folder "Users".
      iii. Right click the user "IONMaintenance" and select "Set Password"
      iv. Please Note down the new password for future references.

6. Run the scheduled tasks manually to verify the tasks are being performed.
    If task is failing with return code 4294770688 (0xFFD0000) check the Program/script path and the arguments path by following the below steps:
      i.  Navigate to the Task properties by right click on the selected Task ->Actions Tab ->Edit
      ii. Modify the Program/script field if necessary. Typically this location will be like "C:\Windows\syswow64\WindowsPowerShell\v1.0\powershell.exe"
      iii. The argument field contains path to the PowerShell file location. Modify the path if location is different on the server.
For further debugging of error codes use FA263465
Was this helpful?
What can we do to improve the information ?