Windows Forum

Ask something
Discussion Locked

Persistent Symbols in XP

0 helpful
3 replies

by dennis.rhine 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are in the process of upgrading several of our computers from Windows 2000 to Windows XP and I have run into a strange problem - probably related to a security change in XP with SP2.

The problem is encountered when I install a program called Vision:ClearAccess. This program runs scripts to access data on a mainframe computer and then generate a report based on that data. In Windows XP the user will get a message stating that he/she doesn't have permissions to write persistent symbols. Clicking on OK will allow the user to continue and, at least apparently, run the script and complete the task.

As I stated above, I believe that this is a permissions problem with XP but I cannot find anything on the web about the problem. Computer Associates, who (I think) currently own the rights to the program don't have anything about this either. In fact, I didn't see where they even had an active support page for this program (although they did have other Vision: programs).

Any ideas about what needs to be changed?

3 replies

by cg it

If it works without service pack 2 and doesn't work with service pack 2, don't install service pack 2. If it's the firewall that comes with service pack 2, disable it. It the compuers who use this program never have access to the internet, don't install service pack 2. If you upgrade to XP simply to upgrade without really a need to , don't upgrade those computers. There are companies that run old O/S simply because they have old programs that they run that do not run on XP and they can't afford to buy the new program. This is the norm rather than the exception. Note Microsofts announcement of a O/S named Geiger that will breathe new life in old comps because schools and non profits can't afford to buy new computers let alone new O/Ss to run on the new computer. Again this is the norm, not the exception. Only very large businesses with healthy business income can afford to constantly upgrade their IT infrastructure on the software and hardware mfgs 3 year cycle.

by sgt_shultz

sell said, CG
anything in the event logs?
i would use regedt32 to examine the permissions on the registry entries for that program.
I would login as domain admin and see if I have the same problem.
if on right track I would give myself local admin group membership and try that.
I would see if i could use XP compatibility mode for the problem program. find the executable and right click it see if it offers you Run in Compatibility mode.
that is maybe a good sign that they don't seem to know anything about problems with xp compatibility.
see if you can get it working somehow then keep calling them politely to keep them apprised of your progress. because i do hear CG but we don't have choice in the matter. ms has declared xp to be the preferred client so i, like you, just go with the flow. sooner or later have to. best to do it now as you are doing. good luck post back with EXACT error message and steps to reproduce and anything you've tried and the results.

by sgt_shultz

er...ever since they took out (or did they never have a) 'watch this thread' feature here at tech republic, i don't come back to old questions. so if now joy on this posting i suggest post it again with more info as suggested in a new question

This discussion is closed to new replies.