I had thought that I had this issue fixed, but unfortunately I don't. Here
is what we've got, and what's happening.



We've got several DLLs written in VB6, which resign on some Windows 2003
Servers, and are accessed, through COM+. Now, both Windows 2003 Servers
have service pack 1 installed on them. I previously learned that after
putting SP1 onto the Windows 2003 Servers that it may be necessary to modify
the COM+ security on the server to allow account under which the COM+
applications run on the server to be able to launch on the server. We have
two servers, a production server and a test server, and I've edited the
Launch and Activation Permissions to allow the network account to launch
remotely and locally, on both servers, in the same way for the same network
ID.



Our client machines are all Windows XP Professional machines with SP2.



The application is also written in VB6. Here is what happens:



Everyone can run the application, pointing the proxies to the test server to
run the middle-tier COM+ components off of that server, just fine. No
problems at all.



If the COM+ proxies on the client machines are pointing to the production
server, then only users who are members of the domain Administrators group,
can run the application. All other users will get a, "Permission denied"
error (error number 70), when attempting to instantiate an object.



As I said previously, the production and test servers are both Windows 2003
Servers with SP1 installed. The only thing I can think of, which is
different between the two of them, is the test server has SQL Server 2005
installed on it, and the production server has SQL Server 2000 installed on
it.



So, why is it that everyone can run the application, if the middle-tier
components being pointed to in the client machine's Component Services is on
the test server, but only Administrators can run the application if those
same middle-tier components are being pointed to the production server?





Rod

Archived from group: microsoft>public>vb>com