Error 1613: Possible parameter count mismatch in Process.StartInfo.Arguments.

BatchPatch Forums Home Forums BatchPatch Support Forum Error 1613: Possible parameter count mismatch in Process.StartInfo.Arguments.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #9057
    coachep
    Participant

    When using BatchPatch, about 1/3 of my servers have been receiving the following error.

    Error 1613: Possible parameter count mismatch in Process.StartInfo.Arguments. The system cannot find the file specified. HRESULT: -2147024894

    If is start a new BatchPatch session, some with the servers that received the error will run fine.

    #10767
    doug
    Moderator

    coachep – Please take a look at the following link: Error 1613: Possible parameter count mismatch

    Let me know what you determine.

    Thanks,

    Doug

    #10768
    coachep
    Participant

    Doug,

    On some of the computers that have the mismatch error, I am able to successfully run the following command, psexec \targetcomputer IPCONFIG. Also, when using BatchPatch, if i check multiple times for available windows updates, i can eventually get BatchPatch to communicate with the server and run the updates. Take a look at the following log file that shows the error and then a successful connection.

    BTW, we are using V2014.8.13.22.50.

    All Messages

    Wed-11:58:10> Windows Update: Download operation completed

    Wed-11:57:49> Windows Update: Executing BatchPatchRemoteAgent.exe…

    Wed-11:57:46> Windows Update: Attempting to initiate Windows update (download updates) …

    Wed-11:57:46> Windows Update: Establishing connection…

    Wed-11:57:45> Windows Update: Initializing…

    Wed-11:57:45> Windows Update: Queued…

    Wed-11:55:39> Windows Update: 25 update(s) found

    Wed-11:55:32> Windows Update: Executing BatchPatchRemoteAgent.exe…

    Wed-11:55:32> Windows Update: Attempting to initiate Windows update (search for updates) …

    Wed-11:55:31> Windows Update: Establishing connection…

    Wed-11:55:31> Windows Update: Initializing…

    Wed-11:55:30> Windows Update: Queued…

    Wed-11:48:56> Windows Update: Error 1613: Possible parameter count mismatch in Process.StartInfo.Arguments. The system cannot find the file specified. HRESULT: -2147024894

    Wed-11:48:49> Windows Update: Executing BatchPatchRemoteAgent.exe…

    Wed-11:48:49> Windows Update: Attempting to initiate Windows update (search for updates) …

    Wed-11:48:49> Windows Update: Establishing connection…

    Wed-11:48:49> Windows Update: Initializing…

    Wed-11:48:49> Windows Update: Queued…

    Wed-11:46:11> Windows Update: Error 1613: Possible parameter count mismatch in Process.StartInfo.Arguments. The system cannot find the file specified. HRESULT: -2147024894

    Wed-11:46:05> Windows Update: Executing BatchPatchRemoteAgent.exe…

    Wed-11:46:04> Windows Update: Attempting to initiate Windows update (search for updates) …

    Wed-11:46:03> Windows Update: Establishing connection…

    Wed-11:46:03> Windows Update: Initializing…

    Wed-11:46:02> Windows Update: Queued…

    Wed-11:44:42> Remote Command: Exit Code: 0 (SUCCESS)

    Wed-11:44:41> Remote Command: Executing \Z1APP01 wuauclt.exe /resetauthorization /detectnow

    Wed-11:44:41> Remote Command: Establishing connection…

    Wed-11:44:41> wuauclt.exe /resetauthorization /detectnow: Queued…

    Wed-11:39:47> Windows Update: Error 1613: Possible parameter count mismatch in Process.StartInfo.Arguments. The system cannot find the file specified. HRESULT: -2147024894

    Wed-11:39:41> Windows Update: Executing BatchPatchRemoteAgent.exe…

    Wed-11:39:40> Windows Update: Attempting to initiate Windows update (search for updates) …

    Wed-11:39:40> Windows Update: Establishing connection…

    Wed-11:39:39> Windows Update: Initializing…

    Wed-11:39:38> Windows Update: Queued…

    Wed-11:03:55> Pending Reboot Status: FALSE

    Wed-11:03:53> Pending Reboot: Attempting to retrieve pending reboot information…

    Wed-11:00:37> Remote Command: Exit Code: 0 (SUCCESS)

    Wed-11:00:37> Remote Command: Executing \Z1APP01 wuauclt.exe /resetauthorization /detectnow

    Wed-11:00:37> Remote Command: Establishing connection…

    Wed-11:00:35> wuauclt.exe /resetauthorization /detectnow: Queued…

    Wed-11:00:11> Windows Update configuration: http://iops03:8530

    Wed-11:00:08> Windows Update configuration: Attempting to retrieve Windows Update configuration…

    Wed-06:52:12> Windows Update: Error 1613: Possible parameter count mismatch in Process.StartInfo.Arguments. The system cannot find the file specified. HRESULT: -2147024894

    Wed-06:52:04> Windows Update: Executing BatchPatchRemoteAgent.exe…

    Wed-06:52:02> Windows Update: Attempting to initiate Windows update (search for updates) …

    Wed-06:52:00> Windows Update: Establishing connection…

    Wed-06:51:58> Windows Update: Initializing…

    Wed-06:51:53> Windows Update: Queued…

    #10770
    doug
    Moderator

    Sounds like something a bit fishy happening on the computer running BP. Considering the fact that every time you execute it, BP is executing the exact same thing, but sometimes it’s working and sometimes it’s not, it seems to me that you should start by rebooting the system that is running BP, and then reboot the targets.

    If you run the psexec command manually a number of times, does it ever fail? I know you said it didn’t fail the one time you tested it, but we also know that BP is not failing every time either. The error that is being triggered in BP is one that should, in theory, never be able to be reached, except in the event that psexec is not behaving properly.

    Also, did you check the other posting that I had pointed you to, which mentioned the use of mandatory profiles? That’s the only thing that I’m aware of that will break psexec 100% of the time, and therefore it will also break functionality in BP that utilizes psexec.

    In any case, I’d still suggest rebooting the BP machine and targets in question, and see if that has any impact.

    -Doug

    #10763
    coachep
    Participant

    thanks for the update. Due to fact that BatchPatch is on a production machine, i will not be able to reboot it for two weeks. I will keep this in mind for April patching. I will also try running psexec multiple times to various remote computers and see if i can find a connection pattern. We are not running mandatory profiles, so i do not think that would be the issue.

    #10764
    doug
    Moderator

    OK, sounds good. Keep me posted. I’ll be curious to learn what, if anything, you find.

    Thanks,

    Doug

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.