Skip to main content
P
PATRICKMCDERMOT1-Visitor
1-Visitor
July 23, 2014
Question

Pro/Intralink 3.4 has detected an internal error. Anyone help?

  • July 23, 2014
  • 3 replies
  • 2867 views

PDMc_DataCursor::Open() failed

3 replies

C
ClintWalton1-Visitor
1-Visitor
July 28, 2014

Patrick,

I've moved this thread to the Windchill Community.

C
ChrisSpartz13-Aquamarine
13-Aquamarine
July 28, 2014

When you get that message, are there any errors written to either the Method Server log or the .proi.log?

P
PATRICKMCDERMOT1-VisitorAuthor
1-Visitor
July 29, 2014

Error Stack:

Error 0:

Message: Pro/INTRALINK has detected an internal error.

Please contact Technical Support for assistance.

Technical Support will require a detailed description of the

actions preceeding this message. Data may also be required.

PDMc_DataCursor::Open() failed

Arguments:

0: PDMc_DataCursor::Open() failed

1: \intralink/ilapi/proilbase/pdmbase/gdatadic.cxx

2: 102

Error 1:

Message: This error message has internal usage only.

It should be never put into stack.

Please check the online knowledge database at www.ptc.com

and/or contact Technical Support,

Arguments:

Error 2:

Message: This error message has internal usage only.

It should be never put into stack.

Please check the online knowledge database at www.ptc.com

and/or contact Technical Support,

Arguments:

Error 3:

Message: This error message has internal usage only.

It should be never put into stack.

Please check the online knowledge database at www.ptc.com

and/or contact Technical Support,

Arguments:

Error 4:

Message: ToolKit Error : -3114

Arguments:

0: Error while trying to retrieve text for error ORA-03114

L
LoriSood23-Emerald I
23-Emerald I
July 30, 2014

Is this occurring for all clients or just certain ones? ORA-03114 typically means that the client can't make a connection with Oracle. I would make sure that Oracle/dataserver is up and running and that there aren't any impediments with connecting to it via the client (i.e. firewall/network issues, or sqlnet.ora configuration settings on the client).

P
PATRICKMCDERMOT1-VisitorAuthor
1-Visitor
July 31, 2014

This is only an issue on computers that are on a seperate network from the license server. The license server is across a VPN connection. It has always been but we had a provider change and the VPN was redone. The VPN is wide open (all traffic allowed) and there are no firewalls turned on in between (client and server firewalls are off). Ports are open and responding normally from the client testing across the VPN to the license server. sqlnet.ora file on the client is nearly empty with no configuration parameters.

L
LoriSood23-Emerald I
23-Emerald I
July 31, 2014

Have you ensured that there are no DNS or LDAP connectivity issues when connected via the VPN?

Are you able to perform a tnsping? <PROI_CLIENT>/bin/tnsping <hostname>

Any change if you set sqlnet.expire_time = 0 in the sqlnet.ora file and CONNECT_TIMEOUT_LISTENER = 0 at the end of listener.ora file.

If that still fails, is there any change if you set SQLNET.AUTHENTICATION_SERVICES= (NONE) in the sqlnet.ora?

Terms & ConditionsCookie settingsAccessibility statement