Unsupported encoding CP1252

I've just installed a new server windows 2000 server with TS6.1 SP1.
As I execute a custom workflow, i obtain the following message : "Unsupported encoding: CP1252 at c:/iw-home/iw-perl/site/lib/Teamsite/Uniscape/uniscape.pm line 88, <LIST> line 2. I have two fields to fill that i can't see!!!

..... If someone has any idea....;o(

thanks!

Find more posts tagged with

Comments

Migrateduser

Do you get this on all workflows or just this particular wft? If it's just this one, can you post it, or at least a snippet of it (I would think either the TAG_info or the CGI_info would be the source of the problem).

chrystel

It seems to be on all workflows with fields to fill, i tried one of the \solutions directory and I had another error which is:
Invalid Workflow template:
Can't call method "o_unicoe" without package or objet reference at c:\iw-home\iw-perl\vendor\lib\JavaRessourceBundle.pm line 481, <FH> line 2

I join my custom workflow

Thanks

Adam Stoller

Can you check what the LOCALE is on your server and/or your client machine?
Also what encoding your browser is set to be in on your client machine?
If that doesn't highlight something - then I think you'll have to work with Support (unless someone here has more ideas on the subject)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

chrystel

Hi!
My regional settings of server and client are set to French and the IE encoding UTF-8 ... I installed Teamsite TS6.1 SP1 in french too ?!

Is there something wrong with these parameters ?

Thanks

Adam Stoller

Don't know - check with Support

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

chrystel

Hi!

The perl module I customized were in /iw-home/iw-perl/site/lib, uniscape.pm and map.pm. If I move this customized modules in the /iw-home/iw-perl/vendor/lib it works !!!!!!

......

Adam Stoller

Don't put it in vendor/lib - put it in site/lib - that's where site installed / customized modules belong. vendor/lib, as the name implies, is where vendor-specific (i.e. Interwoven) modules belong and is subject to overwriting with service packs and upgrades

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

Ah, you didn't tell us that you had modified those modules. I thought that you were using the ones included with the product.

Heed ghoti's warning.

If you are having a name conflict with modules you could either use the full path in your "use" statement, or, what would be better since yours are modified, rename them so you don't have to worry about name conflicts. All of our custom modules go in a TWC folder under /iw-hom/iw-perl/site/lib. So when we use them, the syntax is

use TWC::Utils;
use TWC::Workflow;

and so on.