[rlukes]

Hello. First time post for me.

We recently upgraded from OTM 5.0 to OTM 5.5 and have both versions running on separate servers. We have always used the python upload method to load freight rates into OTM using ClientUtil.py which worked well in OTM 5.0. However, when we try running the same scripts on the OTM 5.5 server we get the following error:

Traceback (most recent call last):
File "/appsoft/otm55/utils/integration/python/ClientUtil.py", line 640, in ?
args.argValue("localDir"),args.argValue("localFile Name"),args.argValue("csvUtilCommand"),args.argVal ue("xvalidate"))
File "/appsoft/otm55/utils/integration/python/ClientUtil.py", line 363, in csvImport
encoding=commonTools.getCharacterEncoding()
File "/appsoft/otm55/utils/integration/python/commonTools.py", line 740, in getCharacterEncoding
return site.encoding
AttributeError: 'module' object has no attribute 'encoding'

Since we didn't change any code, I suspect that this is due to an installation or configuration issue with Python. Unfortunately, my python skills are minimal.

Any ideas or suggestions on what is happening and how I can get our python rate loads working again?

Help is greatly appreciated.

Thank you!
--Richard

[rlukes]

I found the answer on MetaLink:
Cause

The cause is that there is a difference in the python versions used and one has a change in one of the modules. Current python code reference as used by OTM needs to be updated to reflect the change.

This is explained in the following bug:
Bug.<7647979> RECEIVE AN ERROR WHEN RUNNING CLIENTUTIL.PY


Solution

-- To implement the solution, please execute the following steps:
1. Download and review the readme and pre-requisites for 5.5 CU5 RU3 when made available, currently scheduled for release at the end of Jan 2009.

2. Ensure that you have taken a backup of your system before applying Version 5.5 CU5 RU3

3. Apply Version 5.5 CU5 RU3 in a test environment.

4. Retest the issue.

5. Migrate the solution as appropriate to other environments.

[chrisplough]

Thanks for the update. If you test 5.5 CU5 RU03 and it works, please post back. This is a big deal to a lot of OTM users out there.

--Chris

[rlukes]

Sorry for not replying sooner... Bug No. 7647979 now includes details on the exact line(s) in commonTools.py which need to be updated. We made this change and deferred applying the roll-up until later. Our problem is resolved now.