Notification

Icon
Error

Object reference not set to an instance of an object

Posted: Wednesday, October 4, 2017 2:39:15 PM(UTC)
apap

apap

Member Original PosterPosts: 22
0
Like
While deploying a package we have about a dozen nodes that return the following error:
Unexpected failure while connecting to Asset. Object reference not set to an instance of an object.

We are on Version 6.0.100.29
and all the nodes that we are pushing to are Windows 7
Bruce.B
#1Bruce.B Member Administration Posts: 521  
posted: 10/9/2017 4:47:47 PM(UTC)
The error you're receiving on these assets is unfortunately quite a generic null point reference error. I'd recommend checking if the assets in question meet the deployment requirements.

To verify this you can run testconnection.exe which can be found in the Program Files (x86)\Lansweeper\Actions folder on your Lansweeper server. Run the tester directly from your Lansweeper server towards the NetBIOS name of the assets you're getting this error on, using your scanning credentials. The last 2 checks run by the tester need to succeed (c$ and task scheduler check) to be able to deploy on the computer.
apap
#2apap Member Original PosterPosts: 22  
posted: 10/10/2017 6:37:42 PM(UTC)
The Connection Tester comes back without any errors, including the last 2 checks but deployments continue to Object Reference error. Is there anything else we might look at? We have deployed the same package to a few 100 other windows boxes with the same hardware and os build.
thanks ...


Checking C$ Access
Deployment Folder: OK
Access Rights: OK

Checking Task Scheduler
Task was successfully scheduled
Task ran successfully

Task Deleted
RandomAdmin
#3RandomAdmin Member Posts: 5  
posted: 10/10/2017 7:12:34 PM(UTC)
are the trouble computers having an issue with other deployments or just this one? I have had a similar problem in the past and had to delete and then re-add the asset to fix it.
apap
#4apap Member Original PosterPosts: 22  
posted: 10/10/2017 7:40:50 PM(UTC)
All packages tried have failed on this small set of nodes ( the packages work fine elsewhere ).
Deleting and re-adding did not work. Everything adds and scans fine but same deployment error msg.
Bruce.B
#5Bruce.B Member Administration Posts: 521  
posted: 10/11/2017 1:53:52 PM(UTC)
I'd recommend mailing into support@lansweeper.com for this so we can do some debugging if necessary, please include the following:
  • A summary of the issue
  • Program Files (x86)\Lansweeper\Service\Errorlog.txt
  • An export of Deployment\Installer Logs
  • A testconnection.exe output for an asset for which this issue exists, run testconnection.exe directly from your Lansweeper server towards the FQDN of the asset, using your scanning credentials.
erodriguez
#6erodriguez Member Posts: 1  
posted: 12/6/2018 5:36:41 PM(UTC)
I know this is an old post but how did this get resolved. I am having the same issue. Although once in a while my deployment goes through. Been dealing with support and everything seems to checkout. Not sure what to do at this point. Please advise.

Active Discussions

Installer Upgrade Windows 10 to 1803
by  chite   Go to last post Go to first unread
Last post: 11/21/2018 9:11:37 PM(UTC)
Installer LsAgent for Windows
by  kelloggfan  
Go to last post Go to first unread
Last post: 10/24/2018 9:12:26 PM(UTC)
Installer Installer - Firefox 62.0.3
by  kjohnson   Go to last post Go to first unread
Last post: 10/11/2018 8:51:53 PM(UTC)
Installer Office 365 ProPlus Installer
by  maltenburger  
Go to last post Go to first unread
Last post: 8/9/2018 3:20:24 PM(UTC)
Installer Install .Net Framework 4.0
by  StevoCamaro   Go to last post Go to first unread
Last post: 7/9/2018 6:19:58 PM(UTC)
Installer Install .Net Framework 4.7.2
by  Charles.X  
Go to last post Go to first unread
Last post: 7/9/2018 2:29:52 PM(UTC)
Installer Script - Change Desktop and Lock Screen
by  Charles.X   Go to last post Go to first unread
Last post: 7/9/2018 12:06:29 PM(UTC)
Installer Client OS Deployment Template
by  mwrobo09  
Go to last post Go to first unread
Last post: 6/15/2018 9:04:19 PM(UTC)