
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-20-2018 08:14 PM
For some reason I am unable to import the lspush txt files i need to read.
My lspush version is correct and Lansweeper service is working.
My lspush version is correct and Lansweeper service is working.
Labels:
- Labels:
-
General Discussion
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-05-2018 05:05 PM
General log file can be found in Program Files (x86)\Lansweeper\Service\Errorlog.txt.
You'll have to make sure that the file is not modified in any way as it will corrupt the data.
You'll have to make sure that the file is not modified in any way as it will corrupt the data.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-05-2018 04:45 PM
Hi, can i also suggest that the .txt files may be corrupt. My "remote users" run lspush and email me back the text files for import, most all of them failed to import.
So i asked them to ZIP the lspush result file before adding it to the mail and i now have a 100% import success rate.
There is a Lansweeper log file that will actually report on the reason why an import fails (I can't remember where - maybe charles can update this).
Keith
So i asked them to ZIP the lspush result file before adding it to the mail and i now have a 100% import success rate.
There is a Lansweeper log file that will actually report on the reason why an import fails (I can't remember where - maybe charles can update this).
Keith

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-25-2018 12:54 PM
First thing I can think of would be the Lansweeper service not running. As long as the Lansweeper service is running, the lspush files should be automatically imported.
If it isn't the service, I would contact our support team so they can take a look at your errorlogs to see if that provides more insight.
If it isn't the service, I would contact our support team so they can take a look at your errorlogs to see if that provides more insight.
