FW: RecordComms file

Subject 

FW: RecordComms file 

From 

Roger Davis 

To 

Jeff Mack 

Sent 

Thursday, July 19, 2018 4:02 PM 

Attachments 


Hey, 

The RecordComms.dll file is in the attached zip.  

I copy/pasted the relevent portions of the error emails, and highlighted the interesting bits.  That second exception, TypeInitializationException, is almost always due to a missing/bad file.


From: Roger Davis  

Sent: Thursday, July 19, 2018 3:39 PM 

To: Carolyn J. Johnson <CarolynJ@PERENNIALSOFTWARE.COM> 

Subject: RecordComms file 

The attached is a zip file.  Putting the file within (RecordComms.dll) in the SO install directory should fix the issue in the error message below. 

(Whoever you have do this should look for an existing copy of this file.  If one exists, they should change the extension to .bak (or whatever) before copying the new one.) 

Note that it is possible that another DLL upon which “RecordComms” is dependent is missing.  In that case, this solution will not work.

Source: SedonaSchedule 5.7.92.12356 (Changeset 12356) 

DateTime: 07/19/2018 @ 11:24:40 AM 

Machine Name: TS-2 

User Domain \ User Name: GSSI\kmiller 

User Display Name: Kirk Miller 

User Email Address:  

OS Version: Microsoft Windows NT 6.1.7601 Service Pack 1 64bit OS: True .Net Version: 4.0.30319.42000 AppData Path: d:\Users\kmiller\AppData\Roaming External IP: N/A Internal IP: fe80::7c6c:26c4:382a:bece%14, 192.168.10.24 Executing Dir: C:\Program Files (x86)\Perennial Software\Sedona Office 

Additional Data: 

ATTN: This error crashed SedonaSchedule. 

Unhandled AppDomain Non-UI Exception 

Master Server Name: GSSI-ANC-SQL01 

Data Server Name: GSSI-ANC-SQL01 

Data Database Name: Guardian_Final 

Document Server Name: GSSI-ANC-SQL01 

Sedona Company: Guardian Security Systems, Inc (15) Sedona User: Kirk (4) 

System.BadImageFormatException: Could not load file or assembly 'RecordComms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=151ae431f239ddf0' or one of its dependencies. The module was expected to contain an assembly manifest. 

File name: 'RecordComms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=151ae431f239ddf0' 

   at BoldTechnologies.ServerInterface.clsServerInterface.Dispose(Boolean disposing) 

   at BoldTechnologies.ServerInterface.clsServerInterface.Finalize() 

Source: SedonaSchedule 5.7.92.12356 (Changeset 12356) 

DateTime: 07/19/2018 @ 11:24:40 AM 

Machine Name: TS-2 

User Domain \ User Name: GSSI\kmiller 

User Display Name: Kirk Miller 

User Email Address:  

OS Version: Microsoft Windows NT 6.1.7601 Service Pack 1 64bit OS: True .Net Version: 4.0.30319.42000 AppData Path: d:\Users\kmiller\AppData\Roaming External IP: N/A Internal IP: fe80::7c6c:26c4:382a:bece%14, 192.168.10.24 Executing Dir: C:\Program Files (x86)\Perennial Software\Sedona Office 

Additional Data: 

Reason: Error writing to Manitou service log. 

Master Server Name: GSSI-ANC-SQL01 

Data Server Name: GSSI-ANC-SQL01 

Data Database Name: Guardian_Final 

Document Server Name: GSSI-ANC-SQL01 

Sedona Company: Guardian Security Systems, Inc (15) Sedona User: Kirk (4) 

Exception Data: 

ticketNumber: 1728 

status: Closing 

Serial Number: 7762 

System.TypeInitializationException: The type initializer for 'modGlobals' threw an exception. ---> System.BadImageFormatException: Could not load file or assembly 'RecordComms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=151ae431f239ddf0' or one of its dependencies. The module was expected to contain an assembly manifest. 

   at BoldTechnologies.ServerInterface.clsServerInterface..ctor() 

Was this article helpful?
Thank you for your feedback!
User Icon

Thank you! Your comment has been submitted for approval.