Skip to content

DataSplice Support Website

Sections
Personal tools
You are here: Home » Support Forums » DataSplice Forum » MAXIMO Plug-in Errors (2)

 sad MAXIMO Plug-in Errors (2)

Replies: 1   Views: 4133
Up one level
You need to be a registered member to post to this forum. Register now.

 
Member
Posts: 0

sad MAXIMO Plug-in Errors (2)

Posted by gpitner at 2005-01-14 04:36 AM

Our installation and configuration appears to have all gone well and without error or exception.

While trying to use the Remote Client, the following two errors were received. The first error was when trying to save a new work order insert. The second error was while trying to save an update to an existing work order.


---------------------------------------------------------

Fri Jan 14 14:13:41.975 - Thread 0x38f1e8 - Level ffffffff
thread id: 0 status: Inserting record user: MAXIMO::HELMM socket: 10.0.2.15 (1042)
CaughtException: Method setAutoKeyFlag in type psdi.app.workorder.WOSet_Stub from assembly transientProxies, Version=0.0.0.0 does not have an implementation.:
View Name: Workorder Tracking
0: HandlerName: WorkorderModule.CreateNewWorkorder

---------------------------------------------------------

Fri Jan 14 14:16:35.956 - Thread 0x38f1e8 - Level ffffffff
thread id: 0 status: Updating record user: MAXIMO::HELMM socket: 10.0.2.15 (1042)
CaughtException: The invoked member is not supported in a dynamic module.:
View Name: Workorder Tracking
0: HandlerName: WorkorderModule.UpdateWorkorder

---------------------------------------------------------

Also,

We are currently at Maximo 5.2 Patch 2A. The Maximo Plugin installation only went as high as Maximo 5.2 Patch 2. Could this be a possible cause of these errors?

Thank You!

Greg Pitner

 
Manager
kunzem
Posts: 0

 • Re: MAXIMO Plug-in Errors (2)

Posted by kunzem at 2005-01-14 10:00 AM

gpitner wrote:

We are currently at Maximo 5.2 Patch 2A. The Maximo Plugin installation only went as high as Maximo 5.2 Patch 2. Could this be a possible cause of these errors?


It's a pretty good bet that is the problem. They seem to have a lot of API changes with their patches, which break the proxies we have bound to them.

We'll need to get you an updated proxy and see if that fixes the problem.

 

 

Powered by Plone

This site conforms to the following standards: