| |
Results |
|
After restarting Tomcat, Work Center gives error "Unable to load initial data for Work Center, please contact your Administrator" and does not load
|
After restarting Tomcat, Work Center gives error " Unable to load initial data for Work Center , please contact your Administrator " and does not load
|
|
|
|
Work Center getting error of "Unable to load initial data for Work Center, please contact your Administrator."
|
Work Center is getting an error of " Unable to load initial data for Work Center , please contact your Administrator " and there is an error in the server.log of "The DELETE statement conflicted with the REFERENCE constraint "FK7B3D669980B2768D". The conflict occurred in database "DatabaseName", table "dbo.SWC_MENUITEM_OVERRIDE", column 'TS_MENUITEMID'."
|
|
|
|
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".
|
|
|
|
Composer error - connection attempt failed. Could not connect to the Repository. Please check that the connection settings are correct. Underlying error: (No compatible tokens found on the request).
|
If you try to open the Work Center interface you might see the following error Unable to load initial data for Work Center , please contact your Administrator . In order to resolve all the above issues is is to just restart the Tomcat/JBoss service depending on your version of SBM while the database is available so it connects correctly then Composer should connect.
|
|
|
|
Users unable to get into Work Center due errors "Unable to validate user" and "Error: Not Found" and "Error static Top : Not Found"
|
6. Enter a new path (for example 'Program Files/Serena/SBM/Common/RelationshipService/ data /new_graph.db') and select 'Start new initial load in this location'. Click 'OK'.
|
|
|
|
Various errors when Tomcat is started while the SBM database is not accessible.
|
Logging into Work Center you may see the following: Unable to load initial data for Work Center , please contact your Administrator . Logging into Application Repository:
|
|
|
|
Work Center Search: Large attachments can cause performance problems
|
This can cause huge performance and stability problems if there are lots of big attachments (hundreds of MBs and more). It gets worse during initial indexing which is multi-threaded and can potentially load several large files at the same time.
|
|
|
|
IMPACT not generating subroutine info for initial history composite components
|
Composite executable components that possess an initial component history (i.e. CMNBAHST-generated) record as the only one that indicates they exist in baseline are being ignored by impact analysis table build processing. Hence no IA table relationships are generated and, in turn, no applicable audit errors (e.g. SYNCH8!s) are being reported.
|
|
|
|
Login screen shows error "Could not load file or assembly 'Serena.SaaSUserDirectory.Mariner "
|
Users will see this error after using the Modify option for Mariner in Add and Remove Programs to add the Report Server component to an existing installation. In other words, the initial install was done using the "Typical" option, which does not include the Report Server component. When the user realizes this, they chose to Modify the install.
|
|
|
|
VM I-Net: Unable to Get/Put files when initial URL to applet contains a project
|
java.lang.UnsatisfiedLinkError: Native Library <Path>\vmi660.dll already loaded in another classloader
|
|
|
