Problems with Inventory Scan
Malcolm Worster
I have recently installed the Landesk Management Suite v6. I have a Core Server and a database server running MS SQL as per the Installation & Deployment guide.
I have deployed the client agent to Win95 w/stations & am able to access them via remote control. However when I perfom an Inventory Scan I get the message "LDISCN32: The inventory server did not respond" . (The environment here is Novell 4.11, protocols TCP/IP & IPX).
On the w/stations I have ensured no TSR's are running, tried running the agent with TCP/IP & IPX protocols, have run LDISCN32.EXE from a Dos prompt with the various parameters as suggested in the manual. I have also rebooted both the core server & database servers & then tried. I still get the same error.
I can run the Desktop Manager successfully from one of the clients on which I am trying to do an inventory. TCP/IP is used as the client protocol to communicate with the SQL database.
Any ideas ?
Thanks in advance.
Malcolm.
Ashley Leonard
Hi Malcolm,
Check to see if the Inventory service is running on the core server, Also
check the NT event logs on the core server for anything to do with the
Inventory Service.
Good luck
Ashley Leonard
Network Dynamics Corporation
Helping organizations deploy LANDesk.
Malcolm Worster wrote in message ...
Lee G
In a message received by Intel on 5/26/98 11:37:00 PM, Malcolm Worster
wrote:
:>I have recently installed the Landesk Management Suite v6. I have a
:>Core Server and a database server running MS SQL as per the
:>Installation & Deployment guide.
:>
:>I have deployed the client agent to Win95 w/stations & am able to
:>access them via remote control. However when I perfom an Inventory Scan
:>I get the message "LDISCN32: The inventory server did not respond" .
:>(The environment here is Novell 4.11, protocols TCP/IP & IPX).
:>
:>On the w/stations I have ensured no TSR's are running, tried running
:>the agent with TCP/IP & IPX protocols, have run LDISCN32.EXE from a Dos
:>prompt with the various parameters as suggested in the manual. I have
:>also rebooted both the core server & database servers & then tried. I
:>still get the same error.
:>
:>I can run the Desktop Manager successfully from one of the clients on
:>which I am trying to do an inventory. TCP/IP is used as the client
:>protocol to communicate with the SQL database.
:>
:>Any ideas ?
:>
:>Thanks in advance.
:>
:> Malcolm.
The server referred to here is the NT server that our product is
installed on. Check to see if the Intel inventory service is running on
the NT server? How were the workstations setup? Did you use
WSCFG32.EXE?
Lee G
ICS-ASC
Intel Internet Support
Malcolm Worseter
Ashley,
I have been able to get Inventory scan to update the Database for one pc, & that was the one running the Core Server. I ran the following from another pc
ldiscn32.exe /v /s=ldmscore /nti=00002331:0000c0a2e998:4007
I could not get this to work consistantly, or at all for any other pc even thought the Inventory Service was running. The client on the pc's has been installed using WSCFG32.EXE .
Meanwhile I checked the NT Event log as you suggested & I am getting the following error:
ODBC generated an exception: Can't allocate space for object 'Syslogs' in database 'master' because the "logsegment" is full. If you ran out of space in Syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment. This transaction has referenced too many databases. The maximum allowed is 16. The transaction must be split into smaller sections. This error is non-recoverable and caused the service to unload itself.
- I have checked Syslogs & there is plenty of space available (49MB's). We lack SQL skills here, so I am not sure from this error if I have a database problem or if the inventory server is trying to to something it should'nt (ie. reference more than 16 Databases).
Thanks in advance,
Malcolm.
Lee Gines
Malcolm Worseter wrote:
It sounds like the TEMPDB has run out of space. What is the size of
TEMDB? We recommend at least 50 megs. The TEMPDB may not have the
"Truncate Log on Checkpoint" configured. start the SQL Enterprise
Manager. Expand the database folder, right click on the TEMPDB and
choose edit, choose the options tab. Make sure the Truncate Log on
checkpoint is selected.
Lee G
Intel Internet Support
ICS-ACS
Malcolm Worster
Lee,
The saga continues ...
I checked the size of Tempdb as suggested. It's 52MB in size with 44MB free. The Truncate log on checkpoint is checked.
I then checked the size of the other databases, including the Master, which is the default device. This was only 17MB with 2MB free. I expanded this to 40MB leaving 25MB free.
I was then able to run a scan on the core server from a remote pc using ldisc32.exe using either IPX or TCPIP. The Inventory Service on the core server also remained running. Prior to this the scan only ran with IPX and the Inventory service would stop.
However I am still unable to run a scan on other pc's - I get the message "LDISCN32: The Inventory Server did not respond" . I am getting no error messages in the event log on the Core Server. I have tried the scan from different pc's, using the various swithches ldiscn32 has available eg. /a /z , all with the same result. I have checked the ldappl.ini file & this looks ok as far as I can tell.
The pc's are all on the same segment as the core server & database server, so slow response should not be a factor.
Any ideas ?
Thanks,
Malcolm.
Intel(R) (Lee G)
Malcolm Worster wrote:
Use the /o= parameter with the scanner. This option will write a file
to the hard drive, you can then see if the scanner will run. I have seen
a corrupt LDAPPl file cause the scanner not to run. /o=c:\scan.txt,
place a file called scan.txt in the root of c. If the scanner places
information in this file then we have a network problem. If the scanner
does not place information in the file then we have a computer or file
problem. You can also take the /I= parameter off the scan line. Rename
the LDAPPL.INI in the LDCLENT directory, and the scanner will run but
only a hardware scan.
--
Malcolm Worster
Lee,
The scanner will create text output to my c:, & will perform the hardware scan to a text file if LDAPPL.INI is renamed. ie. it's starting to look like a network problem. However ....
I checked the Inventory details for the 2 pc's I have been testing on. Despite always receiving the message that the Core Server was not responding, both pc's had a full set of Inventory data. I had not checked this before as the error message suggested that the scan had failed (On one occaision I got the message that the hardware scan had completed but that the software scan had failed. I was unable to repeat this).
I checked the dates/times of the hardware/software scan & they tied in with when I was experimenting with variations of the LDISCN32.EXE command options.
Next step was to delete one of the records, do a CBA discovery to recreate it, & then try an Inventory scan. So far no luck...I get the not responding message again & no Inventory data.
In summary, it appears that despite the error message an inventory scan has managed to write some Inventory data (both Hardware & Software). I'll keep testing to see if I can determine when & if I can then repeat this. Meanwhile have you any suggestions ?
Thanks,
Malcolm.
Intel(R) (Lee G)
Malcolm Worster wrote:
Don't over look the fact that the LDAPPL.INI file local or even on the
server could be corrupt. I did have one problem where a bad LDAPPL.INI
file kept the scanner for working proper. The scan would write to a file
but would not go to the inventory. There is a new one on our web site .