I have a 4.1 server / 4.2 client environment and today I tried to install the 4.5 client to connect to my 4.1 servers. I found that a number of my apps stopped working. Error code 0A-00000163 which MS says there is a guid issue and to re sequence. This app worked fine in 4.2 why is it broken in 4.5 (only the client changed, if I uninstall and go back to 4.2 it works again). I have over 1500 sequenced applications and this is happening on a fairly large percentage ranging from apps as simple as winzip (yep winzip didnt work) to more complicated custom apps. I'd prefer to fix them rather then re sequence them all. If anyone has any ideas or has seen this it would be greatly appreciated.

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


I am faced with the same issue.
I have had to resequence, reimport the OSD in the console.

I am concerned about the time it takes to do this as well as the errors that can occur resequencing old apps.

Thanks for any input.
Answered 12/17/2008 by: MikeDoyle
Yellow Belt

Please log in to comment
I would recommend upgrading the App-V server first.

Aside from that we have a limited deployment of App-V 4.5 terminal servers connected to a 4.1 SP0 server with no issues.
Answered 01/13/2009 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment

If you still have those issues with packages needing new GUIDs, I'd like to point you to my newly released tool which is able to do GUID regeneration:

It's for cost, but not too expensive for the time you'll save by not having to re-sequence.

Of course, if you re-generate GUIDs, from client perspective those will be new packages so all cached setting will be lost. Also without changing the root directory name, packages with new GUIDs cannot co-exist on client cache with the old ones (deleting them away from client solves this).

Answered 01/20/2009 by: ksaunam
Orange Senior Belt

Please log in to comment