Archive To Go Finder has encountered a problem and needs to close.

[jneureut]

When trying to run the finder of an archive to go version 2.0.0.1 from a network drive I get the error “Archive To Go Finder has encountered a problem and needs to close.” I can run it fine if the archive is on a local drive.
I followed your instructions for running it from a nework drive to no avail. This has worked in the past for earlier versions of archive to go. I currenlty have no issues with version 1.5. I have .net framework security settings for local intranet set to full trust.
I also tried the Trust an assembly and browsed to the network drive, selected one of the archives going to the _viewer dir and and then selecting either a2gofinder.exe or a2goindexer.exe but it says Error Loading assembly Unable to laod assembly: (full path name). So I am unable to select the program to trust as an assembly like I can with version 1.5.

Topic

[jneureut]

I have uninstalled the .net 2.0 redistributable as well as the archive to go 2.0.0.5 off of my windows xp sp2 pc and rebooted. I redownloaded the 2.0.0.5 software from your site and then reinstalled the .net 2.0 redistributable and the archive to go 2.0.0.5 software. I then followed the instructions in the archive2go-creator.pdf “Archive to go will not run from a network drive”. When I get to the point where I select Import and select the a2gofinder.exe it says “The import failed. The assebly does not appear to be valid.” I cannot continue past this point and still cannot access the search feature of archives created with this version off of a windows 2008sp2 enterprise servers network drive. Makes it unusable at this point so any ideas?
The version 1.5 will work with the instructions from running it off a network drive with no error.

[Support 1]

Thank you for reporting this problem, and sorry for the delay.

I think the errors you get with the Trust an Assembly wizard and .NET Configuration tool (.NET 1.1) are due to them being incompatible with Archive To Go 2.x, because it is based on .NET 2.0. You could use the equivalent utilities for .NET 2.0 but (unlike in .NET 1.1) they are not included with a standard .NET 2.0 installation. They are only available with the .NET 2.0 Software Development Kit which is a 354 MB download.

Alternatively, you could try the following based on the CasPol (code access security policy) utility which is included with a standard .NET 2.0 installation.

• Open a command window: go to the Windows Start menu and press Run… (or press the Windows key + R), then enter ‘cmd’.
• Navigate to the directory of .NET 2.0 utilities: either enter the text below by hand or copy it to the clipboard, right-click on the command window and press Paste.

  cd WINDOWSMicrosoft.NETFrameworkv2.0.50727

• Similarly, enter the text below, but change ‘full path to a2gofinder.exe’ to the actual path on your network drive:

  caspol -q -m -ag All_Code -strong -file “full path to a2gofinder.exe” -noname -noversion FullTrust -name “Advansys Archive To Go” -description “Advansys Archive To Go for GroupWise suite of applications.”

I hope this helps. Please let me know how you go.

When we have received confirmation that the above suggestion works, we will update the featured topic Running Archive To Go from a Network drive accordingly.

Kind regards,
Advansys Support

[jneureut]

I figured out that it needed the .NET 2.0 configuration tool which I downloaded and installed from the .NET 2.0 SDK. I used that to expanded MyComputer->Runtime Security Policy->Machine->All_Code, right clicked on LocalIntranet_Zone and then selected properties. On the Permission Set tab I chaged it to FullTrust. That worked.

I did try your solution without needing to install the .NET 2.0 SDK and that worked as well. A lot easier too! Please update the documentaion for the 2.0.0.x version.as this would have been helpful..

Thanks again

[Support 1]

Many thanks for your confirmation.

The featured topic mentioned above has been updated and the next update Archive To Go will include this in its documentation.

Kind regards,
Advansys Support

[Author]

Replies