I've had to deal with the exact same issue. This problem requires a registry edit. I don't have the link to the info at present, I'll see if I can haul it up for you.

Here you go:
 
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q260151

Thanks, I'll try that.

i also noticed that same problem. the registry thingy works
but also w2k seems to have permissions problem
i have fixed many of the problems by resetting the permissions

The registry edit allows user specific privellege to the program, without having to change machine wide rights and priveleges. Or, in some cases network priveledges, no point making your regular users into Power users, or building exotic MSI scripts to give access to a simple program, when it can be done at a local level using Regedit.
 
Fact is, the problem shouldn't be there in the first place \

It depends on the issue, in many cases the application designer should be keeping file and registry key placement in mind when the application is created, but many are in fact too lazy to do this. This particular issue that Catdog is illustrating is along the same vein, but is slightly different. The problem stems from more of a "hiccup" during installation than anything else, and the key permissions were not set properly. This is common in upgrade scenarios, where an older application did not require R/W access to a key, and the upgrade installer did not take permissions into account. Some of the worst offenders are major application vendors like AutoCAD, that seem completely incapable of moving their crappy files into their own directory (R/W access needed), and not allowing for registry permission configs in typical NT networks. Again, a simple matter of just being too damn lazy.