Error code 0xe0434f4d

[mrisen]

We are using WIX to create an install package for our client extensions.

Inside the installer file, after running spregpkg /m:register /p:mypackage.dll, we then call select.exe /setup. This ends up crashing and returning error code 0xe0434f4d, causing a rollback. Does anyone know what error code 0xe0434f4d is and/or how to fix it or if there is another way to get more information?

Thanks,
.Mark

[John Morris]

Ensure that the installer is running with elevated privileges.

Also, are there any entries in the windows event log?

[mrisen]

A non-admin user was logged in, I started a command console as a user in the local administrators group and ran the installer. The below event log entry may be pertinent.


The commands for package Package were not merged. Parameter '' cannot be null.
Parameter name: serializationStream

Call Stack:
at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
at System.Environment.get_StackTrace()
at System.Diagnostics.TraceEventCache.get_Callstack()
at SoftPro.Select.LogTraceListener.OnLog(TraceEventCache eventCache, String message, TraceEventType eventType)
at SoftPro.Select.LogTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message)
at System.Diagnostics.TraceInternal.TraceEvent(TraceEventType eventType, Int32 id, String format, Object[] args)
at System.Diagnostics.Trace.TraceError(String message)
at SoftPro.Select.Managers.CommandManager.MergeCommandTables()
at SoftPro.Select.Runtime.OnSetup()
at SoftPro.Select.Runtime.Start()
at SoftPro.Select.Automation.EnvICE.Start()
at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)
at System.Runtime.Remoting.Messaging.ServerObjectTerminatorSink.SyncProcessMessage(IMessage reqMsg)
at SoftPro.Select.Shell.SynchronizationContextAspect.SyncProcessMessage(IMessage msg)
at System.Runtime.Remoting.Lifetime.LeaseSink.SyncProcessMessage(IMessage msg)
at System.Runtime.Remoting.Messaging.ServerContextTerminatorSink.SyncProcessMessage(IMessage reqMsg)
at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessageCallback(Object[] args)
at System.Threading.Thread.CompleteCrossContextCallback(InternalCrossContextDelegate ftnToCall, Object[] args)
at System.Threading.Thread.InternalCrossContextCallback(Context ctx, IntPtr ctxID, Int32 appDomainID, InternalCrossContextDelegate ftnToCall, Object[] args)
at System.Threading.Thread.InternalCrossContextCallback(Context ctx, InternalCrossContextDelegate ftnToCall, Object[] args)
at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessage(IMessage reqMsg)
at System.Runtime.Remoting.Proxies.RemotingProxy.CallProcessMessage(IMessageSink ms, IMessage reqMsg, ArrayWithSize proxySinks, Thread currentThread, Context currentContext, Boolean bSkippingContextChain)
at System.Runtime.Remoting.Proxies.RemotingProxy.InternalInvoke(IMethodCallMessage reqMcmMsg, Boolean useDispatchMessage, Int32 callType)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(IMessage reqMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at SoftPro.Select.Automation.EnvICE.Start()
at SoftPro.Select.Automation.EnvICE.Run(String rootSuffix, Boolean noSplash, Boolean setupMode, Boolean log, Boolean embedding, Dictionary`2 args, String freeArg)
at SoftPro.Select.Program.Main(String[] args)

[John Morris]

Try running the select.exe /setup command from a debugger. What is the first exception it runs into?

The stack trace provided doesn't give the needed information. It is the logging call stack, not the exception call stack.

[mrisen]

Ok, so the issues does not reproduce outside of the installer. And since the installer spawns that process, it's outside of the debugger. When I run the command directly, inside a debugger, or not, it does not throw the exception. I was able to obtain mini dump files, however, if that would be useful. In the meantime, I'm going to check on the command being called in WIX and see if I'm not escaping characters correctly.

Please let me know where to send the dump files if you would like to look at them.