"Permission Denied" only under WinXP-SP2

[Giobibo]

Probably here is not the right place to post, but I've already tried in
other newsgroups. The problem is that I get the errors only under XP and
not under other MS-OS:

I have a client-server application written in VB5 running fine since
years on Win98, WinNT e Win2000 systems.
Client and server are ActiveX components accessed by Remote Automation.
Now I have tried to install the application on a WinXP-SP2 PC, but I get
a "Permission denied" error while creating the call-back object on
the client PC.

The Remote OLE works only partially:
1) the client succeeds to create the server object on the remote PC
2) The server on the remote PC succeeds to create call-back object on
the server
3) But the last step does not happen: the server on the remote PC cannot
create the call-back object on the client machine

I have disabled the firewall, but I got no result.

Any suggestions?

Thank yoo for replying.

 

[Dave Patrick]

Try asking them here.

http://www.microsoft.com/communitie...8da-b619-44cd-a361-5c6f36369666&lang=en&cr=US

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

 

[Giobibo]

Try asking them here.

http://www.microsoft.com/communitie...8da-b619-44cd-a361-5c6f36369666&lang=en&cr=US

I have already asked there, but I did not make any progress...

There is something todo with the XP security setting or something like
that, but I cannot find any warkorund.

Thank you anyway for your reply.
Gio

 

[Guest]

I have already asked there, but I did not make any progress...

There is something to do with the XP security setting or something like
that, but I cannot find any workaround.

Thank you anyway for your reply.
Gio

While sitting at the PC you are trying to get to call back, can you create
the call back object and have it work? If yes, it is indeed a security
related problem. If no, it's something in your script that needs to be
changed for Windows XP. If you cannot sit at the PC or have someone with
authorization to sit at the PC and run this test, I would wait until you can
sit at the PC and try the above test before investing anymore time with this
project.

Once you can determine for sure it's a security related problem, you can
turn off security for the computer. This is not a very easy task, nor should
it be taken lightly. You'll have to make sure the services you want to use
can interact with your script.
Go to Control Panel > Administrative Tools > Component Services > Services
(Local)
Do what you must do only with administrator approval. You CAN and WILL cause
harm by not knowing what you're doing here. Ask a local computer geek if you
cannot or are not sure where to go from here.

RECORD everything you do on PAPER! Not Notepad or other utility on the
computer. This is incase the computer crashes and you need to restore it back
to the original configuration.

Once you're done. Slowly restore as much security back to the computer as
possible.

NOTE: You've just made this computer susceptible to intruders that use your
technique of call back. I would suggest not having that computer wired to any
networks and not to store any sensitive data on that computer. Of course,
this could defeat the purpose of using the script in the first place.

 

[Guest]

While sitting at the PC you are trying to get to call back, can you create
the call back object and have it work? If yes, it is indeed a security
related problem. If no, it's something in your script that needs to be
changed for Windows XP. If you cannot sit at the PC or have someone with
authorization to sit at the PC and run this test, I would wait until you can
sit at the PC and try the above test before investing anymore time with this
project.

Once you can determine for sure it's a security related problem, you can
turn off security for the computer. This is not a very easy task, nor should
it be taken lightly. You'll have to make sure the services you want to use
can interact with your script.
Go to Control Panel > Administrative Tools > Component Services > Services
(Local)
Do what you must do only with administrator approval. You CAN and WILL cause
harm by not knowing what you're doing here. Ask a local computer geek if you
cannot or are not sure where to go from here.

RECORD everything you do on PAPER! Not Notepad or other utility on the
computer. This is incase the computer crashes and you need to restore it back
to the original configuration.

Once you're done. Slowly restore as much security back to the computer as
possible.

NOTE: You've just made this computer susceptible to intruders that use your
technique of call back. I would suggest not having that computer wired to any
networks and not to store any sensitive data on that computer. Of course,
this could defeat the purpose of using the script in the first place.

As a bonus, I believe MS is also not providing support for VB 5.0 anymore.
Which means that you'll have to upgrade your application. This also could be
the cause for your script not working anymore.

 

[Twayne]

In

I am also facing such type of problem since we have
migrated to win xp. Pls tell me the soln if any.

Thanks in advance.

url:http://www.ureader.com/msg/127827742.aspx

WHAT problem? You didn't Reply so the whole set of posts preceding yours is
gone.