I have changed out the connection string in the data.config file to point to another instance of sql server. I know this connection string works as I tested it from another application, and can login to sql enterprise mgr using the same credentials. Now when i run the app, I cant even load the first page, it bombs on something not in the website, but in one of the external libraries. I have the source code and still can't get to the line blowing up. So what might be going on here?
Exception is below
System.NullReferenceException was unhandled
Message="Object reference not set to an instance of an object."
Source="CommerceBuilder"
StackTrace:
at CommerceBuilder.Utility.ErrorMessage.Save()
at CommerceBuilder.Utility.Logger.a(String A_0, LogMessageType A_1, Exception A_2, Type A_3)
at CommerceBuilder.Utility.Logger.Write(String message, LogMessageType messageType, Exception ex)
at CommerceBuilder.Utility.Logger.Error(String message, Exception ex)
at CommerceBuilder.Utility.MaintenanceWorker.RunMaintenance()
at CommerceBuilder.Services.AbleCommerceHttpModule.a(Boolean A_0)
at CommerceBuilder.Services.AbleCommerceHttpModule.a()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
InnerException:
System.NullReferenceException was unhandled
Message: Object reference not set to an instance of an object.
Object reference not set to an instance of an object?
Object reference not set to an instance of an object?
Steve Portock
Re: Object reference not set to an instance of an object?
Sounds like the db schema is different on your alternate SQL instance. This would result in the permissions not being valid for the connection string and cause the error you are seeing.
Just a theory, but I've definitely seen that error before when the connection string user account doesn't have the right perms to the db in SQL. In my case, it was a schema owner situation.
Just a theory, but I've definitely seen that error before when the connection string user account doesn't have the right perms to the db in SQL. In my case, it was a schema owner situation.
Joe Payne
AbleCommerce Custom Programming and Modules http://www.AbleMods.com/
AbleCommerce Hosting http://www.AbleModsHosting.com/
Precise Fishing and Hunting Time Tables http://www.Solunar.com
AbleCommerce Custom Programming and Modules http://www.AbleMods.com/
AbleCommerce Hosting http://www.AbleModsHosting.com/
Precise Fishing and Hunting Time Tables http://www.Solunar.com