I have a continuous integration build that used to run fine, but began giving me the following exception:
This exception is from the build agent,
Process each ConfigurationsToRelease
Release the build
Run the Release Management build Process for the current configuration:
Exception:
Exception Message: The directory name is invalid (type Win32Exception)
Exception Stack Trace:
Server stack trace:
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at Microsoft.TeamFoundation.Build.Workflow.Activities.InvokeProcess.ProcessWrapper.Start()
at Microsoft.TeamFoundation.Build.Workflow.Activities.InvokeProcess.InvokeProcessInternal.RunCommand (AsyncState state)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[]
args, Object server, Object[]& outArgs
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg,
IMessageSink replySink)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
at System.Func`2.EndInvoke(IAsyncResult result)
at System.Activities.AsyncCodeActivity`1.System.Activities.IAsyncCodeActivity.FinishExecution
(AsyncCodeActivityContext context, IAsyncResult result)
at
System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)
This is using the default build template and it seemed to have started randomly. The release never actually hits the Release Management and never throws an exception or Roll Back there. It seems to die as it should be hitting Release Management.
I've checked the drop folder and everything is there as it should be. Permissions are still correct. I don't know what folder it's looking for.
Has anyone had any experience with this or any ideas of where to begin looking?
Install the RM Client on the build server.
Somehow, the RM Client had gotten removed from the build server in between releases. Going to have a talk with IT about that.
Thank you #Daniel Mann for catching that.
Update:
After upgrading to Release Management 2015, I received the same error. The ReleaseTfvcTemplate.12.xaml was updated. Make sure to copy the new template to your BuildProcessTemplates (or update your custom templates) from "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Release Management\Client\bin"
After upgrading to RM 2015 I had to update my build templates as described in the comment above by abest.
The only changes are the version number in the registry paths.
Related
I am trying to execute the package and every time I see the following error. Especially when I execute the data flow task.
Error :
System.IO.IOException: The process cannot access the file
'C:\PPE_OVERRIDES.ispac' because it is being used by another process.
Full Output:
------ Build started: Project: PPE_OVERRIDES, Configuration: Development ------
Build started: SQL Server Integration Services project: Incremental ...
Starting project consistency check ...
Project consistency check completed. The project is consistent.
Error : System.IO.IOException: The process cannot access the file
'C:\PPE_OVERRIDES.ispac' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalDelete(String path, Boolean checkHost)
at System.IO.File.Delete(String path)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.IncrementalBuildThroughObj(IOutputWindow outputWindow)
at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.BuildIncremental(IOutputWindow outputWindow)
Build complete -- 1 errors, 0 warnings
========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========
How can I fix it. My ispac file is in bin folder. I want to make sure the SsISDB catalog and Visual Studio are not fighting over this location
Based on the following article:
Fix SSIS Error while execution: System.IO.IOException: The process cannot access the file ‘PATH\Project.ispac’ because it is being used by another process.
Possible Solution:
Need to kill the Windows processes (SSIS Debug Host, and SSIS Debug Host (32 bit)) related to SSIS Debug and restart Visaul Studio to address the problem.
Similar Issue links
The process cannot access the file 'ssisproject.ispac' because it is being used by another process.
SSIS: The process cannot access the file ‘*.ispac’ because it is being used by another process
SIS: The process cannot access the file ‘*.ispac’ because it is being used by another process
Every time you start up an instance of SQL Server Manager, you have to go kill the SSIS Debug Host processes. However, I don't think they showed up until I tried to re-execute a package. I might try executing an empty, dummy package, fix the crash, then try again with the real package.
I have created a WPF application in VS 2017 that installs with ClickOnce. After deploying the solution to a network location, I am able to install on my 64-bit Windows 10 computer by visiting the .application link.
However, the application does not run on my machine after it is installed. When I attempt to use the .appref-ms shortcut from the Start menu, nothing happens. I have added code to launch a debugger when the application starts, but it doesn't get hit. I see nothing getting logged in the clickonce log when running the application from here. I have set the logging to Verbose in the registry.
If I attempt to run the application from the %userprofile%\AppData\Local\Apps\2.0\ install location, it runs fine and launches the debugger. However, I can't use this location because it will then use the config file from this location rather than the config stored in %userprofile%\AppData\Local\, which allows new versions to continue using the same configuration. It's also inconvenient for users.
If I go back to the .application link on the server, I am able to install new versions when they are deployed, but it still does not launch the application or log any issues with running the application.
The .appref-ms looks like this, and Launcher.manifest does exist in the install location, along with the file listed in the manifest:
file://192.168.10.11/Projects/Launcher.application#Launcher.application, Culture=neutral, PublicKeyToken=0000000000000000, processorArchitecture=msil
How do I track down the problem with my ClickOnce shortcut?
Edit: Someone mentioned looking in the Event Viewer, and I found a SecurityException, which only occurs when running from the shortcut. Debugger.Launch() is the first line in the MainWindow Constructor on the partial class, but it is not getting hit. Here is the exception from Event Viewer:
Application: applaunch.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Security.SecurityException
at System.Security.CodeAccessSecurityEngine.Check(System.Object, System.Threading.StackCrawlMark ByRef, Boolean)
at System.Security.CodeAccessPermission.Demand()
at MS.Internal.SecurityHelper.DemandUnmanagedCode()
at System.Windows.Window..ctor()
at Launcher.MainWindow..ctor()
This helps in my case (had the same problem):
Project -> Properties
Security: Change from partial trust to full trust
Changes marked yellow:
I am deploying an WPF application in business environment (AD) using clickonce deployment. The application is develop with Visual Studio 2013 and based on .Net 4.5. The deployment targets Windows 7 machines only. The deployment Server uses IIS 7.5 and runs on Windows Server 2008 R2.
The deployment is configured that the applications checks for updates before the applications starts.
The deployment works at least the most of the time but I recently experiencing random issues on a few machines while installing an application update.
The user receives the following error message:
Application cannot be started. Contact the application publisher.
Cannot start the application. Contact the application vendor for assistance.
this error is document in MSDN, Troubleshooting Specific Errors in ClickOnce Deployments
These are generic error messages that occur when the application
cannot be started, and no other specific reason can be found.
I managed to gather a log file which covers this error:
PLATFORM VERSION INFO
Windows : 6.1.7601.65536 (Win32NT)
Common Language Runtime : 4.0.30319.18444
System.Deployment.dll : 4.0.30319.18408 built by: FX451RTMGREL
clr.dll : 4.0.30319.18444 built by: FX451RTMGDR
dfdll.dll : 4.0.30319.18408 built by: FX451RTMGREL
dfshim.dll : 4.0.41209.0 (Main.041209-0000)
SOURCES
Deployment url: file:///C:/Users/ADUSERNAME/AppData/Roaming/Microsoft/Windows/Start%20Menu/Programs/Supply%20Chain%20Services%20-%20Systems%20and%20Processes/APPLICATIONNAME/APPLICATIONNAME%20Suite.appref-ms%7C
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Deployment Provider url: http://SERVERNAME:PORT/APPLICATIONNAME.application
Application url: http://SERVERNAME:PORT/Application%20Files/APPLICATIONNAME_1_0_3_9/APPLICATIONNAME.exe.manifest
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
IDENTITIES
Application Identity: APPLICATIONNAME.exe, Version=1.0.3.9, Culture=neutral, PublicKeyToken=XXXXXXXXXXXXXXXX, processorArchitecture=msil, type=win32
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of C:\Users\ADUSERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Supply Chain Services - Systems and Processes\APPLICATIONNAME\APPLICATIONNAME Suite.appref-ms| resulted in exception. Following failure messages were detected:
+ A device attached to the system is not functioning. (Exception from HRESULT: 0x8007001F)
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [08/09/2014 09:25:02] : Activation of C:\Users\ADUSERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Supply Chain Services - Systems and Processes\APPLICATIONNAME\APPLICATIONNAME Suite.appref-ms| has started.
* [08/09/2014 09:25:04] : Performing necessary update check as specified by the deployment.
* [08/09/2014 09:25:07] : Consuming new update.
* [08/09/2014 09:25:09] : Installation of the application has started.
* [08/09/2014 09:25:10] : Processing of application manifest has successfully completed.
* [08/09/2014 09:25:10] : Found compatible runtime version 4.0.30319.
* [08/09/2014 09:25:10] : Request of trust and detection of platform is complete.
* [08/09/2014 09:25:18] : Downloading of subscription dependencies is complete.
* [08/09/2014 09:25:18] : Commit of the downloaded application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [08/09/2014 09:25:22] System.Runtime.InteropServices.COMException
- A device attached to the system is not functioning. (Exception from HRESULT: 0x8007001F)
- Source: System.Deployment
- Stack trace:
at System.Deployment.Internal.Isolation.IStore.Transact(IntPtr cOperation, StoreTransactionOperation[] rgOperations, UInt32[] rgDispositions, Int32[] rgResults)
at System.Deployment.Application.ComponentStore.SubmitStoreTransaction(StoreTransactionContext storeTxn, SubscriptionState subState)
at System.Deployment.Application.ComponentStore.CommitApplication(SubscriptionState subState, CommitApplicationParams commitParams)
at System.Deployment.Application.SubscriptionStore.CommitApplication(SubscriptionState& subState, CommitApplicationParams commitParams)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.ConsumeUpdatedDeployment(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentUpdate(SubscriptionState& subState, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ProcessOrFollowShortcut(String shortcutFile, String& errorPageUrl, TempFile& deployFile)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
* Transaction at [08/09/2014 09:25:22]
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: ZJHPL38T.V57.application
+ System.Deployment.Internal.Isolation.StoreOperationSetDeploymentMetadata
- Status: Set
- HRESULT: 0x0
+ System.Deployment.Internal.Isolation.StoreOperationStageComponent
- Status: Installed
- HRESULT: 0x0
- Manifest: APPLICATIONNAME.exe.manifest
+ System.Deployment.Internal.Isolation.StoreOperationStageComponentFile
- Status: Installed
- HRESULT: 0x0
- File: APPLICATIONNAME.exe.config
!!! Removed 550 Lines !!!
+ System.Deployment.Internal.Isolation.StoreOperationInstallDeployment
- Status: Installed
- HRESULT: 0x0
- AppId: http://SERVERNAME:PORT/APPLICATIONNAME.application#APPLICATIONNAME.application, Version=1.0.3.9, Culture=neutral, PublicKeyToken=e5b020d18338a5ca, processorArchitecture=msil
+ System.Deployment.Internal.Isolation.StoreOperationSetDeploymentMetadata
- Status: Set
- HRESULT: 0x0
+ System.Deployment.Internal.Isolation.StoreOperationUninstallDeployment
- Status: Uninstalled
- HRESULT: 0x0
- AppId: http://SERVERNAME:PORT/APPLICATIONNAME.application#APPLICATIONNAME.application, Version=1.0.3.3, Culture=neutral, PublicKeyToken=e5b020d18338a5ca, processorArchitecture=msil
+ System.Deployment.Internal.Isolation.StoreOperationSetDeploymentMetadata
- Status: Set
- HRESULT: 0x0
+ System.Deployment.Internal.Isolation.StoreTransactionOperationType (27)
- HRESULT: 0x8007001f
I also activated detailed logging (using this guide) for my test machine but I was not able to reproduce this error or recognize a pattern which causes the error.
The error affects only 5% to 10% percent of the users, uninstall & reinstall is a workaround but not a solution.
In Reply to Hans Passant:
The | is indeed a strange character, I have neither clue where it comes from nor what it stands for in this context. However the deployment url (including the | symbol) is always the same and it works in 90% of the cases. I don’t think that the | symbol is the cause of the problem. However, I will try to find out why the character is there and come back to you afterwards.
Uninstall/Reinstall solves the problem on client side (Same installer!). Therefore we can exclude a corrupted .Net/VS install.
Anti-malware (McAfee) could be a problem I will investigate as soon I manage to reproduce the error on one of my test machines.
The file path is 123 characters long; the file name has 21 characters. File path + file name = 144 characters
...\APPLICATIONNAME\APPLICATIONNAME Suite.appref-ms|
The .NET Framework normally screams bloody murder when it gets a filename like that. The System.IO.Path.CheckInvalidPathChars() method will throw a "Illegal characters in path" exception, the | character is not valid in a file or directory name. But that check isn't performed in the ClickOnce plumbing, it doesn't use the normal file handling code like the FileStream and Path classes.
That bad filename goes straight to the operating system. What happens next is fairly unguessable, but the file system flipping the bird on it like that is certainly not unexpected.
I have no reasonable guess how this got mangled, this just never goes wrong. A wild guess is that you have one machine around that has a corrupted file in the .NET Framework or VS install, given the frequency of this problem. Might be on the desktop of a particular dev. If the same installer produces a good install when it is run again then the problem is client side. Anti-malware is always suspect. The name is long, you could be a bit beyond MAX_PATH (259 chars) and tripping a buffer overflow bug.
Just wild guesses. But that's the problem. Good luck hunting it down.
This is often happen to my click once deployment when the apps is updating or installing
What i did was run the following
rundll32 %windir%\system32\dfshim.dll CleanOnlineAppCache
to clear the wpf cache and run the url again to install
you can give the user a bat file with the command and ask them to run it when they encountered problem installing/updating
I faced the same issue and the solution I followed is to uninstall the AntiVirus software.
I had an error during an in place upgrade of DNN 7. the error occured during the installation of the new providers from the install/providers folder. SPecifically i think it was during the rad editor provider upgrade.
here is the error:
2013-08-27 17:40:54,149 [WS048][Thread:6][FATAL]
DotNetNuke.Web.Common.Internal.DotNetNukeHttpApplication -
System.Web.HttpUnhandledException (0x80004005): Exception of type
'System.Web.HttpUnhandledException' was thrown. --->
ICSharpCode.SharpZipLib.ZipException: System.ApplicationException:
Unknown block type 7 at
ICSharpCode.SharpZipLib.Zip.Compression.Inflater.Decode() at
ICSharpCode.SharpZipLib.Zip.Compression.Inflater.Inflate(Byte[] buf,
System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step,
Boolean& completedSynchronously) 2013-08-27 17:42:59,589
[WS048][Thread:6][ERROR]
DotNetNuke.Common.Internal.ServicesRoutingManager - Unable to register
service routes System.Reflection.TargetInvocationException: Exception
has been thrown by the target of an invocation. --->
System.BadImageFormatException: Could not load file or assembly
'Newtonsoft.Json, Version=4.5.0.0, Culture=neutral,
PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The
module was expected to contain an assembly manifest.
Server stack trace: at
System.Net.Http.Formatting.JsonMediaTypeFormatter..ctor() at
System.Net.Http.Formatting.MediaTypeFormatterCollection.CreateDefaultFormatters()
at System.Web.Http.HttpConfiguration..ctor(HttpRouteCollection routes)
at System.Web.Http.GlobalConfiguration.<.cctor>b__0() at
System.Lazy`1.CreateValue()
This makes me think it was a blocked zip file, but I double checked to make sure the zip file was unblocked
Question: Does someone know where this error comes from? Or how can I figure out more specifically where it is comming from
thanks
EDIT #1
So I restored from a backup and tried again, I got the same error but at a different install/provider zip file. I am not sure what is causing this. This error seems to indicate the zip files are corrupted and are not downloaded/uploaded correctly.
EDIT #2
is there a chance that my ftp client is corrupting the zip files during upload? This has been going on for three days with well over a dozen different attempts to upgrade to various versions. I've never had this difficulty with a dnn upgrade ever and I've been using it for years.
It is definitely possible that you're getting corruption issues somewhere.
I would start by downloading the UPGRADE package again, extracting them using 7zip instead of Windows Compression, then try the upload. Maybe try a new FTP client, or see if you can RDP into the machine instead of FTP
When I try to run a GWT App Engine project using the Eclipse plugin, I get the following error:
Initializing App Engine server
[ERROR] Unable to start App Engine server
java.lang.RuntimeException: Unable to restore the previous TimeZone
at com.google.appengine.tools.development.DevAppServerImpl.restoreLocalTimeZone(DevAppServerImpl.java:228)
at com.google.appengine.tools.development.DevAppServerImpl.start(DevAppServerImpl.java:164)
at com.google.appengine.tools.development.gwt.AppEngineLauncher.start(AppEngineLauncher.java:97)
at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:509)
at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1068)
at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:811)
at com.google.gwt.dev.DevMode.main(DevMode.java:311)
Caused by: java.lang.NoSuchFieldException: defaultZoneTL
at java.lang.Class.getDeclaredField(Class.java:1899)
at com.google.appengine.tools.development.DevAppServerImpl.restoreLocalTimeZone(DevAppServerImpl.java:222)
... 6 more
[ERROR] shell failed in doStartupServer method
Unable to start embedded HTTP server
com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries)
at com.google.appengine.tools.development.gwt.AppEngineLauncher.start(AppEngineLauncher.java:102)
at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:509)
at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1068)
at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:811)
at com.google.gwt.dev.DevMode.main(DevMode.java:311)
Chris Cashwell provided the correct answer. But for people like myself who are relatively new to Eclipse, here are more explicit instructions (which I came across here):
Right-click project directory in Project Explorer window
Select Run As > Run Configurations...
Go to Arguments tab
In VM Arguments textbox, add one of the following parameters mentioned by Chris:
-Dappengine.user.timezone.impl=UTC (this worked in my case)
-Dappengine.user.timezone=UTC
Click Apply then Run
In my case, this was done specifically in the context of a PlayN project I am working on, so I was right-clicking the HTML folder. In the end, my VM arguments looked something like this:
-Xmx512m -javaagent:/long/path/to/appengine-agent.jar -Dappengine.user.timezone.impl=UTC
See this bug report. For me, it was fixed by downgrading the JDK from 1.7.0_03 -> 1.7.0_02. Other things that have been purported to work are adding -Dappengine.user.timezone=UTC (or in some cases -Dappengine.user.timezone.impl=UTC) to the JVM flags.
i got this error, and found port already in use in the console.
I closed eclipse and killed javaw.exe. Then everything worked fine.