‎04-28-2016 10:22 PM
Solved! Go to Solution.
‎05-09-2016 12:54 AM
An entry is only added to tblFloppyHist if there is a change in one or more fields of tblFloppy. Possible explanations we can think of for the behavior you're seeing:
- Your report is built incorrectly. This seems unlikely.
- There was a change in a field that you're not displaying in your report output. We recommend displaying *all* tblFloppyHist fields in your report.
- You have multiple scanning servers scanning the same machine and not all of them are on the same Lansweeper release. We added some fields to the tblFloppy table at one point. If you have two scanning servers scanning a client machine, one old and one new, the new one will scan the new fields while the old one won't. This would cause "changes" to be detected that didn't actually occur on the client machine. Please double-check that all Lansweeper component numbers listed under Configuration\Your License are 5.3.0.34. If they aren't, please update all servers to Lansweeper release 5.3.0.34 by following the instructions in this knowledge base article and verify whether incorrect drive changes are reported again in the future.
If the information above doesn't explain the issue, could you provide us with the following to help us troubleshoot:
- Program Files (x86)\Lansweeper\Service\Errorlog.txt, as present on the Lansweeper server that scanned the problem client machines.
- Screenshot of the Configuration\Your License section of the Lansweeper web console.
- Output of the debug report below, in Excel format. Instructions for adding this report to your Lansweeper installation can be found here.
Select Top 1000000 tblAssets.AssetID As ID,
tblAssets.AssetUnique As [Unique],
tblAssets.Assettype,
tblAssets.Firstseen,
tblAssets.Lastseen,
tblAssets.Lasttried,
tblAssets.Lasttriggered,
tblAssets.LastScheduled,
tblAssets.LastActiveScan,
tblAssets.LastIPScan,
tblAssets.LastLsPush,
tblAssets.lastWorkgroupScan,
tblAssets.LastSaved,
tblAssets.Scanserver,
tblAssets.ServiceVersion,
tblAssets.LsPushVersion,
tblFloppyHist.bytespersector,
tblFloppyHist.InterfaceType,
tblFloppyHist.Manufacturer,
tblFloppyHist.Model,
tblFloppyHist.Name,
tblFloppyHist.Partitions,
tblFloppyHist.Sectorspertrack,
tblFloppyHist.Size,
tblFloppyHist.Totalcylinders,
tblFloppyHist.Totalheads,
tblFloppyHist.Totalsectors,
tblFloppyHist.Totaltracks,
tblFloppyHist.TracksperCylinder,
tblFloppyHist.Lastchanged,
tblFloppyHist.Action
From tblAssets
Inner Join tblFloppyHist On tblAssets.AssetID = tblFloppyHist.AssetID
Order By tblFloppyHist.Lastchanged Desc
‎10-05-2016 10:23 AM
Select Top 1000000 tblAssets.AssetID As ID,
tblAssets.AssetUnique As [Unique],
tblAssets.Assettype,
tblAssets.Firstseen,
tblAssets.Lastseen,
tblAssets.Lasttried,
tblAssets.Lasttriggered,
tblAssets.LastScheduled,
tblAssets.LastActiveScan,
tblAssets.LastIPScan,
tblAssets.LastLsPush,
tblAssets.lastWorkgroupScan,
tblAssets.LastSaved,
tblAssets.Scanserver,
tblAssets.ServiceVersion,
tblAssets.LsPushVersion,
tblFloppyHist.bytespersector,
tblFloppyHist.InterfaceType,
tblFloppyHist.Manufacturer,
tblFloppyHist.Model,
tblFloppyHist.Name,
tblFloppyHist.Partitions,
tblFloppyHist.Sectorspertrack,
tblFloppyHist.Size,
tblFloppyHist.Totalcylinders,
tblFloppyHist.Totalheads,
tblFloppyHist.Totalsectors,
tblFloppyHist.Totaltracks,
tblFloppyHist.TracksperCylinder,
tblFloppyHist.Lastchanged,
tblFloppyHist.Action
From tblAssets
Inner Join tblFloppyHist On tblAssets.AssetID = tblFloppyHist.AssetID
Order By tblFloppyHist.Lastchanged Desc
‎10-04-2016 06:27 PM
‎07-26-2016 06:55 PM
‎05-09-2016 12:54 AM
An entry is only added to tblFloppyHist if there is a change in one or more fields of tblFloppy. Possible explanations we can think of for the behavior you're seeing:
- Your report is built incorrectly. This seems unlikely.
- There was a change in a field that you're not displaying in your report output. We recommend displaying *all* tblFloppyHist fields in your report.
- You have multiple scanning servers scanning the same machine and not all of them are on the same Lansweeper release. We added some fields to the tblFloppy table at one point. If you have two scanning servers scanning a client machine, one old and one new, the new one will scan the new fields while the old one won't. This would cause "changes" to be detected that didn't actually occur on the client machine. Please double-check that all Lansweeper component numbers listed under Configuration\Your License are 5.3.0.34. If they aren't, please update all servers to Lansweeper release 5.3.0.34 by following the instructions in this knowledge base article and verify whether incorrect drive changes are reported again in the future.
If the information above doesn't explain the issue, could you provide us with the following to help us troubleshoot:
- Program Files (x86)\Lansweeper\Service\Errorlog.txt, as present on the Lansweeper server that scanned the problem client machines.
- Screenshot of the Configuration\Your License section of the Lansweeper web console.
- Output of the debug report below, in Excel format. Instructions for adding this report to your Lansweeper installation can be found here.
Select Top 1000000 tblAssets.AssetID As ID,
tblAssets.AssetUnique As [Unique],
tblAssets.Assettype,
tblAssets.Firstseen,
tblAssets.Lastseen,
tblAssets.Lasttried,
tblAssets.Lasttriggered,
tblAssets.LastScheduled,
tblAssets.LastActiveScan,
tblAssets.LastIPScan,
tblAssets.LastLsPush,
tblAssets.lastWorkgroupScan,
tblAssets.LastSaved,
tblAssets.Scanserver,
tblAssets.ServiceVersion,
tblAssets.LsPushVersion,
tblFloppyHist.bytespersector,
tblFloppyHist.InterfaceType,
tblFloppyHist.Manufacturer,
tblFloppyHist.Model,
tblFloppyHist.Name,
tblFloppyHist.Partitions,
tblFloppyHist.Sectorspertrack,
tblFloppyHist.Size,
tblFloppyHist.Totalcylinders,
tblFloppyHist.Totalheads,
tblFloppyHist.Totalsectors,
tblFloppyHist.Totaltracks,
tblFloppyHist.TracksperCylinder,
tblFloppyHist.Lastchanged,
tblFloppyHist.Action
From tblAssets
Inner Join tblFloppyHist On tblAssets.AssetID = tblFloppyHist.AssetID
Order By tblFloppyHist.Lastchanged Desc
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now