Can't open SolidCP
 
Notifications
Clear all

Can't open SolidCP

12 Posts
3 Users
0 Reactions
3,273 Views
Posts: 1509
Admin
(@trobinson)
Noble Member
Joined: 9 years ago

Hello,

You will loose the settings if you uninstall the Enterprise Server or Standalone server as the settings are held in the database.

Based on your screenshot have you completed the following:

  • Ensure any firewall port to 9001 has been opened
  • Ensured that theoffice.la is in DNS and points to the server
  • Loaded http://theoffice.la:9001 ?

There is no problem with forced https redirect as SolidCP will run fine using HTTPS. You will need to add the required https binding and SSL certificate to IIS for this to work.

Kind Regards,

Trevor Robinson

Reply
Posts: 6
Topic starter
(@docfxit)
Active Member
Joined: 6 years ago

I have the SSL Certificate binding in IIS working with my domain. I just can't get

https://theoffice.la:9001

to work.  When I try that I get:

Secure Connection Failed

An error occurred during a connection to theoffice.la:9001. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG

Thanks,

Docfxit

Reply
Posts: 1995
Admin
(@m-tiggelaar)
Noble Member
Joined: 9 years ago

Can you try and configure it on the default SSL port 443? (it shouldn't matter but on strange issues i prefer to use standards).

Reply
Posts: 6
Topic starter
(@docfxit)
Active Member
Joined: 6 years ago

When I tried https://theoffice.la:443 it brought me to my web page.

In the event viewer I'm getting a number of errors for SolidCP.

Faulting application name: SolidCP.SchedulerService.exe, version: 1.4.1.0, time stamp: 0x5b01eb27
Faulting module name: KERNELBASE.dll, version: 6.1.7601.24236, time stamp: 0x5b74e8e8
Exception code: 0xe0434352
Fault offset: 0x000000000001a06d
Faulting process id: 0xbcc
Faulting application start time: 0x01d4755bc18aecc4
Faulting application path: C:SolidCPEnterprise ServerbinSolidCP.SchedulerService.exe
Faulting module path: C:Windowssystem32KERNELBASE.dll
Report Id: 0d254365-e14f-11e8-ac9b-7020840e520d

Application: SolidCP.SchedulerService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Data.SqlClient.SqlException
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(System.Data.ProviderBase.DbConnectionPoolIdentity, System.Data.SqlClient.SqlConnectionString, System.Data.SqlClient.SqlCredential, System.Object, System.String, System.Security.SecureString, Boolean, System.Data.SqlClient.SqlConnectionString, System.Data.SqlClient.SessionData, System.Data.ProviderBase.DbConnectionPool, System.String, Boolean, System.Data.SqlClient.SqlAuthenticationProviderManager)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(System.Data.Common.DbConnectionOptions, System.Data.Common.DbConnectionPoolKey, System.Object, System.Data.ProviderBase.DbConnectionPool, System.Data.Common.DbConnection, System.Data.Common.DbConnectionOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(System.Data.ProviderBase.DbConnectionPool, System.Data.Common.DbConnection, System.Data.Common.DbConnectionOptions, System.Data.Common.DbConnectionPoolKey, System.Data.Common.DbConnectionOptions)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(System.Data.Common.DbConnection, System.Data.Common.DbConnectionOptions, System.Data.ProviderBase.DbConnectionInternal)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(System.Data.Common.DbConnection, System.Data.Common.DbConnectionOptions, System.Data.ProviderBase.DbConnectionInternal)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(System.Data.Common.DbConnection, UInt32, Boolean, Boolean, System.Data.Common.DbConnectionOptions, System.Data.ProviderBase.DbConnectionInternal ByRef)
at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(System.Data.Common.DbConnection, System.Threading.Tasks.TaskCompletionSource`1<System.Data.ProviderBase.DbConnectionInternal>, System.Data.Common.DbConnectionOptions, System.Data.ProviderBase.DbConnectionInternal ByRef)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(System.Data.Common.DbConnection, System.Threading.Tasks.TaskCompletionSource`1<System.Data.ProviderBase.DbConnectionInternal>, System.Data.Common.DbConnectionOptions, System.Data.ProviderBase.DbConnectionInternal, System.Data.ProviderBase.DbConnectionInternal ByRef)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(System.Data.Common.DbConnection, System.Data.ProviderBase.DbConnectionFactory, System.Threading.Tasks.TaskCompletionSource`1<System.Data.ProviderBase.DbConnectionInternal>, System.Data.Common.DbConnectionOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(System.Threading.Tasks.TaskCompletionSource`1<System.Data.ProviderBase.DbConnectionInternal>)
at System.Data.SqlClient.SqlConnection.TryOpen(System.Threading.Tasks.TaskCompletionSource`1<System.Data.ProviderBase.DbConnectionInternal>)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(System.String, System.Data.CommandType, System.String, System.Data.SqlClient.SqlParameter[])
at SolidCP.EnterpriseServer.Scheduler.RunManualTasks()
at SolidCP.EnterpriseServer.Scheduler.ScheduleTasks()
at SolidCP.SchedulerService.SchedulerService.Process(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()

What else can I do to fix this?

Thanks,

Docfxit

Reply
Posts: 1995
Admin
(@m-tiggelaar)
Noble Member
Joined: 9 years ago

Yes, but can you temporarely change the bindings to test if that works?

As far as the error goes: it indicates the Scheduler in enterprisebin config is most likely not equal to the enterprise web.config sql connection settings and cipher key. it however would not cause SolidCP failing to load. it would only cause scheduled tasks to not function proper.

Reply
Page 2 / 3
Share: