stupid question but… where are the logs?
Hello,
I’m getting an inner exception when trying to create a new user.
I’ve seen there are some other threads about this and the solution may be altering the cloudpanel SQL db.
However I’ve searched for 2 hours for the full error details for the inner exception, that each thread reports, and I cannot figure out where they are. Not in the application log, not in the sql errorlog, not in IIS log… what am I missing?
Thank you in advance!
Please post the error and also the error from the log files
Never mind I see you said there was no error. There should be something in the logs they CloudPanel generates.
that’s my question Jacob… where is the CloudPanel log location? I know it’s stupid but cannot find CloudPanel logs (or log path)
It’s in a folder called Logs in the CloudPanel directory
Ok, I was not such an idiot… the Log folder was not created!
I created it manually and assigned Everyone with full control, as I had another permission error before for the web.config file where I had to fix permissions.
I think my installation didn’t go very well… but how to reinstall now from scratch, considering that Exchange (2010 SP3) has already been “touched hard”?
Anyway this is the error, for which I think I can find the solution in a different support thread:
2015-07-31 03:23:38,819 ::: [7] ERROR ::: CloudPanel.Modules.CompanyModules.UsersEditModule — Error updating user c3da0839-58ab-4278-a815-f793e33da1a1 mailbox information: System.Data.Entity.Infrastructure.DbUpdateException: An error occurred while updating the entries. See the inner exception for details. —> System.Data.Entity.Core.UpdateException: An error occurred while updating the entries. See the inner exception for details. —> System.Data.SqlClient.SqlException: Invalid column name ‘TaskType’.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Entity.Infrastructure.Interception.InternalDispatcher1.Dispatch[TTarget,TInterceptionContext,TResult](TTarget target, Func
3 operation, TInterceptionContext interceptionContext, Action3 executing, Action
3 executed)
at System.Data.Entity.Infrastructure.Interception.DbCommandDispatcher.Reader(DbCommand command, DbCommandInterceptionContext interceptionContext)
at System.Data.Entity.Core.Mapping.Update.Internal.DynamicUpdateCommand.Execute(Dictionary2 identifierValues, List
1 generatedValues)
at System.Data.Entity.Core.Mapping.Update.Internal.UpdateTranslator.Update()
— End of inner exception stack trace —
at System.Data.Entity.Core.Mapping.Update.Internal.UpdateTranslator.Update()
at System.Data.Entity.Core.Objects.ObjectContext.ExecuteInTransaction[T](Func`1 func, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction, Boolean releaseConnectionOnSuccess)
at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesToStore(SaveOptions options, IDbExecutionStrategy executionStrategy, Boolean startLocalTransaction)
at System.Data.Entity.SqlServer.DefaultSqlExecutionStrategy.Execute[TResult](Func`1 operation)
at System.Data.Entity.Core.Objects.ObjectContext.SaveChangesInternal(SaveOptions options, Boolean executeInExistingTransaction)
at System.Data.Entity.Internal.InternalContext.SaveChanges()
— End of inner exception stack trace —
at System.Data.Entity.Internal.InternalContext.SaveChanges()
at CloudPanel.Database.EntityFramework.CloudPanelContext.SaveChanges()
at CloudPanel.Modules.CompanyModules.UsersEditModule.<.ctor>b__c4(Object _)
Ahhh yes… This is the fix:
However thats weird it didn’t create the log folder. Which version did you install?
Let me know if what I posted above fixes the issue
Yes it did.
next issue 🙂
Installation of the scheduler with domain admin credentials: cannot start the service: verify you have sufficient privileges to start a service…
I went to services, CloudPanel scheduler service properties, log on tab: I retyped the domain admin password and clicked on Apply. A message popped up saying that the account was given log on as a service right.
Then I “retried” the scheduler installation and it worked this time
It isn’t granting rights to log on as a service which is why the installer can’t start the service after install. When you changed the logon tab it added the user to have rights to log on as a service.
- 5 Forums
- 714 Topics
- 3,630 Posts
- 1 Online
- 254 Members