
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-10-2009 08:23 AM
I've setup lansweeper to scan for 2 files. One of the files is an .exe file and one is a .dll file.
The main reason to scan the files is to show wich version it is.
It always says that the files are present but sometimes the rest of the information is not displayed.
The most important information (the version of the file) is sometimes blank and sometimes not.
This happens with both files on radomly computers within the domain.
What can it be?
The main reason to scan the files is to show wich version it is.
It always says that the files are present but sometimes the rest of the information is not displayed.
The most important information (the version of the file) is sometimes blank and sometimes not.
This happens with both files on radomly computers within the domain.
What can it be?
Labels:
- Labels:
-
Archive
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2009 03:02 PM
Does the empty information always happens with the same computer or is it one scan ok and next scan blank?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-11-2009 02:13 PM
I have the latest service running 3.5.2.4
executable is not made with dotnet framework
File version is not to long (because it sometimes displays it and sometimes it doesn't)
executable is not made with dotnet framework
File version is not to long (because it sometimes displays it and sometimes it doesn't)

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-10-2009 09:10 PM
First check if you have the lastest lansweeperservice.exe
1) This problem can also happen when scanning executables made with dotnet framework. (WMI can not do this yet)
2) It could be that the fileversion is too long (database is set to 50 characters)
1) This problem can also happen when scanning executables made with dotnet framework. (WMI can not do this yet)
2) It could be that the fileversion is too long (database is set to 50 characters)
