Tag Archives | Error

Test Post 1

How Do I Resolve the Issues with Logging In?

Answer

Please keep in mind when you see the error License expired or invalid login, it could be the number of active users has exceeded or invalid login details.

Operation is Not Valid Due to the Current State of the Object

Resolution

If ever you get an exception of ‘operation is not valid due to the current state of the object’ on a XMPro form, or any asp.net form with a huge number of controls, you need to set/add in the web.config file:

<appSettings>
<add key="aspnet:MaxHttpCollectionKeys" value="1001" />
</appSettings>

Increase the value until the problem goes away.

This is a security update from Microsoft link here.

Error Message: ‘User is Inactive’

Issue

While trying to login to a site with a username called ‘KW3’, the following error message was displayed saying ‘User is inactive’.

Logged into the XMWorkspace as admin to activate the user KW3.

But the Active checkbox for the ‘KW3’ user is disabled and unchecked.

Resolution

The active checkbox will be disabled if the number of users active in the site are greater than or equals to the number of users allowed per the site licence.

A temporary solution is to make an another user inactive, which then allowed you to make ‘KW3’ active by providing the option to enable the active checkbox for KW3 user in XMWorkspace.

Server Error in ‘/XMPro 6.1/XMPro’ Application

Issue

When installing XMPro on IIS 6 Server and trying to access XMWorkspace from the browser, the following error is displayed:

Server Error in ‘/XMPro 6.1/XMPro’ Application.

The WebResource.axd handler must be registered in the configuration to process this request.

<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<httpHandlers>
<add path="WebResource.axd" verb="GET" type="System.Web.Handlers.AssemblyResourceLoader" validate="True" />
</httpHandlers>
</system.web>
</configuration>

Description: An unhandled exception occurred during the execution of the current web request.

Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: The WebResource.axd handler must be registered in the configuration to process this request.

<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<httpHandlers>
<add path="WebResource.axd" verb="GET" type="System.Web.Handlers.AssemblyResourceLoader" validate="True" />
</httpHandlers>
</system.web>
</configuration>

Resolution

In this case, the asp.net version is: 4.0.30319 and the IIS Version is: IIS V6.0

Open the web.config file for this site, the following config information will be displayed:

<httpHandlers>
<add type="DevExpress.Web.ASPxUploadControl.ASPxUploadP rogressHttpHandler, DevExpress.Web.v13.2, Version=13.2.6.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a" verb="GET,POST" path="ASPxUploadProgressHandlerPage.ashx" validate="false" />
<add type="DevExpress.Web.ASPxClasses.ASPxHttpHandlerMo dule, DevExpress.Web.v13.2, Version=13.2.6.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a" verb="GET,POST" path="DX.ashx" validate="false" />
<add type="System.Web.HttpHandlers.AssemblyResourceLoad er" verb="GET" path="WebResource.axd" validate="false" />
</httpHandlers>

The bold highlighted line is the one which causing the issue in this case.

Remove this line from httpHandlers and add it to the handlers tag as shown in below.

<handlers>
<add type="DevExpress.Web.ASPxUploadControl.ASPxUploadP rogressHttpHandler, DevExpress.Web.v13.2, Version=13.2.6.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a" verb="GET,POST" path="ASPxUploadProgressHandlerPage.ashx" name="ASPxUploadProgressHandler" preCondition="integratedMode" />
<add type="DevExpress.Web.ASPxClasses.ASPxHttpHandlerMo dule, DevExpress.Web.v13.2, Version=13.2.6.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a" verb="GET,POST" path="DX.ashx" name="ASPxHttpHandlerModule" preCondition="integratedMode" />
<add type="System.Web.HttpHandlers.AssemblyResourceLoad er" verb="GET" path="WebResource.axd" validate="false" />
</handlers>

After removing the line from httpHandlers tag and adding to handlers tag try to access the workspace and you should be able to login.

Also, now you should be able to login to the designer and create processes / modify, etc., without any issues.

What is the Location of the XMAutomate Error Log?

Question

Our project has been configured so that XMAutomate will monitor a folder path and initiate a process if there is a new file in the folder.

This is working fine until today until a few configuration changes were made in the process and then deployed the process again.

From then onwards, XMAutomate is not invoking the process (or) processing the files.

An attempt to debug and see why XMAutomate is not able to invoke the process even when there are files to be processed.

Where are the error log files or what is the issue?

Answer

In event viewer, custom views ..> Administrative Events, the error log for the XMAutomate was found.

The script in the Process is having an extra ‘}’ as a result the files are not picked and processed by XMAutomate.

The script was modified and everything is working as expected now.

Another item to check when the automated scripts are not behaving is to try and submit the activity manually.

If you cannot submit the activity manually, then the automated services will not be able to.

API Error: The Authentication Header Received was ‘Negotiate,NTLM’

Issue

If you are using XMPro API or any XMPro modules which use API, for example, XMMobile, Business Activity Monitor, etc., and you receive the following error while trying to log in:

The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Negotiate,NTLM'

Resolution

The possible cause for this problem could be that Anonymous authentication is not enabled on services folder of XMWorkspace.

Please enable Anonymous authentication as shown below:

Server Error in ‘/XMPro’ Application Runtime Error

Issue

This normally relates to an environmental issue.

On this occasion, within the browser on submit, the error pointed to the web.config file.

The client had recently switched on error logging in live (within the web.config) for another issue and it was since then that these errors started occurring.

Strangely, it was occurring randomly for a large number of users.

The service account doesn’t seem to have WRITE permissions to the error log file location as within Event Viewer on the application server it was throwing up the message:

"Exception type: InvalidOperationException
Exception message: Cannot open log for source 'XMWorkspace'. You may not have write access."

Resolution

In LIVE, disable logging in the config file and then re-testing a form submission worked.

In the process of testing this further at the moment and seeing if this can be replicated in UAT as the client believes that LIVE and UAT are the same.

Incorrect URL when using the XMAlert Service

Issue

Users are getting a 404 error when clicking the link in the notification e-mail.

The link looks as follows:

http://[siteurl]/myActionItem.aspx?g=0&id=665

(The [siteurl] has been blanked out for the above)

The templates have a [LINK] placeholder which is correctly set.

Resolution

The problem is because the myActionItem has been renamed to ActionItem and the URL is being redirected incorrectly.

To resolve, create a new file in the website folder called myActionItem.aspx and add the following code into it:

<%@ Page Language="C#" Debug="true" %>
<script runat="server">
protected void Page_Load(object sender, EventArgs e)
{
    Response.Redirect("myActionItem.aspx?" + Request.QueryString);
}
</script>

Error with XMDesigner

Issue

Server is Windows 2008 R2

When I open XMDesigner, I receive the following error:

The error details:

System.Runtime.InteropServices.COMException (0x80040154): Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
   at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance(Guid& clsid, Object punkOuter, Int32 context, Guid& iid)
   at System.Windows.Forms.AxHost.CreateWithLicense(String license, Guid clsid)
   at System.Windows.Forms.AxHost.CreateInstanceCore(Guid clsid)
   at System.Windows.Forms.AxHost.CreateInstance()
   at System.Windows.Forms.AxHost.GetOcxCreate()
   at System.Windows.Forms.AxHost.TransitionUpTo(Int32 state)
   at System.Windows.Forms.AxHost.CreateHandle()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.UserControl.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

The error appears to be related to the Toolbox window as if it was set to auto hide in which the error is not received until I expand it.

Resolution

This has been updated and resolved within Service Release v6.0.1.

1 2 3 Next →