You are viewing an old version of this content. View the current version.
Compare with Current
View Version History
« Previous
Version 3
Next »
Errors can occur while using Workplace management, in some cases due to incorrect use of the intended function and in other cases due to certain limitations or other boundaries, As an administrator, it is important to be aware of some of the most common error messages user can experience, to be able to help the users better.
Errors that are the result of system limitation, are already described in System boundaries and limits: max. file size, export restrictions, timeouts, etc and are not discussed in this article.
Error messages
Most error messages describe clearly what the issue is. The errors mentioned in this article are a small selection of errors that might require additional explanation.
System error
If an error occurs and no specific error message is defined, Workplace will show a generic: 'A system error has occurred’ message. Please retry what you were doing. If the error still occurs, check the possible causes below. If you are not able to resolve the issue, please contact Spacewell Support.
Error message | Possible causes |
---|
A system error has occurred … [timestamp] | When this happens after a fixed time (e.g. after 1 or 10 minutes) after pressing a button or viewing a page, it’s most likely a timeout because a script or process took to long. Look at the time-out error section of this article for more information Invalid URL (e.g. missing a '/') Bad internet connection When using an embed page, this error occurs when a user clicks a button twice. In this case a new request is send to the server whilst the first request is still being processed. In all other cases something unexpected went wrong for which the Axxerion code does not have a specific error message. Ask Workplace Support for help.
|
File conversion error
’File conversion is done, directly after uploading the document, by report servers/converter engines. Common errors when uploading a document are shown in the table below.
Error message | Possible causes |
---|
No suitable converted found | An obscure file format is uploaded that cannot be converted. The extension does not match the real file format (or example the extension of a .exe was changed to .pptx) A file might contain, not support extras, like Word or Excel macro.
|
Conversion: Time out | |
An issue might also occur directly upon opening a document.
Error message | Possible causes |
---|
No document attached to object | No document version is set. The document version is set automatically if the field 'document.autoPublish= yes'. If this is set to 'no', the current version must be set via a workflow. For example, via the 'Publish' function. To fix this check the document settings and set the version manually if needed.
|
Time out error
Time out errors are often a result of system boundaries/ limits. For more information on time out errors as a result of boundaries/ limits, take a look at this article: System boundaries and limits: max. file size, export restrictions, timeouts, etc.
Error message | Possible causes |
---|
Read time out (on a ftp import or export connector) | Retrieving the file from the FTP server timed out. The so-called 'socket timeout' is the duration within which the client expects a response from the server while retrieving a file, i.e. data is coming in. The error occurs in an external library that uses the Workplace code. We therefore do not receive any more information. The most likely cause is that the connection between Workplace and the host server was temporarily lost.
|
Page loading error
It can happen that a page you want to open keeps loading. If this happens, try again. If this does not solve the issue, take a look at the possible causes in the table below.
What happens? | Possible causes |
---|
A specific include or the whole dashBoard/ startBoard keeps loading | |
Environment/ startBoard continues to load after user logs in or after you switch after this user | |
Login related error (including SSO)
An error can occur the moment a user tries to log in.
Error message | What does it mean? |
---|
You cannot log in because no user groups are active | |
Access denied | |
Your request had been blocked for security reasons | Client tries to login in with a second sessions whilst multi-session login is not allowed. Try closing the browser completely and login again. IP whitelisting is enabled (Settings > ‘Authentication’ tab) and the users IP is not on the whitelist.
|
Logging in with SSO failed | User is not active (active = no) Password of the user is expired User does not have user groups linked to the active contact
|
Unable to validate SAML message | SAML username of the user does not match the SAML username in the client SSO application. Make sure the two match META data has to be updated on Workplace of client side SSO certificate has expired.
|
Workflow related error
After pressing a workflow button an error can occur. A few blocking error messages are shown in the table below. We do not discus intentional warning messages or confirmation messages (this is always a popup).
Error message | Possible causes |
---|
No users can be found to assign to the workflow task: task name - object reference - title  | Note: the error clearly states which task it concerns. |
You do not have enough rights to delete: task name - object reference - title | |
Other issues
What happens? | What does it mean? |
---|
Uploaded photo’s are shown at a 90 degree angle (e.g. portrait instead of landscape) | The camera's original orientation (portrait of landscape) is used to determine rotation after upload. Rotating the photo using a simple Windows photo viewer has no affects as this does not actually change the images’ orientation. |