Error after upgrade from 3.2 to 3.5

[NetAdminNJ]

System.Exception: This page has a MM:DataSet, MM:Insert, MM:Update or MM:Delete tag with a null or empty value for the ConnectionString and DatabaseType attributes.

Often, such values come from application settings in the web.config file. That file might be missing from the server executing this page. Or, it might be missing the particular add key tags for the database connection this page uses. If you are using Dreamweaver, look for the web.config file in the local root folder of your Dreamweaver site. Once you find this file, you can either:
Put this file onto the server that is executing this page.
Copy the add key tags from the web.config in the local root folder of your Dreamweaver site and paste them into the web.config file in the server that is executing this page.

at DreamweaverCtrls.DataSet.DoInit()
--------------------------------------------------------------------------------
System.Exception: This page has a MM:DataSet, MM:Insert, MM:Update or MM:Delete tag with a null or empty value for the ConnectionString and DatabaseType attributes.

Often, such values come from application settings in the web.config file. That file might be missing from the server executing this page. Or, it might be missing the particular add key tags for the database connection this page uses. If you are using Dreamweaver, look for the web.config file in the local root folder of your Dreamweaver site. Once you find this file, you can either:
Put this file onto the server that is executing this page.
Copy the add key tags from the web.config in the local root folder of your Dreamweaver site and paste them into the web.config file in the server that is executing this page.

at DreamweaverCtrls.DataSet.DoInit()

Additionally when I ran lsupgrade.exe and did a connect to the database. Then when i tried to do an execute sql script i got a message (the first time) that the database timed out. Then when i tried it again - not sure if it failed or succeeded - then I got a message saying there already is a table in place called sysconfig or something. Can you please tell me what i did wrong ? And how can i be sure that the upgrade to 3.5 has gone through cleanly.

[NetAdminNJ]

That solved it. Thank you very much. I very much like the ability to integrate the cross-forest information into one view/database.

I am not aware of what limitations exist in my environment that prevent cross-domain management using ACTIVE Directory tools but I am wondering if you are using standard WMI connectivity to get the cross domain information ? Again I want to make sure that I am able to answer questions that my infosec team will present to me. Any insight will help greatly.

[Hemoco]

NetAdminNJ wrote:
That solved it. Thank you very much. I very much like the ability to integrate the cross-forest information into one view/database.

I am not aware of what limitations exist in my environment that prevent cross-domain management using ACTIVE Directory tools but I am wondering if you are using standard WMI connectivity to get the cross domain information ? Again I want to make sure that I am able to answer questions that my infosec team will present to me. Any insight will help greatly.

Info from active directory is gathered by ldap queries, information from computers is gathered from WMI (all read only)

[NetAdminNJ]

Thanks Geert. The upgrade helped solve the error. I copied the web.config file back but now I am getting this error

Column 'nonactive' does not belong to table theTable.
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.ArgumentException: Column 'nonactive' does not belong to table theTable.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

<%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:


[ArgumentException: Column 'nonactive' does not belong to table theTable.]
System.Data.DataRow.GetDataColumn(String columnName) +1899263
System.Data.DataRow.get_Item(String columnName) +10
ASP.state_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer) +1202
System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +2065835
System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +24
System.Web.UI.Page.Render(HtmlTextWriter writer) +26
System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +25
System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +121
System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +22
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1896




--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

[Hemoco]

NetAdminNJ wrote:
Column 'nonactive' does not belong to table theTable.

Use lsupgrade.exe, first run the 3.2 to 3.5 sql script, then run the 3.5.1 script (you probably forgot the first script)

[Hemoco]

1) Please download 3.5.1 beta from http://www.lansweeper.com/forum/yaf_postst1514_Lansweeper-Service-351-update-1-beta.aspx
And run the upgrade script again with the included lsupgrade.exe (this version sovles the timeout issues) (ignore any errors you might get)

2) Upgrade to the 3.5.1 beta version, this version allows you to scan untrusted domains using alternate credentials.


3) is it possible that you deleted the web.config file during the upgrade? this file contains your database connection information.

[NetAdminNJ]

One more question. I have couple of forests that donot have a trust relationship to the domain where I am running Lansweeper. Can I find out how/why the discovery of other domains is getting limited at ?

I added 2 domains but i am only seeing information back from 1 domain.

Is there any explanation of how the information is relayed back to the SQL Server if there is no trust relationship ? (Not trying to pry into product secrets but wanting to prepare with this information when my InfoSec team comes to question me about this product)