We have a developer that cannot access the applications folder in data servers or Managed reporting through dev studio in our production environment. He can run the reports through managed reporting online, but he cannot access them through dev studio. He has no problem in our pre-production evironment but when opening in our production evironment, he gets a 32033 error.

We are using AD and his permissions appear to be exactly the same as another user that can successfully access those dev studio components. His server permissions also seem to be identical to that user except for file shares (which don't pertain to this issue).

We cannot seem to find the problem. What kinds of issues lead to this error code? Thanks in advance

-J

This message has been edited. Last edited by: J,

Hi,

When the person goes into developer studio have them click on edaserve and when it prompts validate there. Then have them click on managed reporting and validate there. We have a couple of developers with the same issue it was found if they opened developer studio and went directly to managed reporting they would get the error, however if they went to edaserve first they did not. It's strange as all our machines use the same load so we have not been able to determine yet what is different.

Turns out he is fine on my installation of Dev Studio. I tried re-pointing to the environment and was still unsuccessful so I will probably just try to do a fresh install on his machine.

When I log onto his machine, everything works fine. It is only when he logs on to his machine that there are issues. I can't seem to eliminate the problem through a fresh install. I've tried to clean out the registry as much as possible and am still having issues.

I noticed that his environments still show up after all of this. Does anyone know where I can go to wipe out those defined environments? Thanks

-J

In windows XP it is located under documents and settings\userid\application data\information builders

The file wfscom.xml

Thanks CLH,

That will be good to know for future clean sweeps as well. We are still having issues and I have opened a case. I will post the solution once this is resolved.

We never ended up fixing this so we just re-imaged his machine and the problem was solved.