MZ@ !L!This program cannot be run in DOS mode. $Rؕ3}3}3}H̴3}H̱3}Rich3}PEL!  l@.rsrc@@0H  9:?F0GHH`IxLR      0 @ P ` p   pDH.x#*L134b7bКMUI?1O3-DDȤpIs S MUI en-USLocalRemoteLaunch ActivationAccessLaunch and Activationmachine-defaultapplication-specificPALimitsDefaultRemote Procedure Call (RPC)oThe RPCSS service is the Service Control Manager for COM and DCOM servers. It performs object activations requests, object exporter resolutions and distributed garbage collection for COM and DCOM servers. If this service is stopped or disabled, programs using COM or DCOM will not function properly. It is strongly recommended that you have the RPCSS service running.DCOM Server Process LauncherThe DCOMLAUNCH service launches COM and DCOM servers in response to object activation requests. If this service is stopped or disabled, programs using COM or DCOM will not function properly. It is strongly recommended that you have the DCOMLAUNCH service running.LocalHost (Using LRPC) UnavailableObject's implementation of IInspectable::GetTrustLevel returned a value that is different from the trust level configured for the class in the catalogPAPicturePAMActivatableClassId and CLSID entries do not reference each other consistentlyEActivatableClassId and CLSID entries in different registration scopesGActivatableClassId entry references a CLSID that is not a runtime classIActivatableClassId entry has missing or malformed ActivationType propertyDActivatableClassId entry has missing or malformed Threading property:ActivatableClassId entry has malformed TrustLevel propertyFActivatableClassId entry is marked outofproc, but has DllPath propertyJActivatableClassId entry is marked inproc, but is missing DllPath property7ActivatableClassId entry has malformed DllPath propertyBActivatableClassId entry is marked inproc, but has Server property8ActivatableClassId entry references missing Server entryFActivatableClassId and Server entries in different registration scopesLActivatableClassId entry is marked outofproc, but is missing Server propertyAActivatableClassId entry present, but a value was missing/invalidJActivatableClassId entry present, but CLSID and/or Server entry is missingGActivation of per-user ActivatableClassId denied from non-AppContainers9Server entry has missing or malformed ServerType property)Server entry has malformed AppID property=Server entry is not a normal exe but has CommandLine property/Server entry has malformed CommandLine property<Server entry has non-exe ServerType but has ExePath property<Server entry is a normal exe but is missing ExePath property+Server entry has malformed ExePath property;Server entry has missing or malformed IdentityType property?Per-user Server registration must not have a RunAs IdentityType@Per-user Server registrations must not have ServiceName property.Server entry has malformed Instancing property3Server entry is not RunAs but has Identity property6Server entry is RunAs but is missing Identity property,Server entry has malformed Identity property:Server entry is not a service but has ServiceName propertyPA:Server entry is a service but missing ServiceName property/Server entry has malformed ServiceName property2Server entry references missing AppID registration/Server entry has malformed Permissions property2Server entry has malformed PackageMoniker property2Server entry has malformed appUserModelID property7Server entry is a service but IdentityType is not RunAs5Server entry present, but a value was missing/invalidFPer-machine Server registrations must not have PackageMoniker propertyNPer-machine Server registration must not have a ActivateAsPackage IdentityTypeDPer-machine Server registration must not have an Instancing propertyFPer-machine Server registrations must not have appUserModelID propertyAActivateAsActivator servers must not have PackageMoniker property?Server entry has non-exe ServerType but has ClassNames property.Server entry has malformed ClassNames property0Server entry has malformed DebuggerPath property/Server entry has malformed Environment property<The executable pointed to by the ExePath property is missingTServer is per user ActivateAsActivator, must not be activated from non app containerPABInterface entry has missing or malformed proxy/stub CLSID property5Proxy/Stub CLSID entry has malformed DllPath propertyPA?CoInitialize cannot be called from apartment shutdown callbacksQRoRegisterForApartmentShutdown cannot be called from apartment shutdown callbacks RoUnregisterForApartmentShutdownA COM call (IID: %1, method index: %2!d!) to an ASTA (thread %3!d!) was blocked because the call chain originated in or passed through another ASTA (thread %4!d!). This call pattern is deadlock-prone and disallowed by apartment call control.PA%''''`''''\'('+'6'!GGh2G(GD3+G+GdL-G-GN88QQS  S00U*'@*'@UPPWQQWSSWSSWSSWXHXXY\YYY  XZ00Z@@x[PP[''T\''$^''^''l_,G,G`Unable to start a DCOM Server: %3. The error:%n"%2"%nHappened while starting this command:%n%1 Unable to start a DCOM Server: %3 as %4/%5. The error:%n"%2"%nHappened while starting this command:%n%1 DCOM got error "%1" and was unable to logon %2\%3 in order to run the server:%n%4 DCOM got error "%1" attempting to start the service %2 with arguments "%3" in order to run the server:%n%4 DCOM got error "%1" from the computer %2 when attempting to activate the server:%n%3 DCOM got error "%1" from the computer %2 when attempting to the server:%n%3 with file %4. The server %1 did not register with DCOM within the required timeout. The activation for CLSID %1 failed because remote activations for COM+ are disabled. To enable this functionality use Server Manager to install the COM+ Network Access feature in the Application Server role. |The machine wide limit settings do not grant %1 %2 permission for the COM Server application with CLSID %n%3%n and APPID %n%4%n to the user %5\%6 SID (%7) from address %8 running in the application container %9 SID (%10). This security permission can be modified using the Component Services administrative tool. tThe %1 permission settings do not grant %2 %3 permission for the COM Server application with CLSID %n%4%n and APPID %n%5%n to the user %6\%7 SID (%8) from address %9 running in the application container %10 SID (%11). This security permission can be modified using the Component Services administrative tool. \The %1 permission settings do not grant %2 access permission to the COM Server application %3 with APPID %n%4%n to the user %5\%6 SID (%7) from address %8 running in the application container %9 SID (%10). This security permission can be modified using the Component Services administrative tool. The application-specific permission settings do not grant %1 access permission to the COM Server application %2 with APPID %n%3%n to the user %4\%5 SID (%6) from address %7 running in the application container %8 SID (%9). The application set this security permission programmatically; to modify this security permission contact the application vendor. dThe machine wide limit settings do not grant %1 access permission to the COM Server application %2 with APPID %n%3%n to the user %4\%5 SID (%6) from address %7 running in the application container %8 SID (%9). This security permission can be modified using the Component Services administrative tool. The machine wide %1 %2 security descriptor is invalid. It contains Access Control Entries with permissions that are invalid. The requested action was therefore not performed. This security permission can be corrected using the Component Services administrative tool. The launch and activation security descriptor for the COM Server application with APPID %n%1%n is invalid. It contains Access Control Entries with permissions that are invalid. The requested action was therefore not performed. This security permission can be corrected using the Component Services administrative tool. tThe %1 access security descriptor for the COM Server application %2 with APPID %n%3%n is invalid. It contains Access Control Entries with permissions that are invalid. The requested action was therefore not performed. This security permission can be corrected using the Component Services administrative tool. The application-specific access security descriptor for the COM Server application %1 with APPID %n%2%n is invalid. It contains Access Control Entries with permissions that are invalid. The requested action was therefore not performed. The application set this security permission programmatically; to modify this security permission contact the application vendor. The machine wide group policy %1 Limits security descriptor is invalid. The security descriptor is defined as an invalid Security Descriptor Definitions Language (SDDL) string. The requested action was therefore not performed. Please contact your administrator to get the security descriptor corrected in the Group Policy settings. ,The machine wide limit settings do not grant %1 %2 permission for COM Server applications to the user %3\%4 SID (%5) from address %6 running in the application container %7 SID (%8). This security permission can be modified using the Component Services administrative tool. DCOM was unable to communicate with the computer %1 using any of the configured protocols; requested by PID %2 (%3). The activation of the CLSID %1 timed out waiting for the service %2 to stop. Unable to start a COM Server for debugging: %3. The error:%n"%2"%nHappened while starting this command:%n%1 An unmarshaling policy check was performed when unmarshaling a custom marshaled object and the class %1 was rejected An unmarshaling policy check was performed when unmarshaling a custom inproc handler and the class %1 was rejected An unmarshaling policy check was performed when unmarshaling a COM+ envoy context property and the class %1 was rejected An unmarshaling policy check was performed due to CLSCTX_NO_CUSTOM_MARSHAL and the class %1 was rejected xThe COM standard marshaler was unable to fix a mismatch between the IID %1 provided by the server and the IID %2 requested by the client, with handler CLSID %3. The error code was %4. The server-side authentication level policy does not allow the user %1\%2 SID (%3) from address %4 to activate DCOM server. Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application. tApplication %1 with PID %2 is requesting to activate CLSID %3 on computer %4 with explicitly set authentication level at %5. The lowest activation authentication level required by DCOM is 5(RPC_C_AUTHN_LEVEL_PKT_INTEGRITY). To raise the activation authentication level, please contact the application vendor. |Application %1 with PID %2 is requesting to activate CLSID %3 on computer %4 with default activation authentication level at %5. The lowest activation authentication level required by DCOM is 5(RPC_C_AUTHN_LEVEL_PKT_INTEGRITY). To raise the activation authentication level, please contact the application vendor. DCOM server attempted to listen on an invalid endpoint. Protocol Sequence: %1 Endpoint: %2 Flags: %3 |The machine wide limit settings do not grant %1 %2 permission for the COM Server application with CLSID %n%3%n and APPID %n%4%n to the user %5\%6 SID (%7) from address %8 running in the application container %9 SID (%10). This security permission can be modified using the Component Services administrative tool. tThe %1 permission settings do not grant %2 %3 permission for the COM Server application with CLSID %n%4%n and APPID %n%5%n to the user %6\%7 SID (%8) from address %9 running in the application container %10 SID (%11). This security permission can be modified using the Component Services administrative tool. \The %1 permission settings do not grant %2 access permission to the COM Server application %3 with APPID %n%4%n to the user %5\%6 SID (%7) from address %8 running in the application container %9 SID (%10). This security permission can be modified using the Component Services administrative tool. The application-specific permission settings do not grant %1 access permission to the COM Server application %2 with APPID %n%3%n to the user %4\%5 SID (%6) from address %7 running in the application container %8 SID (%9). The application set this security permission programmatically; to modify this security permission contact the application vendor. dThe machine wide limit settings do not grant %1 access permission to the COM Server application %2 with APPID %n%3%n to the user %4\%5 SID (%6) from address %7 running in the application container %8 SID (%9). This security permission can be modified using the Component Services administrative tool. The machine wide %1 %2 security descriptor is invalid. It contains Access Control Entries with permissions that are invalid. The requested action was therefore not performed. This security permission can be corrected using the Component Services administrative tool. The launch and activation security descriptor for the COM Server application with APPID %n%1%n is invalid. It contains Access Control Entries with permissions that are invalid. The requested action was therefore not performed. This security permission can be corrected using the Component Services administrative tool. tThe %1 access security descriptor for the COM Server application %2 with APPID %n%3%n is invalid. It contains Access Control Entries with permissions that are invalid. The requested action was therefore not performed. This security permission can be corrected using the Component Services administrative tool. The application-specific access security descriptor for the COM Server application %1 with APPID %n%2%n is invalid. It contains Access Control Entries with permissions that are invalid. The requested action was therefore not performed. The application set this security permission programmatically; to modify this security permission contact the application vendor. The machine wide group policy %1 Limits security descriptor is invalid. The security descriptor is defined as an invalid Security Descriptor Definitions Language (SDDL) string. The requested action was therefore not performed. Please contact your administrator to get the security descriptor corrected in the Group Policy settings. ,The machine wide limit settings do not grant %1 %2 permission for COM Server applications to the user %3\%4 SID (%5) from address %6 running in the application container %7 SID (%8). This security permission can be modified using the Component Services administrative tool. The attempt to connect to the RPCSS service was denied access for the COM Server application %1 to the user %2\%3 SID (%4) running in the application container %5 SID (%6). The most likely cause is that the machine wide Access Limits do not grant the user or application local access permissions. The Access Limits can be modified using the Component Services administrative tool. Classic hIdentifies events for asynchronous operations. dIdentifies events for synchronous work items. Identifies events relating synchronous work items to asynchronous operations. Identifies events for work done by asynchronous operations. lIdentifies events orginated by system components. Identifies events originated by libraries and language projections. hIdentifies events originated by an application. Identifies events originated by the creation of an asynchronous operation. Info Start Stop The COM sub system is suppressing duplicate event log entries for a duration of %1 seconds. The suppression timeout can be controlled by a REG_DWORD value named %2 under the following registry key: HKLM\%3. Information Error Critical Warning Verbose DMicrosoft-Windows-WinRT-Perf LMicrosoft-Windows-DistributedCOM System DMicrosoft-Windows-COMRuntime Application LMicrosoft-Windows-AsyncCausality @Microsoft-Windows-OLE-Perf DMicrosoft-Windows-WinRT-Error xEvent fired when an asynchronous operation is created. |Event fired when an asynchronous operation is completed. Event fired relating a synchronous work items to an asynchronous operation. lEvent fired when a synchronous work item starts. pEvent fired when a synchronous work item completes. Access denied attempting to launch a DCOM Server. The server is:%n%1%nThe user is %2/%3, SID=%4. Access denied attempting to launch a DCOM Server using DefaultLaunchPermssion. The server is:%n%1%nThe user is %2/%3, SID=%4. DCOM got error "%1" when attempting to activate the server:%n%2 DCOM was unable to communicate with the computer %1 using any of the configured protocols. The server %1 could not be contacted to establish the connection to the client There is an assertion failure in DCOM. Context follows: %1 %2 %3 <OLE (Object Linking and Embedding) in the application "%1" was trying to convert embedded content in a document; however, OLE no longer supports the presentation format for the embedded content. Newer versions of this application may support this presentation format natively.%r%r 4VS_VERSION_INFOP%P%?StringFileInfo040904B0LCompanyNameMicrosoft Corporation\FileDescriptionMicrosoft COM for Windows1FileVersion6.3.9600.20625 (winblue_ltsb_escrow.221003-0335)8 InternalNameCOMBASE.DLL.LegalCopyright Microsoft Corporation. All rights reserved.HOriginalFilenameCOMBASE.DLL.MUIj%ProductNameMicrosoft Windows Operating SystemBProductVersion6.3.9600.20625DVarFileInfo$Translation PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGX