SQL & PL/SQL

Have you tried to run them as different users with different PS_HOME environment variables set for the users as well as their own sets of registry entries?

until 8.49 PS_HOME dll's are different in the registry entiresfor each peopletools. this means u can have 8.46 with any combination of other ps_home upto 8.49

from 8.50 u cannot have anything that is older than 8.5 . dll's everytime when u run setup.exe gets backed up and updated. really u cannot work on both PS_homes at the same time with what u have.

This is working as per designed

However, that works fine if settings are same, especially connectid and connect password. We have PT8.22.x, PT8.45.x, PT8.48.x and PT8.50.x on same workstation and didn't see any issue.

Nicolas.

Hi Nicholas,

we are using 8.47 tools and recently also installed 8.5 tools and the problem started. if i use 85 - i cant use 847 or vice - versa. Everytime i have to import the config to make it work.

Connect ID /Passwrd are all same, is it something to do with the registry?

both tools have separate PS_HOME and are taking binaries (tnsnames.ora) from 1 path.

Please advise on how to proceed on this or do we continue like this -- import everytime you want to use whichever tools version

Also advise on check for the settings, if that may help

Thanks.

if u want to use both , means you are looking for something to toggle between the env's.

create a .bat file for the install of workstations(simple ex: use psodbccrinst.exe,pscfg.exe to run on the bat files for different env,s)

everytime u run .bat for PT847 dll's on psodbccrinst.exe register for 847 and u can use it. similarly for PT8.50

don't forget to import pscfg.exe onto the client. just preparing a switch like on and off between clients.

u save time, should be like 5 mins to switch over....

Thnks!

Hi, Thanks for the suggestion.

Let me try to work this out and get back to you.

Also - is this a known issue b/w 85 tools and any lower version.

Secondly - the .bat file that u suggested -- how would it work in my case - as we use different remote desktop connections and there are few 100 users who also use it at sometime - to connect to various instances either on 847 or 85.

so do we place the bat file at a common location which is accessible to everyone or i mean how do you suggest this will work.

plus -- reg. importing of the pscfg.exe on the client -- how do you think - this is suppose to work on user level or a terminal server location.

Please Suggest - Thanks for you help

Hi Nicholas,

I was able to install PT 8.46 and PT 8.50 on users desktop, we have two different PS_HOMEs and we use a bat file to switch between the two version, every time when we run the bat file it imports the cfg file... we can open App Designer for both the version but the problem is we are not able to run nVision for both the PT versions.

Lets say, if i installed PT 846 first and then PT 850 client next, i am only able to open nVision for PT 8.50, when i try to open nVision for PT 846, its erroring out saying nVision is not configured properly.

What ever tools that was installed last, it open the nVision of that version only and erroring out for the other.

Is there any way we can open PSnVision for both the versions one after the other.

Thanks,
Chris

I too had a similar issue. In my project we have to work on production support on 847 & upcoming release on 850.

Below are the steps that I did:

1. Copied the bin folder for 847 & 850 to my laptop.
2. Cleared all Peopletools entries from registry for both current-user & local machine.
3. Made the necessary settings in 847 config manager (dbname, userid, connect-id,etc) and launched & logged in to app designer 847.
4. Now check the registry to see if the peopletools entry has got created in local user or local machine and extract these settings into a .reg file; in case you see that entries are being
created in both then extract both these entries into separate .reg files.
5. Now again clear the registry (repeat step 2).
6. From the 850 bin folder, make settings in 850 config manager and launch & log in to app designer 850; this will create 850 specific entries in registry.
7. Similar to step 4, extract these 850 entries into .reg files.
8. Clear the registry again (this step may or may not not be needed).
9. Now that you have registry entries that get created for 847 & 850, write 2 batch files to first import the reg file/files for the version (847 or 850) into the registry and then launch the
pside.exe from the bin folder of that particular version.


All settings that are made in the pscfg & pside are stored in the registry, so you can accordingly have the different settings for different versions in the .reg files.
However, please note that you cannot have both settings of 847 & 850 in the registry at the same time. So if you run the batch file for 847 and while the 847 app designer is in use you also launch 850 app designer, the 850 batch file would have overwritten the registry entries for 847. So in case there are some parameters the 847 app-designer accesses from the registry after being launched, they may have been overwritten by the 850 .reg file. Having said that, I often use 847 & 850 pside togther, I am yet to encounter any problems...

-Sudripta

Thanks Sudripta for the reply,

We have been using the App Designer for 846 and 850 at the same time and haven't encountered any issues, but the issue is with the PS/nVision. Only one version is working and other errors out saying "PS/nVision is not configured properly on this workstation".

Let me know if there's any way around for PS/nVision.

Thanks,
Chris

Hi Chris ,
You can try the same approach for nvision as well. Capture the registry entries created on launching nvision - 847 & 850 and then import them into registry just before launching nvision exe using a .bat file.

Let us know if this works.


-Sudripta

Hi Sudripta,

I tried few options like importing registry and re-installing workstation everytime we run the bat file and there's no way we can have two version of nVision open at any time, let say i installed PT 8.46 workstation and opened nVision for that and login to nVision, ran a report.( Keeping this session active), i ran the bat file for installing PT 8.5 workstation, when i try to invoke nVision for PT 8.5, it doesn't open any window.

Registry under HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\PeopleSoft PeopleTools will point to the latest PeopleTools installed on the machine.

The only way is close the previous sessions and open a new one.

Still working to find an alternative way.

Thanks,
Chris

Hi,

Did you find a way to address this issue? I need to have both 8.47 & 8.50 in my machine and need to run PS Queries/nVisions simultaneoulsy on both these versions. Please let me know if anyone has got a way to do it.

Edited by: 846094 on Mar 21, 2011 10:25 AM

Hi chris,

How you are giving your report instance name while configuring your nvision reports in configuration manager you need to give separate instance name for each version and try it.

Regards,
Yarli