Microsoft KB Archive/938353

= The job status for all transactions is listed as &quot;InProgress&quot; even after the transactions have successfully completed in Windows XP Home Edition for Prepaid Computers or in Windows XP Home Edition for Subscription Computers =

Article ID: 938353

Article Last Modified on 8/14/2007

-

APPLIES TO


 * Microsoft Windows XP Home Edition for Prepaid Computers
 * Microsoft Windows XP Home Edition for Subscription Computers

-





SYMPTOMS
On a computer that is running Microsoft Windows XP Home Edition for Prepaid Computers or Microsoft Windows XP Home Edition for Subscription Computers, the CSR page lists the status of all prepaid packet transactions and confirmation packet transactions as &quot;InProgress.&quot; This status is listed as &quot;InProgress&quot; even after the transactions have successfully completed. Additionally, the Summary page shows diagnostic code 1 and diagnostic code 3 for each job ID.

This problem occurs if the computer is behind a proxy server.

The customer does not experience any problems as long as the transactions complete successfully. However, because multiple transactions display the &quot;InProgress&quot; status, a troubleshooter cannot determine the specific transaction that failed if a problem occurs.



CAUSE
This issue occurs when the client requests a provisioning packet, and the provisioning servers have already created a provisioning packet. The &quot;InProgress&quot; job status means that the client has tried to download the packet from the servers. Before the server changes the job status to &quot;Succeeded,&quot; the provisioning server waits to receive an acknowledgement (ACK) from the client. If the customer receives the time from the client but disconnects the network connection before the client sends the acknowledgement, the job status remains listed as &quot;InProgress.&quot;

Because of the proxy server, the Microsoft servers never receive the acknowledgement that the client sends to verify that the client received the information. Therefore, the transaction status is never updated, even though the transaction was successfully completed.



WORKAROUND
To work around this issue, run the following command at a command prompt: plactive /k This command manually sends acknowledgements to the Microsoft server. Additionally, the command updates the status of all previously completed transactions.



MORE INFORMATION
After a client computer sends a use time token to a prepaid computer, and a back-end server processes the token correctly, the distribution server creates a prepaid provisioning packet for pickup. If the client computer successfully sends a request, the time is added to the client computer. If the client requests a download, the job status changes from &quot;Created&quot; to &quot;InProgress.&quot; Most of the jobs that have a status of &quot;InProgress&quot; receive the provisioning packet before the download starts. When the client sends an acknowledgement to the provisioning servers, the job status changes to &quot;Succeeded.&quot;

To make sure that the server continually reflects the correct transaction status, we recommend that you perform the manual update process after every transaction. However, because the manual update corrects the status of every previously completed transaction, you can also perform the manual update only when troubleshooting is necessary.

Keywords: kbtshoot kbprb KB938353

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.