| |
Results |
|
Unable to load relation 'common' and Common Log won't show anything in Repository when using Oracle db.
|
When accessing the Common Log from the Repository we get an error of: Unable to load relation 'common'. Internal Server Error ( 500 )
|
|
|
|
You can get the following error if you access Event Manager Log in Environments - Error: Application Repository Unable to load relation 'events'.Internal Server Error (500)"java.lang.NullPointerException"
|
You can get the following error if you access Event Manager Log in Environments - Error: Application Repository Unable to load relation 'events'.Internal Server Error (500)"java.lang.NullPointerException"
|
|
|
|
Unable to load relation 'events' Internal Server Error (500)
|
" Unable to load relation 'events'.<br><br>Internal Server Error (500)<br><br>"org.apache.axis2.AxisFault: Read timed out"
|
|
|
|
Promote of pre 10.1.5 snapshot fails in 10.1.5 with error = Unable to load relation.>Internal Server Error (500)
|
Promote of pre 10.1.5 snapshot fails in 10.1.5 with error = Unable to load relation .>Internal Server Error (500)
|
|
|
|
Not able to open Environment->Deploy History - error - Unable to load relation 'history
|
'Unable to load relation 'history'.<br><br>Internal Server Error ( 500 )<br><br>" could not execute query; SQL [SELECT DISTINCT av.ASSETVERSION_ID as ASSETVER1_1_0_, av.VERSION as VERSION1_0_, av.LOCKED as LOCKED1_0_, av.LOCKED_BY as LOCKED4_1_0_, av.LOCK_LABEL_
|
|
|
|
Repository: Process App view gives error "Unable to load relation 'versions'."
|
4) User gets Stack trace: Unable to load relation 'versions'. Internal Server Error ( 500 )
|
|
|
|
VM 8.x on AIX: Error "vm/common/lib/....": Cannot run a file that does not have a valid format. exec(): 0509-036 Cannot load program because of the following errors: 0509-130 Symbol resolution failed for .../vm/common/lib/aix/libpvcsfscli.a
|
or exec(): 0509-036 Cannot load program <CLI> because of the following errors: 0509-130 Symbol resolution failed for .../vm/common/lib/aix/libpvcsfscli.a
|
|
|
|
"Application Repository !Unable to load relation "import". Method not allowed (405) when importing SSM / SRC solutions
|
"Application Repository ! Unable to load relation "import". Method not allowed (405) when importing SSM / SRC solutions
|
|
|
|
Work Center gives error "Unable to load initial data", Repository gives error 500
|
Work center is not accessible after upgraded to SBM11.1 with the message " Unable to load initial data for Work Center, please contact your Administrator". Also, The Application Repository is inaccessible with "Internal Server Error (500)". Running Static Diagnostics test shows all successful, except Notification server and Mail Client Database Connection get "Cannot connect to the Application Engine database or an internal error has occurred".
|
|
|
|
Error 403 or (500) when trying to load Application Repository, or SBM Composer error "No compatible tokens found on the request".
|
Error "( 500 )" on the login page ... Could not connect to the Repository. ... located in "SBM\ Common \Tomcat 7.0\server\default\logs", you may have the following error:
|
|
|
