SMS 1.2 Package Command Manager problem
Hi all,
We're running SMS 1.2 SP3 on an NT network with around 5000 95/98/NT clients. One 95 client has been unable to run packages via PCM for some time, and I'm struggling to find out why.
The job appears in PCM as normal, but when the user clicks Execute, she gets the error "Path not found: F:\Sxxxxxxx" (where 'xxxxxxxx' is the SMS Package ID).
The user has full rights to that share, and I am able to map the drive and run the package manually with no problems on her machine.
I tried mapping F:\ to the correct place before again executing the job from PCM, but all that happens is the error changes to "Path not found: G:\Sxxxxxxx" and so on.
At what point does the temporary network drive get mapped by PCM, and any ideas why this might not be working now? The same package is distributed to all 5000 clients and on the whole, works fine. Also its not just one job causing the problem, every SMS package fails on this client. This particular client is using PCMWIN16 - is this significant, and can I just replace it with PCMWIN32.exe?
Desktop support have uninstalled/reinstalled the SMS client software (so they tell me) so I'm not really sure where to go from here...
Thanks in advance,
Angela
We're running SMS 1.2 SP3 on an NT network with around 5000 95/98/NT clients. One 95 client has been unable to run packages via PCM for some time, and I'm struggling to find out why.
The job appears in PCM as normal, but when the user clicks Execute, she gets the error "Path not found: F:\Sxxxxxxx" (where 'xxxxxxxx' is the SMS Package ID).
The user has full rights to that share, and I am able to map the drive and run the package manually with no problems on her machine.
I tried mapping F:\ to the correct place before again executing the job from PCM, but all that happens is the error changes to "Path not found: G:\Sxxxxxxx" and so on.
At what point does the temporary network drive get mapped by PCM, and any ideas why this might not be working now? The same package is distributed to all 5000 clients and on the whole, works fine. Also its not just one job causing the problem, every SMS package fails on this client. This particular client is using PCMWIN16 - is this significant, and can I just replace it with PCMWIN32.exe?
Desktop support have uninstalled/reinstalled the SMS client software (so they tell me) so I'm not really sure where to go from here...
Thanks in advance,
Angela
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
angela_itr
20 years ago
Thought I'd post the contents of PCMWIN.log to see if this gives anyone any clues? After comparing this with the log file from a working PC, I noticed that the problem PC shows "Running process handle is -1" whereas the working PC shows "Running process handle is 4390". I've searched Google till I'm blue in the face but can't find anything that tells me what these numbers mean... anyone?
[04/15/04] Package Command Manager ==> User clicked on the Execute button.
[04/15/04] Package Command Manager ==> The running process handle is 0
[04/15/04] Package Command Manager ==> A job is not in process.
[04/15/04] Package Command Manager ==> Checking current logon server for package.
[04/15/04] Package Command Manager ==> INFO: SMS_access(szServerBuffer, 0) failed
[04/15/04] Package Command Manager ==> NetShareEnum path:
[04/15/04] Package Command Manager ==> \\BTC030PSBD09003\SMS_PKGD\S0000195\
[04/15/04] Package Command Manager ==> Attempting to connect to package server \\BTC030PSBD09003\SMS_PKGD\S0000195\
[04/15/04] Package Command Manager ==> Connected to current logon server: \\BTC030PSBD09003\SMS_PKGD\\S0000195\
[04/15/04] Package Command Manager ==> The unvalidated command line is 98a219c.bat
[04/15/04] Package Command Manager ==> The location of the MSTest directory is \\BTC030PSBD09003\SMS_SHR\mstest\
[04/15/04] Package Command Manager ==> The drive and directory for the package is G:\S0000195\
[04/15/04] Package Command Manager ==> Changed to the package directory.
[04/15/04] Package Command Manager ==> Took action on the validated command line: G:\S0000195
[04/15/04] Package Command Manager ==> Monitoring running job.
[04/15/04] Package Command Manager ==> The running process handle is -1
[04/15/04] Package Command Manager ==> A job is in process.
[04/15/04] Package Command Manager ==> Executed process terminated, cleaning up.
[04/15/04] Package Command Manager ==> Reporting on completed package execution.
[04/15/04] Package Command Manager ==> An error was detected while attempting to run the job.
[04/15/04] Package Command Manager ==> Writing status information to \\BTC030PSBD09003\SMS_SHR\despoolr.box
[04/15/04] Package Command Manager ==> Attempting to refresh package collection from logon server.
[04/15/04] Package Command Manager ==> Connected to logon server: \\BTC030PSBD09003\SMS_SHR\pcmins.box
[04/15/04] Package Command Manager ==> Looking for instruction file: \\BTC030PSBD09003\SMS_SHR\pcmins.box\S001Q39L.INS
[04/15/04] Package Command Manager ==> Packages before filter: 1
[04/15/04] Package Command Manager ==> Packages after filter: 1
[04/15/04] Package Command Manager ==> No new packages found.
[04/15/04] Package Command Manager ==> Package (Request ID) S000488 has a view mode and can be executed.
[04/15/04] Package Command Manager ==> There is 1 item to display.
[04/15/04] Package Command Manager ==> User clicked on the Execute button.
[04/15/04] Package Command Manager ==> The running process handle is 0
[04/15/04] Package Command Manager ==> A job is not in process.
[04/15/04] Package Command Manager ==> Checking current logon server for package.
[04/15/04] Package Command Manager ==> INFO: SMS_access(szServerBuffer, 0) failed
[04/15/04] Package Command Manager ==> NetShareEnum path:
[04/15/04] Package Command Manager ==> \\BTC030PSBD09003\SMS_PKGD\S0000195\
[04/15/04] Package Command Manager ==> Attempting to connect to package server \\BTC030PSBD09003\SMS_PKGD\S0000195\
[04/15/04] Package Command Manager ==> Connected to current logon server: \\BTC030PSBD09003\SMS_PKGD\\S0000195\
[04/15/04] Package Command Manager ==> The unvalidated command line is 98a219c.bat
[04/15/04] Package Command Manager ==> The location of the MSTest directory is \\BTC030PSBD09003\SMS_SHR\mstest\
[04/15/04] Package Command Manager ==> The drive and directory for the package is G:\S0000195\
[04/15/04] Package Command Manager ==> Changed to the package directory.
[04/15/04] Package Command Manager ==> Took action on the validated command line: G:\S0000195
[04/15/04] Package Command Manager ==> Monitoring running job.
[
[04/15/04] Package Command Manager ==> A job is in process.
[04/15/04] Package Command Manager ==> Executed process terminated, cleaning up.
[04/15/04] Package Command Manager ==> Reporting on completed package execution.
[04/15/04] Package Command Manager ==> An error was detected while attempting to run the job.
[04/15/04] Package Command Manager ==> Writing status information to \\BTC030PSBD09003\SMS_SHR\despoolr.box
[04/15/04] Package Command Manager ==> Attempting to refresh package collection from logon server.
[04/15/04] Package Command Manager ==> Connected to logon server: \\BTC030PSBD09003\SMS_SHR\pcmins.box
[04/15/04] Package Command Manager ==> Looking for instruction file: \\BTC030PSBD09003\SMS_SHR\pcmins.box\S001Q39L.INS
[04/15/04] Package Command Manager ==> Packages before filter: 1
[04/15/04] Package Command Manager ==> Packages after filter: 1
[04/15/04] Package Command Manager ==> No new packages found.
[04/15/04] Package Command Manager ==> Package (Request ID) S000488 has a view mode and can be executed.
[04/15/04] Package Command Manager ==> There is 1 item to display.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.