Continue to Site

Welcome to MCAD Central

Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.

Error Code assistance

BWells

New member
Pro/Intralink is giving one of our engineers problems, I was wonder if anyone knows what is going on with the following message. He logs in and after a few minutes it gives you this message. Any help is appreciated.


Pro/Intralink has detected an internal error. Please contact Technical Support for assistance.Tech Support will require a detailed description of the message. Data may also be required. PDMc_QueryCursor_OQL<T>::Initialize

Edited by: BWells
 
My guess is that the local.dbb file is corrupt.


Try to rename the .proi folder on the workstation and then start Intralink. If a new .proi folder structure is created without errors, then the local,dbb was corrupt.
 
Google gave me this hit:


http://ww3.cad.de/foren/ubb/Forum69/HTML/000271.shtml


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_QueryCursor_OQL<T>::Initialize
Argumets:
0: PDMc_QueryCursor_OQL<T>::Initialize
1: \intralink/ilapi/proilbase/inc\cursor.h
2: 390
Error 5:
Message: ToolKit Error : -3114
Argumets:
0: Error while trying to retrieve text for error ORA-03114
Alternate Technique
-----------------
The problems stem from the default stacksize of the Oracle 8.1.7
'tnslsnr.exe' binary.
Increasing that value as documented below resolves the checkout issue.
Increase the stacksize of the binary file 'TNSLSNR.EXE' using the steps
below.
1. Open the DOS command prompt
2. Shutdown the dataserver using 'dbshut_ilink.bat'
3. Change directory to '%ORACLE_HOME%\bin'
4. Change the stacksize using the following command:
orastack TNSLSNR.EXE 1572864
Note that this value is in 1.5Mbytes (1024 x 1024 x 1.5). The default
value
is 1048576 bytes
(i.e. 1024 x 1024).
5. Execute 'dbstart_ilink.bat' after making the change.
Try checking-out the assembly again. If the issue still exists, repeat
steps
2-4 and increase
the stacksize to a higher value, for example, 1835008 (which is 1024 x
1024 x
1.75).
System Admins should increase the stack size in small increments (~.25Mb)
and
retest the
check-out process. Setting the stacksize to an overly large value is not
recommended because
increasing stacksize will increase the address space allocations on the
server.
If this does not resolve the issue and is specific to only Windows 2000
clients please refer to
TPI 120311 for a possible workaround.
Note: With some installations, very large stack sizes (i.e. 4-8Mb) are
necessary.



<tg>
 
BWells, we have a few users that are receiving that same message. We have also seen one that reads "Internal error, please refresh the data or re-start Pro/INTRALINK".I thought our problemwasmore of a corrupt Local.dbb simply because it doesn't happen to everyone and it can't always be recreated onanother machine. However, I deleted the .proi directory, created a new workspace, and got the same error message. Anyhow, I was just wondering if your situation was resolved and what course of action you took so I can try it here.
 

Sponsor

Back
Top