1 Reply Latest reply on Jan 30, 2013 12:29 AM by igaydajiev

    Orchestrator v4.2 "Access not allowed" after jar replacements (KB)

    Bar2D2 Novice

      I implemented http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2031391 to fix the performance issues with my client v.4.2.1.555 but now I get ACCESS NOT ALLOWED when I try to login.

      I can't login the Orchestrator configuration interface either, I get user/password mismatch

      I checked the permissions on the new jar files.

      Anybody had the same issue and fixed this?