Author Topic: Error codes 2503 and 2502  (Read 111 times)

Offline Graham1

  • Jr. Member
  • **
  • Posts: 70
    • View Profile
Error codes 2503 and 2502
« on: May 15, 2019, 04:14:41 PM »
I have just tried (several times, including after reboot) to install the latest PM6 update (3143) on my desktop computer (Windows 10).  The installation does not complete, coming up with, successively, error code 2503 then 2502 dialogue boxes.  It installed with no problem on my Windows 10 laptop.  Any ideas?  Thanks.

Graham

Offline Jerry H

  • Camera Bits Staff
  • Full Member
  • *****
  • Posts: 157
    • View Profile
    • Camera Bits, Inc.
Re: Error codes 2503 and 2502
« Reply #1 on: May 15, 2019, 05:41:56 PM »
That error seems to be related to a permissions problem, although I'm unclear as to the source of the permissions problem.

If you're comfortable working in the Command Prompt, you can try running the installer from a Command Prompt window as admin. Press Windows+R to open the “Run” box. Type “cmd” into the box and then press Ctrl+Shift+Enter to run the command as an administrator.

In the Command Prompt window enter cd /d %USERPROFILE% and hit Return to change the directory to your home folder. Now enter msiexec /package Downloads\PM6SetupR3143.msi to run the Photo Mechanic 6 build 3143 installer, assuming the installer is located in your Downloads folder, otherwise replace Downloads with the path to the installer.

If the above doesn't resolve the problem, or you're not comfortable using the Command Prompt, follow the link below for other possible solutions.

https://answers.microsoft.com/en-us/windows/forum/all/internal-error-25032502/28b361b7-b2d7-494d-8470-5969f6850f5a

HTH,

-Jerry

Offline Graham1

  • Jr. Member
  • **
  • Posts: 70
    • View Profile
Re: Error codes 2503 and 2502
« Reply #2 on: May 16, 2019, 12:54:46 AM »
Thanks, Jerry

The specific solution you suggested did not work, but the link you provided was very helpful.  For the benefit of anyone else with the same problem, the solution that worked for me was running from the elevated command prompt, as explained in a post by a user called CliveJFox.  This happened shortly after one of those all too frequent Windows 10 updates, which I guess broke something, as so often seems to happen.  I had done my laptop PM6 update installation before the same Win 10 update, which perhaps explains why that worked, but my desktop installation had the problem.

Graham