hd1

[hd1]

quote:

---

Do you mean that the problem has been resolved with this fix?

---

Yes

quote:

---

Can you confirm whether .NET 2.0 is installed on this server? Whether .NET 1.1 is also installed does not matter.

---

This does not matter, as long as .Net 1.1 is install the viewer will run. This site had some info on the issue.

http://www.sellsbrothers.com/askthewonk/Secure/Whydoesntmy.NETapplicatio.htm

So once full trust was adjusted on Local Intranet, the indexer ran fine. I guess because the indexer is a .Net app and the viewer is not? Maybe.

quote:

---

I am not sure what you mean by “code groups”. To change the “trust level” for Creator, I mean:

---

What I meant by code groups was when you open up .Net Configuration 1.1, you can click Runtime Security Policies to expand a tree for Enterprise, Machine, and User. Under each of these categories is Code Groups, Permission Sets, Policy Assemblies. I expanded Enterprise and right clicked “All_Code” to add a new trust for both the Finder and the Indexer. This however doesn’t need to be added once Full Trust is given to the Intranet.

quote:

---

To my knowledge, in order to execute a .NET assembly from another computer, it is sufficient to use the Trust an Assembly Wizard. It is also preferable to using Adjust Zone Security, which applies the new security setting to all assemblies in the relevant zone.

---

Yes this is much clearer now. I did add the programs to the Assembly wizard as well. I did not see anything about Adjust Zone security though, I must have overlooked that.

Thank you for your time and efforts!

Brian

[hd1]

I have sent off an email, I didn’t post the entire log just the error message at this time. Could we finish this discussion through email?

[hd1]

Here is the fix from one of the other IT persons here.

1. Go to: Settings >> Control Panel >> Administrative Tools >> Microsoft .NET Framework 1.1 Configuration

2. The .NET 1.1 Configuration module will appear. Click on the “Runtime Security Policy” folder on the left hand side of the screen.

3. Click on the “Adjust Security Zone” link in the body of the screen.

4. Click “Next.”

5. Click the “Local Intranet” security button

6. Adjusted the security to “FULL.”

[hd1]

.Net 1.1 was uninstalled while .Net 2.0 remained on the system. The error that was received while trying to perform an index search was this:

Archive to Go Finder has encountered a problem and needs to close. We are sorry for the inconvenience.

If you were in the middle of something, the information you were working on might be lost.

I am a little confused on what you posted.

“Unless there is some reason for running Creator off the network drive, restore the trust level for it back to the default. This maximizes your security.”

Does this mean remove my Code groups, or uninstall and reinstall .Net 1.1. I have tried uninstalling and reinstalling .Net 1.1 but that still didn’t work. My code groups are set to Enterprise level only.

Using the Wizard for .NET 2.0 (instead of .NET 1.1) increase the trust level for running Finder (and Indexer if indexing/reindexing might be necessary) from a network drive.

I only configuration and wizard I have is for .Net 1.1 I do not have any for .Net 2.0, and it is installed.

[hd1]

I copied the archive locally and it consumes about 4 GB. I ran the indexer for several hours and after finishing, the search works when the viewer is run off of the local drive and if the archive files and new index are on the local drive.

However, if I move the archive back to the network (with the new indexes) and try to run the viewer, the viewer will work but the a2GOFinder.exe will NOT work. It does NOT work even if I trust the assembly as indicated in the support documents.

If I run the viewer and try a search directly off of the console of the windows 2003 server, it works just fine.

[hd1]

I just got done adding in the .NET configuration new codes for both the indexer and the engine. I was unable to add the 2 viewer .exe it was saying the it was unable to import it. I still am having the same errors. I also went into the Wizards a gave full trust to the indexer and the engine as well, still same results. What else could I try? I don’t know if this applies or if I already mentioned it but the users are using a novell client to log into there machines. The machine hosting the archives is a Windows 2003 server.

[hd1]

I tried that on the machine that was accessing the information, but I got the same error. when I click OK it prompts me with a new one that does mention Security Permissions. I would like to know if this process should be done on the server as well. The viewer works fine it’s just then I access the finder. I only increased the trust level for the finder. Should I increase the trust level for all of the modules or will that cause problems?

[hd1]

Well I think I narrowed it down a little. The finder seems to run fine off of the local machine. Doesn’t seem to work at all when you run the archive from the network share. So maybe the computer hosting the archives needs to have archive to go as a trusted app as well, I guess I will look into that, but any input could help.

[Author]

Replies