1 Attachment(s)
What tools can I use to find out the reason for this error?
This has been happening since today morning. I get this error when I try to open my project.
Creating a new project is not an issue. I suspect activeX controls are causing this issue.
Our entire development is carried out on a Citrix Terminal Server. I went to my profile folder and deleted all the files. This has not helped. It still throws up the error.
I am thinking of downloading FileMon
Do you know of any other tools that could be better and easy to use?
:wave:
Re: What tools can I use to find out the reason for this error?
Quote:
Originally Posted by abhijit
... I suspect activeX controls are causing this issue.
You are right about it - control may need to be reinstalled or at least re-registered.
Also, (and out of curiosity only) why are you developing over citrix?
All development should really be done on your development machine so you won't "stress" server.
Re: What tools can I use to find out the reason for this error?
Quote:
Originally Posted by RhinoBull
You are right about it - control may need to be reinstalled or at least re-registered.
Also, (and out of curiosity only) why are you developing over citrix?
All development should really be done on your development machine so you won't "stress" server.
Organization policy. :sick: :sick:
Re: What tools can I use to find out the reason for this error?
Ouch! It's very unusal (to say the least :rolleyes: ) policy.
Re: What tools can I use to find out the reason for this error?
Quote:
Originally Posted by RhinoBull
Ouch! It's very unusal (to say the least :rolleyes: ) policy.
Not to mention, very frustrating. :mad: :mad:
Re: What tools can I use to find out the reason for this error?
Well, it's just a job and nothing personal, right ? :)
Anyhow, did you try reinstalling that component?
Re: What tools can I use to find out the reason for this error?
Quote:
Originally Posted by RhinoBull
Well, it's just a job and nothing personal, right ? :)
Anyhow, did you try reinstalling that component?
The windows server admin reinstalled MS Common Dialog. That has resolved the issue. He copied over the same files from another server on a farm.
Suprisingly the issue only seemed to affect the IDE and not the executable on the same server.
:wave: