3

153 ●6 ●8 ●20

Hi, I try to run this script

import sys, os
sys.path.insert(0, r"C:\Program Files\PTI\PSSE33\PSSBIN")  # xx --> substitute xx with Version Number here.
os.environ['PATH'] = r"C:\Program Files\PTI\PSSE33\PSSBIN" + ";" + os.environ['PATH']
import redirect
redirect.psse2py()  # this redirects PSS(R)E progress, report output to Python Shell/Console
import psspy

CASE = r"H:\PortableAppscom\Documents\PSSE group\PSSPY\EMT_CAMax_SEP_12_Exp_PA_SN.sav"

psspy.psseinit(12000)
psspy.case(CASE)

But I got a pop up

"Bad version number 33 for program PSSE Was expecting 32"

I have installed both version.

Can you help me to find the problem?

Thanks, Waltter

edit retag flag offensive close merge delete

Comments

@chip have you seen this error before?

JervisW ( 2012-07-16 17:33:09 -0600 )edit

1

I've seen this trying to get my environment setup. Try *env > debug_env.txt* and search through the text file for an errant v32 reference. Remove the v32 references from your environment until your script starts working.

chip ( 2012-07-16 20:44:43 -0600 )edit

I think this is because I installed the version 32 after the 33. Itried this script on another PC where I installer 32 before 33 and there is no problem. I'm going to reinstall the version 33

waltterval ( 2012-07-16 23:57:59 -0600 )edit

I think this is because I installed the version 32 after the 33. Itried this script on another PC where I installer 32 before 33 and there is no problem.

waltterval ( 2012-07-16 23:58:01 -0600 )edit

Well the error was fixed. I reinstalled the PSSE33, and now all is ok.

waltterval ( 2012-07-20 09:48:06 -0600 )edit

see more comments

1

answered 2012-11-07 17:47:20 -0600

Enrique
71 ●2 ●2

I had a similar experience and asked PTI support for help (before actually seeing the fix here, which was really helpful - thanks Waltter - since it got me going again until PTI got to the bottom of the problem).

Apparently PSSPY does some 'housekeeping' whenever it is imported. Part of this requires WRITE access to HKEY_LOCAL _MACHINE\SOFTWARE\PTI\License. Once my IT department granted WRITE access to this registry key I was able to uninstall\reinstall PSSE32 (getting back to the state where PSSE32 was installed after PSSE33) and no longer get the Bad Version Number error when following the above procedure of calling psspy.psseinit from outside PSSE.

Regards, Enrique

edit flag offensive delete link

Comments

Thanks Enrique. I think the IT write permissions will be a stumbling block for many companies. Glad to have it documented for next time.

JervisW ( 2012-11-07 18:42:42 -0600 )edit

add a comment

1

answered 2012-07-20 10:46:04 -0600

waltterval

153 ●6 ●8 ●20

I fixed the error, the problem was that I intalled PSSE32 after PSEE33, so, I don't know why, mi PC always was looking PSSE32 as the default version. I reinstalled PSSE33 and I can run my script with no problem, even if I want to use PSSE32.

Regards, Waltter

edit flag offensive delete link

Comments

nice one. Happy to see it fixed. So the answer is to install PSSE32 first and then PSSE33, not the other way around

JervisW ( 2012-07-20 16:32:28 -0600 )edit

add a comment

Bad Version number

Comments

2 answers

Comments

Comments

Your Answer

Question Tools

Stats

Related questions