Our CRM experienced an error and cannot update the record and experienced this error:
`
Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: Cannot update Closed or Cancelled ActivityDetail:
<OrganizationServiceFault xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/xrm/2011/Contracts">
<ErrorCode>-2147220891</ErrorCode>
<ErrorDetails xmlns:d2p1="http://schemas.datacontract.org/2004/07/System.Collections.Generic">
<KeyValuePairOfstringanyType>
<d2p1:key>OperationStatus</d2p1:key>
<d2p1:value xmlns:d4p1="http://www.w3.org/2001/XMLSchema" i:type="d4p1:string">0</d2p1:value>
</KeyValuePairOfstringanyType>
<KeyValuePairOfstringanyType>
<d2p1:key>SubErrorCode</d2p1:key>
<d2p1:value xmlns:d4p1="http://www.w3.org/2001/XMLSchema" i:type="d4p1:string">-2146233088</d2p1:value>
</KeyValuePairOfstringanyType>
</ErrorDetails>
<Message>Cannot update Closed or Cancelled Activity</Message>
<Timestamp>2016-11-08T03:37:50.997897Z</Timestamp>
<InnerFault i:nil="true" />
<TraceText>
[Microsoft.Crm.ObjectModel: Microsoft.Crm.ObjectModel.SyncWorkflowExecutionPlugin]
[79b7ca55-7812-e611-8126-c4346bad26cc: ]
Starting sync workflow 'Ph2 CSF Status', Id: 6eb7ca55-7812-e611-8126-c4346bad26cc
Entering ConditionStep1_step: Automatic update of Status field in CSF
Entering SetStateStep15_step: If RM approves the CSF
Sync workflow 'Ph2 CSF Status' terminated with error 'Cannot update Closed or Cancelled Activity'
</TraceText>
</OrganizationServiceFault>
`
this happened when we try to update an existing record from in process to approved.
The error is pretty self-explanatory I think:
workflow 'Ph2 CSF Status' terminated with error 'Cannot update Closed or Cancelled Activity'
Your workflow has a step ("If RM approves the CSF") which is trying to update an activity which is already close/cancelled. You will need to update the activity before closing it or change the status to an active on before updating it (and then close it again).
Related
After reboot device, if I directly visit today widgets, my app's today widget will show with "unable to load" (But if - after reboot device, firstly, I open my app, and then visit today widgets, everything works fine)
I tried my ways, but there is no way to debug this issue. I try to use "iOS Console", and get following error logs:
key error logs:
Sep 19 18:37:37 My-iPhone SpringBoard(Widgets)[58] <Notice>: <com.***.***: 0x109008200; container: WGWidgetListItemViewController> Remove snapshots at file:///private/var/mobile/Containers/Data/PluginKitPlugin/3E4710C0-9E8F-4F87-B6DA-D7072057B92D/Library/Caches/com.apple.notificationcenter/Snapshots/com.***.***-PhoneTall-359-zh_CN-UICTContentSizeCategoryL-NCWidgetDisplayModeCompact.ca/ due to error: Error Domain=CAARFileLoadingDomain Code=950000 "(null)" UserInfo={NSUnderlyingError=0x1cc448f40 {Error Domain=CoreAnimationErrorDomain Code=2 "Unable to load CAPackage from URL: index.xml
Sep 19 18:37:39 My-iPhone SpringBoard(PlugInKit)[58] <Error>: Hub connection error Error Domain=NSCocoaErrorDomain Code=4097 "connection to service named com.***.***" UserInfo={NSDebugDescription=connection to service named com.***.***}
Sep 19 13:36:16 My-iPhone backboardd(BaseBoard)[659] <Error>: Unable to bootstrap_look_up port with name com.xxxx.Extension.gsEvents: unknown error code (1102)
Sep 19 13:36:17 My-iPhone xxxxExtension(CoreFoundation)[996] <Error>: Couldn't read values in CFPrefsPlistSource<0x1d411a940> (Domain: group.com.xxxx.extension-df, User: kCFPreferencesAnyUser, ByHost: Yes, Container: (null), Contents Need Refresh: Yes): Using kCFPreferencesAnyUser with a container is only allowed for System Containers, detaching from cfprefsd
I have tried just about everything on https://chocolatey.org/install
Here is the error I get using the method most strongly recommended:
Per their instructions, I used PowerShell to
'Set-ExecutionPolicy AllSigned'
I have also tried performing the install from PowerShell
with the following result:
I have also tried the "completely offline install" which involves manually downloading and extracting a nupkg file, but with similar results as the above. Do you have any insight into the errors I'm receiving? What should I do to get chocolatey installed?
Thank you in advance for any ideas you might have.
UPDATE: Click Here for the chocolatey log file. Snippet below to satisfy SO requirement:
2017-04-26 11:47:33,091 [DEBUG] - Configuration:
CommandName='install'|
CacheLocation='C:\Users\PARAGON\AppData\Local\Temp\chocolatey'|
ContainsLegacyPackageInstalls='True'|
CommandExecutionTimeoutSeconds='2700'|WebRequestTimeoutSeconds='30'|
Sources='https://chocolatey.org/api/v2/'|SourceType='normal'|
Debug='False'|Verbose='False'|Trace='False'|Force='False'|Noop='False'|
HelpRequested='False'|UnsuccessfulParsing='False'|RegularOutput='True'|
QuietOutput='False'|PromptForConfirmation='True'|AcceptLicense='False'|
AllowUnofficialBuild='False'|Input='choco'|AllVersions='False'|
SkipPackageInstallProvider='False'|PackageNames='choco'|
Prerelease='False'|ForceX86='False'|OverrideArguments='False'|
NotSilent='False'|ApplyPackageParametersToDependencies='False'|
ApplyInstallArgumentsToDependencies='False'|IgnoreDependencies='False'|
AllowMultipleVersions='False'|AllowDowngrade='False'|
ForceDependencies='False'|Information.PlatformType='Windows'|
Information.PlatformVersion='6.2.9200.0'|
Information.PlatformName='Windows 8'|
Information.ChocolateyVersion='0.10.5.0'|
Information.ChocolateyProductVersion='0.10.5'|
Information.FullName='choco, Version=0.10.5.0, Culture=neutral,
PublicKeyToken=79d02ea9cad655eb'|
Information.Is64BitOperatingSystem='True'|
Information.Is64BitProcess='True'|Information.IsInteractive='True'|
Information.IsUserAdministrator='True'|
Information.IsProcessElevated='True'|
Information.IsLicensedVersion='False'|Information.LicenseType='Foss'|
Features.AutoUninstaller='True'|Features.ChecksumFiles='True'|
Features.AllowEmptyChecksums='False'|
Features.AllowEmptyChecksumsSecure='True'|
Features.FailOnAutoUninstaller='False'|
Features.FailOnStandardError='False'|Features.UsePowerShellHost='True'|
Features.LogEnvironmentValues='False'|Features.VirusCheck='False'|
Features.FailOnInvalidOrMissingLicense='False'|
Features.IgnoreInvalidOptionsSwitches='True'|
Features.UsePackageExitCodes='True'|
Features.UseFipsCompliantChecksums='False'|
Features.ShowNonElevatedWarnings='True'|
Features.ShowDownloadProgress='True'|
Features.StopOnFirstPackageFailure='False'|
Features.UseRememberedArgumentsForUpgrades='False'|
Features.ScriptsCheckLastExitCode='False'|
ListCommand.LocalOnly='False'|
ListCommand.IncludeRegistryPrograms='False'|ListCommand.PageSize='25'|
ListCommand.Exact='False'|ListCommand.ByIdOnly='False'|
ListCommand.IdStartsWith='False'|ListCommand.OrderByPopularity='False'|
ListCommand.ApprovedOnly='False'|
ListCommand.DownloadCacheAvailable='False'|
ListCommand.NotBroken='False'|
ListCommand.IncludeVersionOverrides='False'|
UpgradeCommand.FailOnUnfound='False'|
UpgradeCommand.FailOnNotInstalled='False'|
UpgradeCommand.NotifyOnlyAvailableUpgrades='False'|
UpgradeCommand.ExcludePrerelease='False'|
NewCommand.AutomaticPackage='False'|
NewCommand.UseOriginalTemplate='False'|SourceCommand.Command='unknown'|
SourceCommand.Priority='0'|SourceCommand.BypassProxy='False'|
SourceCommand.AllowSelfService='False'|
FeatureCommand.Command='unknown'|
ConfigCommand.Command='unknown'|PinCommand.Command='unknown'|
Proxy.BypassOnLocal='True'| 2017-04-26 11:47:33,095 [DEBUG] - _
Chocolatey:ChocolateyInstallCommand - Normal Run Mode _ 2017-04-26
11:47:33,102 [INFO ] - Installing the following packages: 2017-04-26
11:47:33,111 [INFO ] - choco 2017-04-26 11:47:33,119 [INFO ] - By
installing you accept licenses for the packages. 2017-04-26
11:47:33,517 [WARN ] - [NuGet] An error occurred while loading
packages from 'https://chocolatey.org/api/v2/': The remote server
returned an error: (403) Forbidden. 2017-04-26 11:47:33,531 [ERROR] -
choco not installed. The package was not found with the source(s)
listed. If you specified a particular version and are receiving this
message, it is possible that the package name exists but the version
does not. Version: "" Source(s): "https://chocolatey.org/api/v2/"
2017-04-26 11:47:33,558 [WARN ] - Chocolatey installed 0/1 packages.
1 packages failed. See the log for details
(C:\ProgramData\chocolatey\logs\chocolatey.log). 2017-04-26
11:47:33,569 [INFO ] - 2017-04-26 11:47:33,577 [ERROR] - Failures
2017-04-26 11:47:33,586 [ERROR] - - choco - choco not installed. The
package was not found with the source(s) listed. If you specified a
particular version and are receiving this message, it is possible that
the package name exists but the version does not. Version: ""
Source(s): "https://chocolatey.org/api/v2/" 2017-04-26 11:47:33,596
[WARN ] - Enjoy using Chocolatey? Explore more amazing features to
take your experience to the next level at
https://chocolatey.org/compare 2017-04-26 11:47:33,606 [DEBUG] -
Sending message 'PostRunMessage' out if there are subscribers...
2017-04-26 11:47:33,613 [DEBUG] - Exiting with 1
My guess is that most likely you are running into a SSL/TLS issue. We just switched the certificates out on Monday, and the old certificate expired on Tuesday. My guess is that you need to update your certificates or you have a caching of the old certificate for some reason.
The other possibility is there is a proxy in the way that is stopping you from reaching out.
Don't forget about your chocolatey.config. Appears you got blocked but for anyone visiting this question these are the relevant keys you'll need to fill out. Unless you've been a bad boy and got your IP black listed.
<config>
<add key="cacheLocation" value="" description="Cache location if not TEMP folder." />
<add key="containsLegacyPackageInstalls" value="true" description="Install has packages installed prior to 0.9.9 series." />
<add key="commandExecutionTimeoutSeconds" value="2700" description="Default timeout for command execution. '0' for infinite (starting in 0.10.4)." />
<add key="proxy" value="" description="Explicit proxy location. Available in 0.9.9.9+." />
<add key="proxyUser" value="" description="Optional proxy user. Available in 0.9.9.9+." />
<add key="proxyPassword" value="" description="Optional proxy password. Encrypted. Available in 0.9.9.9+." />
<add key="webRequestTimeoutSeconds" value="30" description="Default timeout for web requests. Available in 0.9.10+." />
<add key="proxyBypassList" value="" description="Optional proxy bypass list. Comma separated. Available in 0.10.4+." />
<add key="proxyBypassOnLocal" value="true" description="Bypass proxy for local connections. Available in 0.10.4+." />
I am trying to deploy a composite I created in JDeveloper 12.1.3.0.0 to Weblogic 12.1.3.0.0. When I deploy from JDeveloper I get the following message on deployment.
[01:17:00 PM] Error deploying archive sca_MX_StormCreateUpdatePlantAcctWO_ABCS_req_rev1.0.jar to partition "WorkOrderServices" on server WLS_SOA1 [https://myip:8002]
[01:17:00 PM] HTTP error code returned [500]
[01:17:00 PM] Error message from server:
There was an error deploying the composite on WLS_SOA1: Deployment Failed: Error occurred during deployment of component: MX_StormCreateUpdatePlantAcctWO_ABCS_req to service engine: implementation.bpel, for composite: MX_StormCreateUpdatePlantAcctWO_ABCS_req: ORABPEL-05215
Error while loading process.
The process domain is encountering the following errors while loading the process "MX_StormCreateUpdatePlantAcctWO_ABCS_req" (composite "WorkOrderServices/MX_StormCreateUpdatePlantAcctWO_ABCS_req!1.0*soa_7dc4d4f8-7df0-465a-9d11-e7c1d8cb9c2d"): Validation of BPEL2.0 process failed..
This error contained an exception thrown by the underlying process loader module.
Check the exception trace in the log (with logging level set to debug mode). If there is a patch installed on the server, verify that the bpelcClasspath domain property includes the patch classes.
.
[01:17:00 PM] Check server log for more details.
[01:17:00 PM] Error deploying archive sca_MX_StormCreateUpdatePlantAcctWO_ABCS_req_rev1.0.jar to partition "WorkOrderServices" on server WLS_SOA1 [https://myip:8002]
[01:17:00 PM] Deployment cancelled.
[01:17:00 PM] ---- Deployment incomplete ----.
[01:17:00 PM] Error deploying archive file:/WorkOrder_EBS/MX_StormCreateUpdatePlantAcctWO_ABCS_req/deploy/sca_MX_StormCreateUpdatePlantAcctWO_ABCS_req_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)
This composite compiles fine in JDeveloper. In the WLS_SOA1-diagnostic.log I am seeing these errors.
[2016-06-13T13:16:57.542-05:00] [WLS_SOA1] [ERROR] [] [oracle.soa.bpel.engine.compiler] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: TX12238] [ecid: 921f7c10-6914-4003-96f8-df103a09a69a-0005c140,0] [APP: soa-infra] [DSID: 0000LLAykDqB1FELJ6U4Uf1NMlsk00007u] Validation of BPEL2.0 process failed.
[2016-06-13T13:16:57.542-05:00] [WLS_SOA1] [ERROR] [] [oracle.soa.bpel.engine.compiler] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: TX12238] [ecid: 921f7c10-6914-4003-96f8-df103a09a69a-0005c140,0] [APP: soa-infra] [DSID: 0000LLAykDqB1FELJ6U4Uf1NMlsk00007u] BPEL/MX_StormCreateUpdatePlantAcctWO_ABCS_req.bpel:71 error "element" is set to "ns3:LogEvent" on this <bpel:variable> but it cannot be resolved (check value of "element", imports, WSDLs or XSDs)., Suggested Fix : Make sure that value "ns3:LogEvent" is resolvable (check imports, value of "element").
[2016-06-13T13:16:57.543-05:00] [WLS_SOA1] [ERROR] [] [oracle.soa.bpel.engine.compiler] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: TX12238] [ecid: 921f7c10-6914-4003-96f8-df103a09a69a-0005c140,0] [APP: soa-infra] [DSID: 0000LLAykDqB1FELJ6U4Uf1NMlsk00007u] BPEL/MX_StormCreateUpdatePlantAcctWO_ABCS_req.bpel:81 error Variable "inputVariable" does not have a part named "payload" - check expression segment "$inputVariable.payload"
I have ran into similar ORABPEL-05215 errors before and resolved them by updating my MDS. I updated all the MDS files that this composite references. I have re-created the inputVariable to try to resolve this error message with no luck.
I was able to deploy after removing this file WorkOrderRouter_ep.wsdl and its reference in the composite.xml. After looking in the logs the WLS_SOA1-diagnostic.log had multiple entries for not being able to find XSD files that were not necessary to this composite. Turns out this WSDL was referencing them.
I have installed the TeamCity build agent on my machine a few different ways- using Java Web Start and the manual .zip distribution. Both result in viable installations, as I have once or twice been able to connect and register properly with the TeamCity server. However, upon restarting (<install_location>/bin/agent.sh stop...<install_location>/bin/agent.sh start) I get the following error in teamcity-agent.log (with extra debugging turned on in the log4j config file).
[2013-04-03 09:05:09,870] DEBUG - jetbrains.buildServer.XMLRPC - faultStringjava.lang.RuntimeException: org.jdom.input.JDOMParseException: Error on line 28: XML document structures must start and end within the same entity.faultCode0
[2013-04-03 09:05:09,878] DEBUG - buildServer.AGENT.registration - jetbrains.buildServer.xmlrpc.RemoteCallException: Call http://teamcityserver:8080/RPC2 buildServer.registerAgent3: org.apache.xmlrpc.XmlRpcException: java.lang.RuntimeException: org.jdom.input.JDOMParseException: Error on line 28: XML document structures must start and end within the same entity.
jetbrains.buildServer.xmlrpc.RemoteCallException: Call http://teamcityserver:8080/RPC2 buildServer.registerAgent3: org.apache.xmlrpc.XmlRpcException: java.lang.RuntimeException: org.jdom.input.JDOMParseException: Error on line 28: XML document structures must start and end within the same entity.
at jetbrains.buildServer.xmlrpc.AbstractXmlRpcTarget.call(AbstractXmlRpcTarget.java:94)
at jetbrains.buildServer.agent.impl.ServerXmlRpcProxy.registerAgent3(ServerXmlRpcProxy.java:62)
at jetbrains.buildServer.agent.impl.BuildAgentImpl.doRegisterOnBuildServer(BuildAgentImpl.java:776)
at jetbrains.buildServer.agent.impl.BuildAgentImpl.registerOnBuildServer(BuildAgentImpl.java:748)
at jetbrains.buildServer.agent.impl.ServerMonitor.run(ServerMonitor.java:71)
Caused by: org.apache.xmlrpc.XmlRpcException: java.lang.RuntimeException: org.jdom.input.JDOMParseException: Error on line 28: XML document structures must start and end within the same entity.
at org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcClientResponseProcessor.java:104)
at org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClientResponseProcessor.java:71)
at org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
at org.apache.xmlrpc.TCXmlRpcClient$1.execute(TCXmlRpcClient.java:89)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
at jetbrains.buildServer.xmlrpc.impl.CommonsXmlRpcTargetImpl$1.execute(CommonsXmlRpcTargetImpl.java:72)
at jetbrains.buildServer.xmlrpc.AbstractXmlRpcTarget.call(AbstractXmlRpcTarget.java:84)
... 4 more
[2013-04-03 09:05:09,878] WARN - buildServer.AGENT.registration - Call http://teamcityserver:8080/RPC2 buildServer.registerAgent3: org.apache.xmlrpc.XmlRpcException: java.lang.RuntimeException: org.jdom.input.JDOMParseException: Error on line 28: XML document structures must start and end within the same entity.
[2013-04-03 09:05:09,878] WARN - buildServer.AGENT.registration - Connection to TeamCity server is probably lost. Will be trying to restore it. Take a look at logs/teamcity-agent.log for details (unless you're using custom logging).
This is the xml in question according to the logs with extra xmlrpc debugging:
<?xml version="1.0"?><methodCall><methodName>buildServer.registerAgent3</methodName><params><param><value><![CDATA[<?xml version="1.0" encoding="UTF-8"?>
<agentDetails agentName="aaronhbox_0" agentPort="9090" authToken="" osName="Linux, version 3.5.0-17-generic">
<alternativeAddresses>
<address>10.2.1.232</address>
<address>192.168.225.1</address>
<address>192.168.80.1</address>
</alternativeAddresses>
<availableRunners>
<runner runType="Ant" />
<runner runType="Duplicator" />
<runner runType="gradle-runner" />
<runner runType="Inspection" />
<runner runType="Ipr" />
<runner runType="JPS" />
<runner runType="Maven2" />
<runner runType="rake-runner" />
<runner runType="simpleRunner" />
</availableRunners>
<availableVcs>
<vcs name="perforce" />
<vcs name="mercurial" />
<vcs name="jetbrains.git" />
<vcs name="svn" />
<vcs name="cvs" />
</availableVcs>
<buildParameters>
<param name="env.COLORTERM" value="gnome-terminal" />
<param name="env.COMP_WORDBREAKS"><![CDATA["'><;|]]></value></param></params></methodCall>
Only once have I been able to restart the agent and have it connect again properly. Generally, I can install it, have it run once, then restarting it gives this error. Any ideas?
It looks like the formatting of the COMP_WORDBREAKS environment variable was messing with the xml structure and not allowing the complete generation of the xml request message.
The COMP_WORDBREAKS value on my machine is "'><;|&(:.
Placing the following line in the buildAgent.properties file fixed this problem and allows the agent to properly register.
env.COMP_WORDBREAKS=
I don't see any side-effects yet of making this change; the agent now seems to behave properly.
I'm building a WiX bundle. I need to chain an executable package (actually ASCOM Platform 6 SP1). The detection condition is that a certain registry key exists, and contains a version number greater than a certain minimum required version. If those conditions are not met, then the prerequisite is not met and the EXE file package needs to be downloaded and installed.
The fragment I've authored looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<?include $(sys.CURRENTDIR)\Config.wxi?>
<!-- Define a prerequisite for ASCOM Platform 6 SP1 -->
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension">
<Fragment>
<util:RegistrySearch Id="FindAscom6Installed"
Variable="AscomPlatform6Installed"
Root="HKLM"
Key="SOFTWARE\ASCOM\Platform"
Value="Platform Build"
Result="exists"
Win64="$(var.Win64)"
/>
<util:RegistrySearch Id="FindAscom6Build"
Variable="AscomPlatformBuild"
Root="HKLM"
Key="SOFTWARE\ASCOM\Platform"
Value="Platform Build"
Result="value"
Win64="$(var.Win64)"
/>
<PackageGroup Id="AscomPlatform6Sp1">
<!-- If necessary, install ASCOM Platform version 6, do not uninstall
it during driver uninstall. -->
<!-- DetectCondition="AscomPlatformInstalled AND AscomPlatformBuild >= 6.0.10028.2207" -->
<ExePackage
SourceFile="ASCOMPlatform6SP1.exe"
DetectCondition="AscomPlatform6Installed AND AscomPlatformBuild >= 6.0.10028.2207"
DownloadUrl="http://download.ascom-standards.org/ASCOMPlatform6SP1.exe"
PerMachine="yes"
Permanent="yes"
Vital="yes" />
</PackageGroup>
</Fragment>
</Wix>
This compiles OK but when the setup is run, it fails. Here's the log output:
[0E54:141C][2012-12-12T06:37:38]i001: Burn v3.7.1204.0, Windows v6.2 (Build 9200: Service Pack 0), path: C:\Users\Tim\Documents\visual studio 2012\Projects\Wix.BurnTutorial\Wix.BurnTutorial\bin\Debug\Wix.BurnTutorial.exe, cmdline: ''
[0E54:141C][2012-12-12T06:37:38]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\Tim\AppData\Local\Temp\Wix.BurnTutorial_20121212063738.log'
[0E54:141C][2012-12-12T06:37:38]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\Tim\Documents\visual studio 2012\Projects\Wix.BurnTutorial\Wix.BurnTutorial\bin\Debug\Wix.BurnTutorial.exe'
[0E54:141C][2012-12-12T06:37:38]i000: Setting string variable 'WixBundleName' to value 'Wix.BurnTutorial'
[0E54:141C][2012-12-12T06:37:39]i100: Detect begin, 2 packages
[0E54:141C][2012-12-12T06:37:39]i000: Registry key not found. Key = 'SOFTWARE\ASCOM\Platform'
[0E54:141C][2012-12-12T06:37:39]i000: Registry key not found. Key = 'SOFTWARE\ASCOM\Platform'
[0E54:141C][2012-12-12T06:37:39]i000: Setting numeric variable 'AscomPlatform6Installed' to value 0
[0E54:141C][2012-12-12T06:37:39]e000: Error 0x8007000d: Failed to parse condition "AscomPlatform6Installed AND AscomPlatformBuild >= 6.0.10028.2207". Unexpected character at position 51.
[0E54:141C][2012-12-12T06:37:39]e000: Error 0x8007000d: Failed to read next symbol.
[0E54:141C][2012-12-12T06:37:39]e000: Error 0x8007000d: Failed to parse value.
[0E54:141C][2012-12-12T06:37:39]e000: Error 0x8007000d: Failed to parse term.
[0E54:141C][2012-12-12T06:37:39]e000: Error 0x8007000d: Failed to parse boolean-factor.
[0E54:141C][2012-12-12T06:37:39]e000: Error 0x8007000d: Failed to parse boolean-term.
[0E54:141C][2012-12-12T06:37:39]e000: Error 0x8007000d: Failed to parse boolean-term.
[0E54:141C][2012-12-12T06:37:39]e000: Error 0x8007000d: Failed to parse expression.
[0E54:141C][2012-12-12T06:37:39]e051: Error 0. Failed to parse condition AscomPlatform6Installed AND AscomPlatformBuild >= 6.0.10028.2207. Unexpected symbol at position (null)
[0E54:141C][2012-12-12T06:37:39]e000: Error 0x8007000d: Failed to evaluate executable package detect condition.
[0E54:141C][2012-12-12T06:37:39]e151: Detect failed for package: ASCOMPlatform6SP1.exe, error: 0x8007000d
[0E54:141C][2012-12-12T06:37:39]i101: Detected package: ASCOMPlatform6SP1.exe, state: Unknown, cached: None
[0E54:141C][2012-12-12T06:37:39]i101: Detected package: TargetPackage, state: Absent, cached: None
[0E54:141C][2012-12-12T06:37:39]i199: Detect complete, result: 0x8007000d
I suspect the problem might be that, because the key doesn't exist, then AscomPlatform6Build is null, which WiX doesn't like.
How do I correctly construct this detection condition?
You should be able to add a condition to the second RegistrySearch based off the first one. If you assign a base value to the AscomPlatformBuild as well, it won't be reported as null.
<Variable Name="AscomPlatformBuild" Type="numeric" Value="1.0.0" />
...
<util:RegistrySearch Id="FindAscom6Build"
Variable="AscomPlatformBuild"
Root="HKLM"
Key="SOFTWARE\ASCOM\Platform"
Value="Platform Build"
Result="value"
Win64="$(var.Win64)"
Condition="AscomPlatform6Installed" />
The ExePackage can be left alone.
Faced the same issue.
Resolved it by adding v before the version constant in the condition .i.e v6.0.10028.2207
<ExePackage
SourceFile="ASCOMPlatform6SP1.exe"
DetectCondition="AscomPlatform6Installed AND AscomPlatformBuild >= v6.0.10028.2207"
DownloadUrl="http://download.ascom-standards.org/ASCOMPlatform6SP1.exe"
PerMachine="yes"
Permanent="yes"
Vital="yes" />