| Author |
Message |
BS
Guest
|
 Posted:
Tue Mar 01, 2005 10:17 pm Post subject:
Problems with Windows 2003 Server |
|
|
I can not start working COMTI on Windows Server 2003.
Probably I do not have enough permission with my user, but I do not know
where to set them.
I am using Component Bulider for Unisys MCP and it keeps saying "Permission
Denied".
There is no problematic event in event log. So I do not know where to
search.
I can normally register components through regsvr32 command, so there should
be no catch.
I even reinstalled "Application Server" components in Windows Setup, but it
did not help.
Tommorow I will reinstall the whole server, maybe someone have the answer
from the hand? |
|
| Back to top |
|
 |
Paul Skaistis
Guest
|
| Posted:
Wed Mar 02, 2005 6:49 am Post subject:
Re: Problems with Windows 2003 Server |
|
|
What operation caused the "Permission Denied" message? What were you doing
when the error occurred?
Are you using HIS 2000 or HIS 2004? |
|
| Back to top |
|
|
BS
Guest
|
| Posted:
Wed Mar 02, 2005 1:23 pm Post subject:
Re: Problems with Windows 2003 Server |
|
|
HIS 2000 is installed.
Unisys COMTI version MCP 8.0 (Cycle 189, Patch 8019) is installed.
"Permission Denied" message
This message I get from COMTI component builder. When I try to publish my
component (Add to Package or Application) I can select COM+ Package and
Remote Environment.
But when I click OK button only "Permission Denied" message is shown.
I can not see where the problems are . . .
"Paul Skaistis" <paulskaistis@organization.com> wrote in message
news:%23WgxSKvHFHA.1528@TK2MSFTNGP09.phx.gbl...
| Quote: | What operation caused the "Permission Denied" message? What were you
doing
when the error occurred?
Are you using HIS 2000 or HIS 2004?
|
|
|
| Back to top |
|
|
Paul Skaistis
Guest
|
| Posted:
Wed Mar 02, 2005 9:20 pm Post subject:
Re: Problems with Windows 2003 Server |
|
|
To help pin this down you can make sure you are auditing security events
(Local Security Policy -> Audit Policy). Then check the security log via
event viewer after a failure occurs.
Perhaps there is a Domain Policy that is preventing access.
Can you create a COM+ Application using the Component Services MMC? Then
add the component there? |
|
| Back to top |
|
|
BS
Guest
|
| Posted:
Thu Mar 03, 2005 6:18 pm Post subject:
Re: Problems with Windows 2003 Server |
|
|
I had to set permissions for the vbc.exe file (ASP.NET compiler for VB) to
"Read & Execute".
After that access to my COM component was enabled.
Then I could run web pages from local computer and it's ISS.
When I tryed to run those web pages from IIS on another computer (using
DCOM) I could not to that.
So I disabled authorisation checking for taht specific COM+ Application and
now I can run it freely & easily.
Thx for your help . . . .
"Paul Skaistis" <paulskaistis@organization.com> wrote in message
news:ulWzbtzHFHA.3332@TK2MSFTNGP15.phx.gbl...
| Quote: | To help pin this down you can make sure you are auditing security events
(Local Security Policy -> Audit Policy). Then check the security log via
event viewer after a failure occurs.
Perhaps there is a Domain Policy that is preventing access.
Can you create a COM+ Application using the Component Services MMC? Then
add the component there?
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in