2

Closed

Unable to install SQL Nexus properly

description

I have downloaded the sqlnexus.2.5.0.3 .zip file. I had extracted all the files into a directory and clicked on SQLnexus.exe file. This action ended up in the following error.
 
PLATFORM VERSION INFO
Windows             : 6.0.6000.0 (Win32NT)
Common Language Runtime     : 2.0.50727.1378
System.Deployment.dll       : 2.0.50727.1378 (REDBITSB2.050727-1300)
mscorwks.dll            : 2.0.50727.1378 (REDBITSB2.050727-1300)
dfdll.dll           : 2.0.50727.1378 (REDBITSB2.050727-1300)
dfshim.dll          : 2.0.50727.1378 (REDBITSB2.050727-1300)
 
SOURCES
Deployment url          : file:///C:/Users/daneshb/Desktop/Perfengicourese/sqlnexus.2.5.0.3/sqlnexus.application
 
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of C:\Users\daneshb\Desktop\Perfengicourese\sqlnexus.2.5.0.3\sqlnexus.application resulted in exception. Following failure messages were detected:
    + Exception reading manifest from file:///C:/Users/daneshb/Desktop/Perfengicourese/sqlnexus.2.5.0.3/sqlnexus.application: the manifest may not be valid or the file could not be opened.
    + Manifest XML signature is not valid.
    + No signature was present in the subject.
 
 
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
 
WARNINGS
There were no warnings during this operation.
 
OPERATION PROGRESS STATUS
* [3/17/2008 4:47:17 PM] : Activation of C:\Users\daneshb\Desktop\Perfengicourese\sqlnexus.2.5.0.3\sqlnexus.application has started.
 
ERROR DETAILS
Following errors were detected during this operation.
* [3/17/2008 4:47:17 PM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
    - Exception reading manifest from file:///C:/Users/daneshb/Desktop/Perfengicourese/sqlnexus.2.5.0.3/sqlnexus.application: the manifest may not be valid or the file could not be opened.
    - Source: System.Deployment
    - Stack trace:
        at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
        at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
        at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
        at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
        at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
    --- Inner Exception ---
    System.Deployment.Application.InvalidDeploymentException (SignatureValidation)
    - Manifest XML signature is not valid.
    - Source: System.Deployment
    - Stack trace:
        at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
        at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
    --- Inner Exception ---
    System.Security.Cryptography.CryptographicException
    - No signature was present in the subject.
 
    - Source: System.Deployment
    - Stack trace:
        at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags verifyFlags)
        at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
 
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
Closed Aug 15, 2008 at 9:34 PM by jackli

comments

krasstouff wrote Mar 31, 2008 at 11:45 AM

I have the same problem, with no log file. Maybe a clue: I saw that I have only one choice for identification for connection, windows one, but here we use SQL server identification.
Thanks
Kristof

jackli wrote Apr 8, 2008 at 2:39 PM

It appears that you must have clicked sqlnexus.application instead of sqlnexus.exe. sqlnexus.application is used for clickonce internally. try to delete sqlnexus.application and then just launch sqlnexus.exe to see what happens

wrote Aug 15, 2008 at 9:34 PM

wrote Feb 21, 2013 at 11:49 PM

wrote May 16, 2013 at 11:18 AM