Server Scheduler troubleshooting 

Common issues when running the Scheduler 

Always check the Forum  to see if your issue is addressed there.  This link will access all posts tagged "Scheduler": 

Cannot run as a Windows Service?

Make sure you have configured the service to use the same user account as has been activated.

See also Windows Service troubleshooting

Not enough memory when running as a Windows Service?

Make sure that the memory has been configured in the wrapper.conf in your installation folder

See also Windows Service troubleshooting

Cannot perform actions on Excel files when running as a Windows Service?

Using the Scheduler as an installed service on Windows 7 and Server 2008, you may find that actions which open and save Excel files no longer work.  In the logs, you may see errors such as:


Excel error 

Error communicating with Application. Please try again.

Invoke of: Open

Source: Microsoft Excel

Description: Microsoft Excel cannot access the file '...'. There are several possible reasons:

• The file name or path does not exist.

• The file is being used by another program.

• The workbook you are trying to save has the same name as a currently open workbook.


In older versions of Omniscope, you might not see any errors in the log.
This problem is discussed in detail here:  
However, to fix this, while running with admin privileges, simply create these folders:
  • "C:\Windows\SysWOW64\config\systemprofile\Desktop" (if running a 64-bit operating system)
  • "C:\Windows\System32\config\systemprofile\Desktop"  (on all systems)

Cannot find file when saving through Scheduler

You may encounter a problem when trying to save Scheduler settings with a message relating to "config.xml cannot be found". The most common cause for this is that the config.xml file is saved in a write-protected location, for example, in Program Files.

In order to fix this, you need to make sure that the config.xml file is in a non-protected location, or that Scheduler has administrative privileges. This is a limitation of Windows where non-administrative privileges application are not allowed to write to certain location such as Program files. 

Note: By default config.xml is placed in local user account, and not in write-protected location.