Jump to content
C4 Forums | Control4

Composer home edition quits


Recommended Posts

Hi,

I just installed the composer HE but it quits.

Logs this:

Exception: System.ArgumentNullException

Message: Value cannot be null.

Parameter name: buffer

Source: mscorlib

at System.Security.Cryptography.HashAlgorithm.ComputeHash(Byte[] buffer)

at Control4.Client.Controller.PerformChallengeResponse()

at Control4.Client.C4System.ConnectToController(String ipAddress, String filename, String systemPassword)

at Control4.Client.C4System.ConnectToController(String ipAddress, Int32 port, String filename, Boolean useSsl, String systemPassword)

at Control4.Designer.DesignerForm.ConnectToController(String uuid, String ipAddress, Int32 port, String filename, String username, String password, Boolean useSsl)

at Control4.Designer.DesignerForm.ConnectToController(String uuid, String ipAddress, String username, String password)

at Control4.Designer.DesignerForm.ConnectToLocalController()

at Control4.Designer.DesignerForm.ShowStartup()

at Control4.Designer.DesignerForm.ShowStartupOnFirstRun()

at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)

at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)

at System.Threading.ExecutionContext.runTryCode(Object userData)

at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)

at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)

at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

Thanks anyone for help

Link to comment
Share on other sites

  • 3 weeks later...

Are you using a HC1000 for the Director 2.2.2 with the HE2.2.2?

If so, I had a similar (but not exact) logged problem when unsuccessfully trying to open a customer's HE:

Exception: System.Security.Cryptography.CryptographicException

Message: Object identifier (OID) is unknown.

Source: mscorlib

at System.Security.Cryptography.X509Certificates.X509Utils._GetAlgIdFromOid(Stringoid)

at System.Security.Cryptography.X509Certificates.X509Utils.OidToAlgId(Stringoid)

at System.Security.Cryptography.RSACryptoServiceProvider.SignHash(Byte[]rgbHash, String str)

at Control4.Client.Controller.PerformChallengeResponse()

at Control4.Client.C4System.ConnectToController(String ipAddress, String filename, String system Password)

at Control4.Client.C4System.ConnectToController(String ipAddress, Int32 port, String filename, Boolean useSsl, StringsystemPassword)

at Control4.Designer.DesignerForm.ConnectToController(String uuid, String ipAddress, Int32 port, String filename, String username, String password, Boolean useSsl)

at Control4.Designer.DesignerForm.ConnectToController(String uuid, String ipAddress, String username, String password)

at Control4.Designer.DesignerForm.ConnectToLocalController()

at Control4.Designer.DesignerForm.ShowStartup()

at Control4.Designer.DesignerForm.ShowStartupOnFirstRun()

at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntrytme)

at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)

at System.Threading.ExecutionContext.runTryCode(Object userData)

at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCodecode, CleanupCode backoutCode, Object userData)

at System.Threading.ExecutionContext.RunInternal(ExecutionContextexecutionContext, ContextCallback callback, Object state)

at System.Threading.ExecutionContext.Run(ExecutionContextexecutionContext, ContextCallback callback, Object state)

at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntrytme)

at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

ComposerPro worked fine, but HE would always crash.

I am a C4 Tech2 and was able to escalate the problem through tech support to an engineer who remote logged in. After two days and several engineers brainstorming, the diagnosis was a software bug. The fix is in the pipeline with no official ETA.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.