cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
koglerh
Engaged Sweeper III
I am running Lansweeper 5.2.0.42 and get this Error when installing packages via Schedules on our remote office:

Initialization Failed! Task Service Error. Task Scheduler 2.0 (1.2) does not support setting this property. You must use an InteractiveToken in order to have the task run in the current user session


When i install a package on the remote office via "deploy package" i get this error message:

Initialization Failed! Task Service Error. The network path was not found. (Exception from HRESULT: 0x80070035) Credential: (xxxxx\Administrator).


When i log on to a PC with the given credentials i can access the network path and install the software from there.
Everything is fine at the headquarters, so the package and the credentials are not the problem. Any ideas?
1 ACCEPTED SOLUTION
Susan_A
Lansweeper Alumni
No, we haven't made any port changes. Lansweeper accesses Windows computers through WMI (Windows Management Instrumentation). WMI data is by default sent over random ports. For Windows 2008 and higher and Windows Vista and higher, the dynamic port ranges should be 49152 through 65535 and 1025 through 5000, according to Microsoft's knowledge base.

You should either allow *all* WMI traffic through your firewalls or set up a fixed WMI port instead. See this article on Windows scanning requirements.

View solution in original post

4 REPLIES 4
koglerh
Engaged Sweeper III
ok thx!
Susan_A
Lansweeper Alumni
No, we haven't made any port changes. Lansweeper accesses Windows computers through WMI (Windows Management Instrumentation). WMI data is by default sent over random ports. For Windows 2008 and higher and Windows Vista and higher, the dynamic port ranges should be 49152 through 65535 and 1025 through 5000, according to Microsoft's knowledge base.

You should either allow *all* WMI traffic through your firewalls or set up a fixed WMI port instead. See this article on Windows scanning requirements.
koglerh
Engaged Sweeper III
After further investigations we could figure out, that one port (tcp 49154) was blocked by our firewall. did you change something in the oport configuration between version ~5.2.0.30 and the current 5.2.0.42? anyways, the issue has been resolved now!
Susan_A
Lansweeper Alumni
Could you contact support@lansweeper.com and provide the information listed below. We will troubleshoot via email.
  • Description of the problem.
  • Program Files (x86)\Lansweeper\Service\Errorlog.txt, as present on your Lansweeper server.
  • Export of the deployment package you are trying to run.
  • Excel export of the Deployment\Logs page. (Hit the export button on the left.)