Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

SFTP & SCP Server Task Scheduler Error

Just installed NCM on a fresh windows 2008 32 bit server. Trying to setup the SCP/SFTP server and whenever I make a change to the user accounts it says "Error Communicating with Task Scheduler"

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
ScpServerTray.TaskSchedulerException: Error communicating with Task Scheduler. ---> System.InvalidCastException: Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Taskschd.ITrigger'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{09941815-EA89-4B5B-89E0-2A773801FAC3}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).
   at ScpServerTray.TaskSchedulerHelper.ScheduleLoginTask()
   --- End of inner exception stack trace ---
   at ScpServerTray.TaskSchedulerHelper.ScheduleLoginTask()
   at ScpServerTray.MainForm.tmsiConfigure_Click(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4211 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
ScpServerTray
    Assembly Version: 1.0.0.15
    Win32 Version: 1.0.0.15
    CodeBase: file:///C:/Program%20Files/SolarWinds/SftpServer/ScpServerTray.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4205 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
SolarWinds.Sftp.Shared
    Assembly Version: 1.0.0.15
    Win32 Version: 1.0.0.15
    CodeBase: file:///C:/Windows/assembly/GAC_32/SolarWinds.Sftp.Shared/1.0.0.15__2d74dbe163da350f/SolarWinds.Sftp.Shared.dll
----------------------------------------
System.Data
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.ServiceProcess
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------
Interop.Taskschd
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SolarWinds/SftpServer/Interop.Taskschd.DLL
----------------------------------------
CustomMarshalers
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)
    CodeBase: file:///C:/Windows/assembly/GAC_32/CustomMarshalers/2.0.0.0__b03f5f7f11d50a3a/CustomMarshalers.dll
----------------------------------------
System.Web
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4209 (VistaSP2GDR.050727-4200)
    CodeBase: file:///C:/Windows/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Find more posts tagged with

Accepted answers

All comments

BirdDog

I am having the same issue. Has any SW engineer looked at this?

BirdDog

believe i have it figured out.

if you right click on the program icon and go into 'Troubleshoot Compatibility'. You will need to tell the troubleshooter that the program worked in a previous version of windows and needs more permissions. from there you can choose win2003 sp1 and apply those settings. I was then able to modify user and add new users to the sftp server and backup remote systems successfully.

Hope this helps.

xtraspecialj

Keep in mind, what's throwing the error is the Server Tray program, which is separate than the actual service itself. If you want, you can just go into Services.msc and set the service to start automatically. However, if you are getting errors when trying to configure settings the server tray program as well as when trying to control the service from within this program instead of the services.msc console, the following info should help. After doing the below steps, I still get an error if I go into File > Configure and don't make a change, but that's not a big deal. Before, I was getting an error when I did make a change and clicked OK.

Very old post, I know, but I just ran into this problem and BirdDog's response here helped me fix it. We have Server 2012 R2, so when running the Compatability Troubleshooter some of the options were a bit different than what he posted. However, you can skip running the Compatability Troubleshooter completely by just choosing the options below:

Right-click on the "SolarWinds SFTP & SCP Server" like BirdDog says in his post
Click on the Compatibility tab
Click on "Change settings for all users" at the bottom.
In the new options menu that opens up, click on the drop-down in the "Compatability mode" section near the top. The "Windows Server 2003 SP1" option wasn't available on ours. If it is on yours, choose that like BirdDog says, but if your options are like ours, choose "Windows XP SP3"
Next, choose "Run this program as an administrator" at the bottom and hit Apply.
Now open up the SFTP Server program, go to File > Configure and change an option that you were previously getting an error with. For us whenever we set it the "Automatically start with Windows" option under the "Startup & System Tray" tab and clicked "OK" we would get the Unhandled Exception Error. Now we don't and we are able to start/stop the service from within the program (before we could only start/stop it in the Services.msc console).

Hope that helps. Please reply if you have any other issues or different solutions because, despite the age of this post, people are still having problems and this thread is one that shows up when searching, so it could be useful to others.

dmclean

That fixed the issue for me also. Thanks BirdDog!

ctodd_qld

i just installed the Solarwinds SFTP/SCP application onto a clean, new, Windows Server 2016 vm and had problems getting it to start up, similar to above.

I have found that I had to start the application 'as administrator' to be able to either bind a local IP address and start the service within the application.

austinjpoirier

In the past, Solarwinds scheduled task issues have been a permissions issue with the account. I would use the Solarwinds Service Account to run them if possible, assuming it is in the admin group on the server. That way it ensures it has the highest permissions to both the application and the server.