Act! 2000 and ZyFind

[CidMatrix]

I have two problems. First, Act! 2000 runs intermittently. When I first installed it and tested, no problems. Soon as I rolled it out to my pilot group, not reliable. When it doesn't work, it gets stuck on the Act! splash screen and the server BOD's. Can't replicate it all the time.

Second problem involves a program called ZyFind by ZyLabs. When I first installed it and tested it, no problem. Now, the only people that can run it are Dom. Admins. The error I get is "Unable to access the registry". I know it sounds like a security issue on the registry, but, can't locate it where exactly.

My environemnt consists of two servers on W2K (SP2) and Metaframe XPa. Server 1 is a DC with DNS. Server 2 is Citrix primary. ZyFind works great on Server 2. Both servers had the applications installed exactly the same. I have since reinstalled SP2 on server 1 to try to fix issues mentioned above, but no luck.

I am using W2K Group Policy, but don't think this is a problem because I get the same error message without it. The only way I get a user to run ZyFind is by making them Dom. Admin. and I really don't want to do that.

Anyone have any ideas?

 

[CitrixEngineer]

I'm not familiar with either app, but here's a couple of quickies;

If ZyFind works OK on one server but not the other, then surely there's a difference in configuration somewhere?

You may want to check the version of ODBC/MDAC you're using. Some versions work better with Citrix MetaFrame than others.

To find a registry issue, you might want to run regmon from

http://www.sysinternals.com.

Have you applied the 5.03 Act patch?

If the server BSODs, it's more likely that a driver is playing up - probably a printer driver.

Running Filemon from sysinternals might track this one down.

Hope this helps

 

[CidMatrix]

Thanks for the help. I'll take a look at the sysinternals tool. I did get Zyfind to work. For whatever reason the install wasn't picked up by Citrix well because it didn't give sufficient registry rights. I manually gave rights to the group of users that will need this app and it worked. I haven't applied the Act patch, I'll look into that. I suspect a printer driver problem too. So, I've disabled client printer mapping and created the printers on the servers using correct drivers hopefully this works.