WorkSite Web 8.1

Hi,
I am getting " Cannot import a null node” Err when logging-in with any user even admin to 8.1 WSW.
Checked permission in the DB and followed the Tech note on NTFS permissions.

Any thoughts?

Find more posts tagged with

Comments

dabird

The error that you have provided is the "friendly error", which is not meant to provide detailed information. In order for us to help pinpoint the problem, we will need you to post the call stack. Getting the call stack is actually very easy. All you need is to make a change to your web.config file.

1. On the physical WorkSite Web server, navigate to <WSW install directory>.
2. At the root level you will see a file named "web.config".
3. If you have an xml editor, open with that (easier to read). Otherwise, open it with Notepad.
4. Search the file for "customErrors". The value is probably "On".
5. Change the setting to "Off" (this is case-sensitive).
6. Save the file. NOTE: You do not have to restart IIS.
7. Try your login again with an admin account first. This time you're going to get an ugly HTML page with the entire call stack.
8. Copy the call stack data and post it back to this topic. We'll be able to help you from there.
9. After you've copied the call stack message, you should probably set customErrors back to "On" because you don't want your users to get such ugly messages.

Migrateduser

Cannot import a null node.
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: Cannot import a null node.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[InvalidOperationException: Cannot import a null node.]
System.Xml.XmlDocument.ImportNodeInternal(XmlNode node, Boolean deep) +669
System.Xml.XmlDocument.ImportNode(XmlNode node, Boolean deep) +10
iManage.WorkSite.Web.ResourcePageUpdater.updateViewsInResourcePage(XmlDocument existingResourcePage, XmlDocument newResourcePage)
iManage.WorkSite.Web.ResourcePageUpdater.UpdateResourcePage(XmlDocument existingResourcePage, XmlDocument newResourcePage)
iManage.WorkSite.Web.Resources.update(SessionContext sessionContext, IManWorkspace workspace)
iManage.WorkSite.Web.Resources.load()
iManage.WorkSite.Web.Resources.get_objectID()
iManage.WorkSite.Web.Serialization.ViewSerializer..ctor(String name, String href, Boolean hasMaxRows)
iManage.WorkSite.Web.Serialization.SerializerFactory.get_Workspace()
iManage.WorkSite.Web.Serialization.SerializerFactory.GetSerializer(imObjectType objectType, Boolean isMailFolder)
iManage.WorkSite.Web.UI.BasePage.get_ViewsSerializer()
iManage.WorkSite.Web.UI.Portal.buildHeader()
iManage.WorkSite.Web.UI.PortalHandler.ProcessRequest()
iManage.WorkSite.Web.UI.HttpHandler.ProcessRequest(HttpContext context)
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +179
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87

dabird

It looks like the resource page is missing some data. At this point I can only recommend that you contact Tech Support so that your issue can be formally tracked. When you contact Tech Support, supply them with the call stack information, as this will help them tremendously.