|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
|
|
|
|
Server Error in '/SlxClient' Application. - Invalid column name 'CATEGORIES'. 
Posted: 09 Oct 08 8:22 PM
|
Hi,
I have got a freshly installed SLX 7.5. There are initially no accounts or contacts in the database. Use the New->Account/Contact menu on the web to create a new contact and account. I can view the contact and account in the network client. But when I click on the account in the web account grid to view the account details, I get the following error:
Server Error in '/SlxClient' Application.
--------------------------------------------------------------------------------
Invalid column name 'CATEGORIES'.
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.Data.OleDb.OleDbException: Invalid column name 'CATEGORIES'.
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:
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:
[OleDbException (0x80040e14): Invalid column name 'CATEGORIES'.]
System.Data.OleDb.OleDbCommand.ExecuteCommandTextForSingleResult(tagDBPARAMS dbParams, Object& executeResult) +267
System.Data.OleDb.OleDbCommand.ExecuteCommandText(Object& executeResult) +192
System.Data.OleDb.OleDbCommand.ExecuteCommand(CommandBehavior behavior, Object& executeResult) +48
System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method) +106
System.Data.OleDb.OleDbCommand.ExecuteReader(CommandBehavior behavior) +111
System.Data.OleDb.OleDbCommand.System.Data.IDbCommand.ExecuteReader() +6
NHibernate.Impl.BatcherImpl.ExecuteReader(IDbCommand cmd) +32
NHibernate.Loader.Loader.GetResultSet(IDbCommand st, RowSelection selection, ISessionImplementor session) +182
NHibernate.Loader.Loader.DoQuery(ISessionImplementor session, QueryParameters queryParameters, Boolean returnProxies) +175
NHibernate.Loader.Loader.DoQueryAndInitializeNonLazyCollections(ISessionImplementor session, QueryParameters queryParameters, Boolean returnProxies) +56
NHibernate.Loader.Loader.LoadCollectionBatch(ISessionImplementor session, Object[] ids, IType type) +185
[ADOException: could not initialize a collection batch: [Sage.SalesLogix.Entities.Account.Contacts#System.Object[]][SQL: SELECT contacts0_.ACCOUNTID as ACCOUNTID__1_, contacts0_.CONTACTID as CONTACTID1_, contacts0_.CONTACTID as CONTACTID23_0_, contacts0_.ACCOUNT as ACCOUNT23_0_, contacts0_.ALTERNATEKEYPREFIX as ALTERNAT3_23_0_, contacts0_.ALTERNATEKEYSUFFIX as ALTERNAT4_23_0_, contacts0_.ALUMNI as ALUMNI23_0_, contacts0_.ASSISTANT as ASSISTANT23_0_, contacts0_.BIRTHDAY as BIRTHDAY23_0_, contacts0_.CHILDREN as CHILDREN23_0_, contacts0_.CREATEDATE as CREATEDATE23_0_, contacts0_.CREATEUSER as CREATEUSER23_0_, contacts0_.CUISINEPREF as CUISINE11_23_0_, contacts0_.DEPARTMENT as DEPARTMENT23_0_, contacts0_.DESCRIPTION as DESCRIP13_23_0_, contacts0_.DIRECTIONS as DIRECTIONS23_0_, contacts0_.DONOTEMAIL as DONOTEMAIL23_0_, contacts0_.DONOTFAX as DONOTFAX23_0_, contacts0_.DONOTMAIL as DONOTMAIL23_0_, contacts0_.DONOTPHONE as DONOTPHONE23_0_, contacts0_.DONOTSOLICIT as DONOTSO19_23_0_, contacts0_.EMAIL as EMAIL23_0_, contacts0_.EMAIL3 as EMAIL21_23_0_, contacts0_.FAX as FAX23_0_, contacts0_.FIRSTNAME as FIRSTNAME23_0_, contacts0_.HOMEPHONE as HOMEPHONE23_0_, contacts0_.IMPORTSOURCE as IMPORTS25_23_0_, contacts0_.INITIALS as INITIALS23_0_, contacts0_.INTERESTS as INTERESTS23_0_, contacts0_.ISPRIMARY as ISPRIMARY23_0_, contacts0_.ISSERVICEAUTHORIZED as ISSERVI29_23_0_, contacts0_.LASTHISTORYBY as LASTHIS30_23_0_, contacts0_.LASTHISTORYDATE as LASTHIS31_23_0_, contacts0_.LASTNAME as LASTNAME23_0_, contacts0_.LASTNAME_UC as LASTNAME33_23_0_, contacts0_.LOCATIONCODE as LOCATIO34_23_0_, contacts0_.MIDDLENAME as MIDDLENAME23_0_, contacts0_.MOBILE as MOBILE23_0_, contacts0_.MODIFYDATE as MODIFYDATE23_0_, contacts0_.MODIFYUSER as MODIFYUSER23_0_, contacts0_.OTHERPHONE as OTHERPHONE23_0_, contacts0_.PAGER as PAGER23_0_, contacts0_.PAGERNUMERIC as PAGERNU41_23_0_, contacts0_.PINNUMBER as PINNUMBER23_0_, contacts0_.PREFERRED_CONTACT as PREFERRED43_23_0_, contacts0_.PREFIX as PREFIX23_0_, contacts0_.PREVIOUSEMPLOYER as PREVIOU45_23_0_, contacts0_.REFERRAL as REFERRAL23_0_, contacts0_.REPORTSTO as REPORTSTO23_0_, contacts0_.SALUTATION as SALUTATION23_0_, contacts0_.SCORE as SCORE23_0_, contacts0_.SECONDARYEMAIL as SECONDA50_23_0_, contacts0_.SPOUSE as SPOUSE23_0_, contacts0_.SPOUSEBIRTHDAY as SPOUSEB52_23_0_, contacts0_.STATUS as STATUS23_0_, contacts0_.SUBTYPE as SUBTYPE23_0_, contacts0_.SUFFIX as SUFFIX23_0_, contacts0_.TITLE as TITLE23_0_, contacts0_.TYPE as TYPE23_0_, contacts0_.WEBADDRESS as WEBADDRESS23_0_, contacts0_.WEBADDRESS2 as WEBADDRESS59_23_0_, contacts0_.WEBPASSWORD as WEBPASS60_23_0_, contacts0_.WEBPASSWORDHINT as WEBPASS61_23_0_, contacts0_.WEBUSERNAME as WEBUSER62_23_0_, contacts0_.WEIGHT as WEIGHT23_0_, contacts0_.WORKPHONE as WORKPHONE23_0_, contacts0_.YEARGRADUATED as YEARGRA65_23_0_, contacts0_.MailingCountyCountry as Mailing66_23_0_, contacts0_.FullName as FullName23_0_, contacts0_.NameLF as NameLF23_0_, contacts0_.Name as Name23_0_, contacts0_.Mailingstreet as Mailing70_23_0_, contacts0_.Mailingcitystzip as Mailing71_23_0_, contacts0_.NamePFL as NamePFL23_0_, contacts0_.CATEGORIES as CATEGORIES23_0_, contacts0_.ACCOUNTMANAGERID as ACCOUNT74_23_0_, contacts0_.ADDRESSID as ADDRESSID23_0_, contacts0_.DIVISIONALMANAGERID as DIVISIO76_23_0_, contacts0_.REGIONALMANAGERID as REGIONA77_23_0_, contacts0_.SECCODEID as SECCODEID23_0_, contacts0_.SHIPPINGID as SHIPPINGID23_0_, contacts0_.ACCOUNTID as ACCOUNTID23_0_ FROM CONTACT contacts0_ WHERE contacts0_.ACCOUNTID=?]]
NHibernate.Loader.Loader.LoadCollectionBatch(ISessionImplementor session, Object[] ids, IType type) +279
NHibernate.Loader.Collection.BatchingCollectionInitializer.Initialize(Object id, ISessionImplementor session) +180
NHibernate.Persister.Collection.AbstractCollectionPersister.Initialize(Object key, ISessionImplementor session) +59
NHibernate.Impl.SessionImpl.InitializeCollection(IPersistentCollection collection, Boolean writing) +375
NHibernate.Collection.AbstractPersistentCollection.Initialize(Boolean writing) +111
[LazyInitializationException: Failed to lazily initialize a collection]
NHibernate.Collection.AbstractPersistentCollection.Initialize(Boolean writing) +195
NHibernate.Collection.PersistentSet.get_Count() +11
Sage.Platform.Collections.AbstractEntityCollection`1.get_Count() +12
Sage.Platform.WebPortal.Binding.WebEntityListBindingSource.GetChildByIndex(Int32 index) +126
Sage.Platform.WebPortal.Binding.WebEntityListBindingSource.GetData(Int32 maximumRows, Int32 startRowIndex, Boolean asComponentView) +390
Sage.Platform.WebPortal.Binding.WebEntityListBindingSource.OnCurrentSourceSet() +938
Sage.Platform.WebPortal.Binding.WebEntityBindingSource.SetCurrentSource(Object entity) +49
Sage.Platform.WebPortal.Binding.WebEntityBindingSource.set_SourceObject(Object value) +14
ASP.CopyAccount_PrintView.dsContacts_OnCurrentEntitySet(Object sender, EventArgs e) +49
Sage.Platform.EntityBinding.EntityBindingSource.SetCurrentEntity(Object entity) +214
Sage.Platform.EntityBinding.EntityBindingSource.set_Current(Object value) +4
Sage.Platform.WebPortal.SmartParts.EntityBoundSmartPart.OnLoadCurrentEntity() +81
Sage.Platform.WebPortal.SmartParts.EntityBoundSmartPart.OnLoad(EventArgs e) +98
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210 |
|
|
|
Re: Server Error in '/SlxClient' Application. - Invalid column name 'CATEGORIES'.
Posted: 10 Oct 08 7:47 AM
|
Hi Ashish,
When I upgraded from SLX 7.2.2 to 7.5 I had the same problem. Version 7.2.2 Does not have the field 'CATEGORIES' in the Contact Table... After installing the "SalesLogix v7.2.x to 7.5 Upgrade.sxb" bundle in Workgroup Administrator (which contains the script for adding the CATEGORIES field) it worked.
|
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|