Error messages everywhere

[goocy]

What is wrong with my version?
I freshly converted my big partition to NTFS, just to run tag2find.

What happens:
- Windows starts
- tag2find appears in tray
- floatbar appears
- I close the floatbar -> error message (An internal error occured. This instance will now shut down.)
- I rightclick on the tray icon -> error (with additional message "Attempted to write to protected memory")
- tag2find shuts down

- restarting tag2find (Manage Tags)
- Both floatbox and tray icon reappear
- I close the floatbar -> error message
- I rightclick on the tray icon -> popup menu, I choose "New Tag Browser"
- tag browser opens, moans that service isn't running
- I start the service

- tag2find finally runs!
- Options -> any changed setting -> Apply: error

If I fill out the feedback form, it gives me a connection timeout. This does also happen with disabled firewall.
This sucks!

[martin]

Hi,

I am very sorry for your inconvenience. It appears that one of the native DLLs is corrupted, because writing to protected memory should not happen in the .NET part of the software. The only reason I can think of is that maybe the installer got corrupted, please uninstall tag2find and download the installer once again.

If the problem still persists, please write me an e-mail at contact@tag2find.com and I'll look into it as soon as I am in the office tomorrow (today is a holiday in Austria). If you really cannot submit an error, please also let me know. You could copy/paste the information from the details of the error-report either here or more preferred in an e-mail to me.

Once again, sorry. I'll do my best to help you resolve the issue.

Best regards,
Martin

[goocy]

Ah, now I remember why I didn't try copy & paste earlier - the feedback mechanism crashes my entire IP-stack
2 hours ago the explorer crashed additionally, and system wasn't stabilizing anymore at all (I waited 20 minutes, just to make sure)
Ok, this would actually be funny if my machine wouldn't need 15 minutes after each reboot to set up its webserver again..
Re-installation didn't change anything - besides I now don't have tag2find in my autostart any more.

I really am willing to help you fix this problem - shouldn't be a big flaw to handle, and I cannot imagine I'm the only one with this problem.

This one is reproducable: Start tag2find, Options, change one arbitrary item, click apply -> error
If this is anyhow useful for you, the complete error message is following:

Code:

System.ArgumentException: The binary form of an ACE object is invalid.
Parameter name: binaryForm
   at System.Security.AccessControl.GenericAce.CreateFromBinaryForm(Byte[] binaryForm, Int32 offset)
   at System.Security.AccessControl.RawAcl.SetBinaryForm(Byte[] binaryForm, Int32 offset)
   at System.Security.AccessControl.RawSecurityDescriptor..ctor(Byte[] binaryForm, Int32 offset)
   at System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
   at System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
   at System.Security.AccessControl.FileSystemSecurity..ctor(Boolean isContainer, String name, AccessControlSections includeSections, Boolean isDirectory)
   at System.Security.AccessControl.FileSecurity..ctor(String fileName, AccessControlSections includeSections)
   at System.Configuration.Internal.WriteFileContext.DuplicateTemplateAttributes(String source, String destination)
   at System.Configuration.Internal.WriteFileContext.DuplicateFileAttributes(String source, String destination)
   at System.Configuration.Internal.WriteFileContext.Complete(String filename, Boolean success)
   at System.Configuration.Internal.InternalConfigHost.StaticWriteCompleted(String streamName, Boolean success, Object writeContext, Boolean assertPermissions)
   at System.Configuration.Internal.InternalConfigHost.System.Configuration.Internal.IInternalConfigHost.WriteCompleted(String streamName, Boolean success, Object writeContext, Boolean assertPermissions)
   at System.Configuration.Internal.DelegatingConfigHost.WriteCompleted(String streamName, Boolean success, Object writeContext, Boolean assertPermissions)
   at System.Configuration.ClientSettingsStore.ClientSettingsConfigurationHost.WriteCompleted(String streamName, Boolean success, Object writeContext)
   at System.Configuration.UpdateConfigHost.WriteCompleted(String streamName, Boolean success, Object writeContext)
   at System.Configuration.MgmtConfigurationRecord.SaveAs(String filename, ConfigurationSaveMode saveMode, Boolean forceUpdateAll)
   at System.Configuration.Configuration.SaveAsImpl(String filename, ConfigurationSaveMode saveMode, Boolean forceSaveAll)
   at System.Configuration.Configuration.Save()
   at System.Configuration.ClientSettingsStore.WriteSettings(String sectionName, Boolean isRoaming, IDictionary newSettings)
   at System.Configuration.LocalFileSettingsProvider.SetPropertyValues(SettingsContext context, SettingsPropertyValueCollection values)
   at System.Configuration.SettingsBase.SaveCore()
   at System.Configuration.SettingsBase.Save()
   at System.Configuration.ApplicationSettingsBase.Save()
   at Com.Tag2Find.Desktop.T2FOptionsManager.OptionsManager.SecureSaveSettings()
   at Com.Tag2Find.Desktop.T2FOptionsManager.OptionsManager.set_ShowFloatingTagTextBox(Boolean value)
   at aar.l(Object A_0, EventArgs A_1)
   at System.Windows.Forms.ToolStripMenuItem.OnCheckStateChanged(EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.set_CheckState(CheckState value)
   at System.Windows.Forms.ToolStripMenuItem.set_Checked(Boolean value)
   at aar.ab()
   at aar.a(Object A_0, MouseEventArgs A_1)
   at System.Windows.Forms.NotifyIcon.OnMouseDown(MouseEventArgs e)
   at System.Windows.Forms.NotifyIcon.WmMouseDown(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.NotifyIcon.WndProc(Message& msg)
   at System.Windows.Forms.NotifyIcon.NotifyIconNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[martin]

Hmm,

this is rather strange (even more strange would be a .NET application crashing your entire IP stack). Do you have the latest patches for the .NET Framework applied (will automatically install via Windows Update if enabled)?

Regarding the stacktrace you posted, it seems that either the settings file or the settings API inside the .NET framework are corrupted. I "hope" its the first one, because I am not aware of any issues in the .NET framework itself.

Please try the following:

• Open "C:\Documents and Settings\<yourusername>\Local Settings\Application Data\tag2find" (please note that both Local Settings and Appliation Data are hidden by default, you'll have to enable showing hidden files/folders in Explorer first)
• Delete all tag2find.exe_* and tag2find_common directories

This will reset all your options to default. Based on the stacktrace you posted, it should work then. If not, the only other thing I can imagine is to uninstall and re-install the Microsoft .NET Framework 2, which can be downloaded at http://www.microsoft.com/downloads/details.aspx?FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5 (http://www.microsoft.com/downloads/details.aspx?FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5).

I really hope this helps you resolve the issue. Please post again for any further questions!

Best regard,
Martin

[goocy]

Hi,

Deleting the settings didn't change anything at all, but your tip with .net Service Updates lead to success.
Oddly enough, it seems that KB898461 is neccesary - and since then I don't have any IP problems any more. (Yes I know this is a Windows Installer Package)
Thus, I think you can't probably patch your source code. But if the problem occurs again, you'll know what to advice

Thankful greetings,
Herbert Falk

[martin]

Hi,

thank you for your debugging efforts and for your suggestion. I have added the KB article to our knowledge database in order to be able to help others once requested. It is really rather strange that this special KB is required and causing this issue.

Once again, thanks for sharing the information and for not giving up on the initial problems!

Best regards,
Martin