dcom

问题 This is my first time dealing with IIS and DCOM so I apologize if I am butchering terminology: I am trying to develop an Intranet web site and I am having fits with what I think is a permissions issue. There is a function called from a DLL referenced in the web application that reads data from several DCOM applications on the web server. When I run the web application in the Visual Studio debugger on another computer on the network, it reads successfully. If I put the same DLL and function

问题 I have a COM server written in C++ running on some computer in a network. Clients may perform remote calls to it from the other computers. Can I determine the name of the user which make the call to the COM-methods from the methods itself? 回答1: You can accomplish this by calling CoImpersonateClient() from within a COM method. One you're impersonating, you can then call GetUserNameEx() to fetch the user name. 来源： https://stackoverflow.com/questions/9486348/how-can-i-get-the-user-name-who

问题 is there an api to change the Access Permissions for the COM Security? i need to write new values to "Edit Limits..." and "Edit Default...". are these plain registry settings? can't find how to set these entries. 回答1: The quick answer is Yes they are registry settings, the long answer is No they are not simple registry settings. The values are binary and point to an ACL structure. In order to change these you need to load, update, and save the ACL (which requires a fair amount of code). The

问题 I am creating a simple asp.net web site that use office 2007/2010 automation .. when i published the website on the iis 7 on my local machine (window 7) have an exception Retrieving the COM class factory for component with CLSID {000209FF-0000-0000-C000-000000000046} failed due to the following error: 80080005 Server execution failed (Exception from HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE)). I have searched for this exception and i found that i have to set some permissions to office in

问题 I developed a C# program that pulls data from a SQL Server database and then generates Word documents which include the data. I've set the program up to run as part of an SSIS job on a Windows Server 2003 box. The program runs as user SQLSVC which doesn't have administrative privileges. When I log in as SQLSVC and run the program it executes correctly. However, when the program is run automatically as an SSIS job it freezes at the following line of code Microsoft.Office.Interop.Word

问题 For many years I have used the old " SAP DCOM Connector " to communicate between Microsoft based applications and SAP. Unfortunately this old but good and performant technology is no longer supported by SAP since years. Therefore I want and must migrate to another newer technology. First there is the " SAP Connector for .NET 2.0 ". At first glance it seems to be a good replacement. But this connector can only used with .NET 1.1 (with a workaround also with .NET 2.0) and there is no further

问题 We need to figure out how a service can peek at a running VB6 app and/or its DCOM spawned exe and figure out which VB6 app goes with which DCOM exe. The VB6 app and the spawned exe are both on the same server. We have a VB6 app that spawns an instance of Bartender (from Seagull Scientific) by way of a CreateObject() call. On a given server, we may have ten or twenty instances of our app, each represents a handheld RF gun client in a warehouse. 95% or more of these VB6 apps will have their own

问题 I am using Microsoft Office Interop Word to generate documents using C#. In order for the document generation to work, there should be an entry for the "Microsoft Office Word 97 - 2003 Document" under the Dcom Config Settings as shown below: The Local Path under the General Tab has a correct path when Microsoft Office is first installed. If I then join the computer to a Domain, and then restart the system with a Domain user, the Local Path becomes blank and the application doesn't generate

问题 I know .net has WCF, which I believe was touted as the replacement for COM when it was codenamed Indigo(?) - but is it actually suitable for use in a .NET app, providing the same functionality as a C++/DCOM application? A DCOM app on a client-server system can be a pain, but I think it's quite efficient compared to other options like web-services - which have other issues anyway. So, is WCF a true successor to (D)COM or does it have different aims? EDIT: I'm talking specifically about

问题 I currently need to create a COM object that is served by an out-proc COM server from inside an ASP.NET handler. So every time I deploy the COM server I have to fire up DCOM Config and change the security settings. Specifically I need to ensure that both "local launch" and "local activation" is allowed fro the local user ASPNET. What surprises me is that when I open the relevant settings page "local launch" is already allowed but "local activation" is not allowed. That doesn't make sense -