The ServicedComponent being invoked is not correctly configured (Use regsvcs to re-register).
이런 유의 오류가 발생하면서,
Server Error in '/' Application.
The ServicedComponent being invoked is not correctly configured (Use regsvcs to re-register).
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.EnterpriseServices.ServicedComponentException: The ServicedComponent being invoked is not correctly configured (Use regsvcs to re-register).
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[ServicedComponentException: The ServicedComponent being invoked is not correctly configured (Use regsvcs to re-register).]
System.EnterpriseServices.ServicedComponentProxy.FilterConstructors() +115
System.EnterpriseServices.ServicedComponentProxyAttribute.CreateInstance(Type serverType) +752
System.Runtime.Remoting.Activation.ActivationServices.IsCurrentContextOK(Type serverType, Object[] props, Boolean bNewObj) +67
TestWebApp.ComPlusServerTest.Page_Load(Object sender, EventArgs e) in C:\Temp\TestWebApp\ComPlusServerTest.aspx.cs:63
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +14
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +43
System.Web.UI.Control.OnLoad(EventArgs e) +91
System.Web.UI.Control.LoadRecursive() +74
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1716
메시지에 따라 regsvcs.exe로 COM+ 객체를 등록할 때 다음의 오류 메시지가 나오는 경우,
The following installation error occurred:
1: One or more of the components being installed are already registered as 64 bit components in the target application. You must install the 32 bit versions of the components being installed in a diff
erent COM+ application, or delete the existing 64 bit versions of the components being installed from the target COM+ application prior to attempting install of the 32 bit versions. COM+ applications
cannot contain bit neutral components.
아마도 .NET COM+ DLL을 이미 COM+에 64비트 Library 유형으로 등록한 상태에서 다시 32비트로도 COM+에 등록하는 경우일 것입니다.
어쩔 수 없습니다. 만약 저런 상황이 나오면 해당 COM+ 객체를 64비트와 32비트에 대해 ApplicationName 등의 속성을 별도 분리해서 컴파일해야 합니다.
#if DEF_X86BUILD
[assembly: ApplicationName("MyComponentLibraryX86")]
#else
[assembly: ApplicationName("MyComponentLibrary")]
#endif
또한 각각의 Library 유형에서 서비스하게 되는 COM+ 객체의 GUID도 바꿔서,
#if DEF_X86BUILD
[System.Runtime.InteropServices.Guid("F873A6B6-ADC0-4C51-AF0F-FC2F88E466A6")]
#else
[System.Runtime.InteropServices.Guid("BDC0B215-0BA0-465A-A0C8-7CD5C7120ECF")]
#endif
public class MyComponentLibrary : ServicedComponent
{
// ...[생략]...
}
빌드하면, 이후 해당 COM+를 사용하는 32/64비트 응용 프로그램은 정상적으로 객체를 등록/활성화할 수 있습니다.
[이 글에 대해서 여러분들과 의견을 공유하고 싶습니다. 틀리거나 미흡한 부분 또는 의문 사항이 있으시면 언제든 댓글 남겨주십시오.]