Monday, November 5, 2012

PeopleSoft Application Designer - Missing or invalid version of SQL library PSORA(200,0)

In this doodle, I will discuss about one of the common error message developers used to see when they are setting up their new workstation or after oracle upgrade or new oracle installations.

After you launch your application designer, you will prompted for PeopleSoft user id and password. After you enter your credentials you will be displayed with the error message " Missing or invalid version of SQL library PSORA (200,0)" as shown in the below screenshot.

First Reason is "start in" path that you have specified for your application designer is invalid. Application designer use this path to locate the Oracle client bin folder.

Right click on the PSIDE.exe shortcut that you have on your machine. Click on the Properties,you will be displayed with the dialog box. Specify path of the oracle bin folder  in "Start in" as highlighted in the below screenshot

Second reason is valid if you are using PeopleTools 8.5x. In this case, your application designer is trying to access 64bit Oracle client library.

PeopleTools 8.5x is certified to run on 64bit windows but the application designer pside.exe is 32bit utility. This means any library that need to be loaded by this 32bit utility has to be 32bit. Due to this you need to make sure Oracle 32bit version is installed in your machine to avoid this error message.

You can identify your Oracle version through the below SQL. This is one of the way.


The banner will tell you 64-bit if the 64-bit version is installed. If it does not specify 64-bit then it is 32-bit (even though it does not explicitly say so). You will get the same information when using SQL*PLUS.


  1. Hi, The problem are sucessfull whit this instructions.
    however, chek the secction names of the tnsnames.ora because the spaces ( " " ) is not a valid configuration before the section connection name. There is another reason, and the solution of the relationated error.

  2. mypeoplesoft is PeopleSoft ERP applicant is a technical and business support leading in the IT world through management, strategies, consulting and latest trends.

  3. Have reinstalled PeopleTools 7 which is our archived database. Using windows 7. Getting error Missing or invalid varsion of SQL library PSORA.DLL (0, 0)........Im not a developer however I'm trouble shooting this for a number of users ........any ideas or is this such an old version of People Tools that it's not compatible with WIN 7?

    1. Check the path in which Oracle is been installed. Make sure environment variable is setup with this path.

  4. I am testing new tools env PT853 install and I ran into the error: "Missing or invalid version of SQL library PSORA32 (200,0) Reason: SQL library not initialized (200,0)" as I ran an AE two tier.

    THE PSIDE is not on my local's properties are from the server. The results of the SQL SELECT * FROM V$VERSION;

    Oracle Database 11g Enterprise Edition Release - 64bit Production
    PL/SQL Release - Production
    CORE Production
    TNS for Linux: Version - Production
    NLSRTL Version - Production

    What would I do to resolve this issue since I don't have it installed locally?

    1. Hi C D Cox. Do you have an answer on this? I am stuck with a similar problem. Appreciate your help!!

    2. Referencing the 32bit oracle home before the 64 bix in the evnironment varible fixed my issue.

  5. Hi C D Cox. Do you have an answer on this? I am stuck with a similar problem. Appreciate your help!!

  6. add the path of your Oracle 32 bit client bin directory at the beginning of your %PATH% variable and check .

  7. Folks, I had been tearing my hair out with the psora32 error, and wanted to mention another thing to check: firewalls. In my case it turned out that the windows firewall was blocking something that was causing this error. If you're sure that all the paths, environment variables, registry settings, etc are correct, look at any firewalls or other connection issues between the client and the database that they are trying to reach! Don't forget to verify the tnsnames.ora as well. What a hatefully misleading error.