
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-20-2025 03:15 PM
Hi All,
The latest version Lansweeper deployment package preliminary checks failed. Task Registering Error. Value does not fall within the expected range. Credential: (.\Lansweeper). ShareCredential: (Deployer). ExecutionMode (System).
Lansweeper Server v12.3.3.0
LsAgent Windows 12.2.0.1

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Hi FrankSC,
After Lansweeper server upgraded to v12.4.0.1, parts of target machine still deployment failed. Alreay tried below two steps, but still unsucessful deployment. Can you advise how can I troubleshoot the issue? Thanks.
Result: Package timeout reached. Unknown last result. Timeout: (900Sec). Credential: (.\Lansweeper). ShareCredential: (Deployer). Scheduled Task not present.
https://community.lansweeper.com/t5/quick-tech-solutions/deployments-package-timeout-reached-unknown...
Copy the Command of your step and manually run it in Command Prompt on a target machine to see if it works. (Working)
Replace {packageshare} with the UNC path of your package share as defined under Deployment\Security Options. (Not Working)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Hey Danny - it's not best practice, but... I always use the IP address of the server 🙂 Have you tried the 'testconnection.exe' tool located at C:\Program Files (x86)\Lansweeper\Actions ? Give that a go

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Hi Jacob,
Testconnection result was okay, but deployment failed even using default package share path with IP \\192.168.100.99\DefaultPackageShare$. What can I do next?
Lansweeper Connection Tester 7.1.0.1
Scanning Lansweeper Service (on this machine)..
Status: Running
Version: 12.4.0.1
Pinging 192.168.100.14
Ping ok.
Scanning TCP ports..
135 open (EPMAP)
139 open (NetBIOS Session Service)
445 open (SMB)
Checking DNS..
192.168.100.14 resolved to: 192.168.100.14
If this is not correct, please check for DNS problems.
Checking reverse DNS..
192.168.100.14:
PC-CSR
Scanning netbios (UDP)..
Computername: PC-CSR
Domain: WORKGROUP
Scanning netbios (445)..
Could not scan netbios
Scanning Active Directory..
Error: The specified domain does not exist or cannot be contacted.
Domain: WORKGROUP
Scanning WMI..
Computername: PC-CSR
If this is not correct, please check for DNS problems
Operating system: Microsoft Windows 10 Pro
\root\cimv2 Remote WMI access test OK
Operating system: Windows 10 Pro
\root\default Remote WMI access test OK
Checking C$ Access
Deployment Folder: OK
Access Rights: OK
Checking Task Scheduler
Task was successfully scheduled
Task ran successfully
Task Deleted
Done.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-21-2025 10:19 AM
Hello Danny_Summer,
We will include a few fixes in our next release for deployments. The error you are seeing can occur in a few scenario's, I assume yours is one of them.
Our new version, 12.4 will be released soon.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-21-2025 11:51 AM
Hi FrankSC
Thanks for your information. Waitting for the next release to fix the issue, thanks.
