I´m using BTDF v5.7 to deploy a BizTalk solution to BizTalk Server 2016. When deploying to our DEV environment (only one server) all goes well, but when we try to deploy to INT (two servers) it breaks on the second server (the one which have the "last server" flag set to true).
Checking logs I found this:
Target BounceAllBizTalkHosts:
Host list (BizTalkHosts ItemGroup) not customized.
Host instance ClusterdHost has cluster type Clustered.
Querying localhost to request active cluster node...
C:\Program Files (x86)\...\BizTalkDeploymentFramework.targets(1234,5): error : Invalid namespace
C:\Program Files (x86)\...\BizTalkDeploymentFramework.targets(1234,5): error : at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
C:\Program Files (x86)\...\BizTalkDeploymentFramework.targets(1234,5): error : at System.Management.ManagementScope.InitializeGuts(Object o)
C:\Program Files (x86)\...\BizTalkDeploymentFramework.targets(1234,5): error : at System.Management.ManagementScope.Initialize()
C:\Program Files (x86)\...\BizTalkDeploymentFramework.targets(1234,5): error : at System.Management.ManagementObjectSearcher.Initialize()
C:\Program Files (x86)\...\BizTalkDeploymentFramework.targets(1234,5): error : at System.Management.ManagementObjectSearcher.Get()
C:\Program Files (x86)\...\BizTalkDeploymentFramework.targets(1234,5): error : at DeploymentFramework.BuildTasks.ControlBizTalkHostInstance.GetActiveClusterNodeName()
C:\Program Files (x86)\...\BizTalkDeploymentFramework.targets(1234,5): error : at DeploymentFramework.BuildTasks.ControlBizTalkHostInstance.ControlHostInstances(String query)
C:\Program Files (x86)\...\BizTalkDeploymentFramework.targets(1234,5): error : at DeploymentFramework.BuildTasks.ControlBizTalkHostInstance.Execute()
Done building target "BounceAllBizTalkHosts" in project "Deployment.btdfproj" -- FAILED.
I did a small research on the BTDF sources and it seems that GetActiveClusterNodeName() method is trying to access to the MSCluster namespace through WMI. Apparently it breaks because it`s not able to find it (it makes sense since servers are not configured as a MS FailOver Cluster).
Any idea about why BTDF is detecting this node as a clustered one?
PS: If we force servers to not restart, adding:
<TargetName="BounceBizTalk"DependsOnTargets="SetWinVer"/>
to .btdfprj, the issue doesn't happen. But we need to do a restart after deployment to apply changes :(
Related
I have an asp.net webform project that build on system1 but not on system2 (they both are windows 10 and visual studio 2022 Version 17.4.3) and when I build visual studio show an error in error list window :
"Severity Code Description Project File Line Suppression State
Error Metadata failure while creating assembly -- The file or directory is corrupted and unreadable. Modabber D:\BehsamanCode\Modabber\Modabber.Web\ALINK"
Also it shows this error in the output window :
"ALINK : error AL1019: Metadata failure while creating assembly -- The file or directory is corrupted and unreadable"
I searched these errors and I enabled long path on windows10 and uncheck Sign the assembly but not work.
What should we do?
I don't know how but it resolved. I think system2 hard drive has a problem and after win10 repair it itself then restart windows the problem gone and project builded.
I just change the datasource of my form, when I tried to save the form the client crashed.
Ever since the client crashed every time i tried to start it up
Does anyone else have this problem? Or does anyone have an explanation or solution?
Error log:
Name of the corrupted application: Ax32.exe, version: 6.3.6000.10707, timestamp: 0x5fd6ef55
Name of the corrupted module: Ax32.exe, version: 6.3.6000.10707, timestamp: 0x5fd6ef55
Exception Code: 0xc00000fd
Error offset: 0x0001dbe0
ID of the faulty process: 0x4a1c
Start time of the faulty application: 0x01d7f183a25b6a92
Path of the faulty application: C:\Program Files (x86)\Microsoft Dynamics
AX\60\Client\Bin\Ax32.exe
Path of the corrupted module: C:\Program Files (x86)\Microsoft Dynamics
AX\60\Client\Bin\Ax32.exe
Berichtskennung: dfd93a82-3ef5-43f0-92a3-e893babff96e
Full name of the corrupted package:
Application ID relative to the corrupted package:
With the client closed, go to C:\Users\username\AppData\Local (aka %localappdata%), and delete all of the *.auc and *.kti files. Then go to C:\Users\username\AppData\Local\Microsoft\Dynamics Ax and delete everything in that folder.
Then try and reopen the AX client. If that doesn't work, try another AX client on a different machine. If that does work, then reinstall your AX client. If that doesn't work, you have another issue.
I am pretty new to the .net and I had this error while trying to publish my website to file system.
Error: A '-dest' argument must be specified with the 'sync' verb. This error is shown when I try to publish in the default detination
Copying to output path C:\Users\Iulica'sPc\AppData\Local\Temp\PublishTemp\GpsTracking103
Multiple commands defined. Defaulting to web.
Using command 'web' as the entry point for web.config.
Time elapsed 00:02:45.9471627
Publishing with publish method [FileSystem]
Publishing files to C:\Users\Iulica'sPc\Documents\Visual Studio 2015\Projects\GpsTracking\artifacts\bin\GpsTracking\Release\PublishOutput
Executing command ["C:\Program Files (x86)\IIS\Microsoft Web Deploy V3\msdeploy.exe" -source:contentPath='C:\Users\Iulica'sPc\AppData\Local\Temp\PublishTemp\GpsTracking103\' -dest:contentPath='C:\Users\Iulica'sPc\Documents\Visual Studio 2015\Projects\GpsTracking\artifacts\bin\GpsTracking\Release\PublishOutput' -verb:sync -enableRule:DoNotDeleteRule -retryAttempts:2 -disablerule:BackupRule]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.DNX.Publishing.targets(386,5): Error : Error: A '-dest' argument must be specified with the 'sync' verb.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.DNX.Publishing.targets(386,5): Error : Error count: 1.
I have searched for hours for an answer but nothing solved my problem.
Please help!
I think it's because there is an ' in your path name (or your username actually):
["C:\Program Files (x86)\IIS\Microsoft Web Deploy V3\msdeploy.exe" -source:contentPath='C:\Users\Iulica'sPc\AppData\Local\Temp\PublishTemp\GpsTracking103\' -dest:contentPath='C:\Users\Iulica'sPc\Documents\Visual Studio 2015\Projects\GpsTracking\artifacts\bin\GpsTracking\Release\PublishOutput' -verb:sync -enableRule:DoNotDeleteRule -retryAttempts:2 -disablerule:BackupRule]
Try deploying to a different folder like c:\projects\ ad also the source path could be the issue.
Check the Important things to remember here: https://technet.microsoft.com/en-us/library/dd569005(v=ws.10).aspx
In order for the sync operation to function correctly, the Msdeploy.exe.configsettings file must be the same on the source and destination computers. If you add any rules or custom providers to the Msdeploy.exe.configsettings file, make sure that this configuration file is identical on the source and the destination computers before you perform a synchronization.
I'm unable to reliably use ASP.NET web deployment to push updates to my server running on an EC2 instance.
The server is running Windows Server 2012 R2 (fully updated and patched), and it's running the latest version of the Web Deployment Service (3.5, actual version 9.0.176.0). I'm trying under both Visual Studio 2013 and Visual Studio 2015, and try connecting directly to the EC2 instance or via the ELB. In all cases, if the deploy takes more than x seconds, it just hangs and then errors out (many) minutes later.
If the deploy consists of many small files, each subsequent attempt to deploy will upload another handful of files before hanging, like this:
2>Start Web Deploy Publish the Application/package to http://52.8.131.99/MSDEPLOYAGENTSERVICE ...
2>Adding ACL's for path (NeoSmart)
2>Adding ACL's for path (NeoSmart)
2>Updating file (NeoSmart\bin\RestSharp.dll).
2>Updating file (NeoSmart\bin\secure\secrets.release.bin).
2>Updating file (NeoSmart\bin\secure\secrets.sandbox.bin).
2>Updating file (NeoSmart\bin\System.Net.Http.Formatting.dll).
2>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4270,5): Warning : Retrying the sync because a socket error (10054) occurred.
2>Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 1 of 10.
2>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4270,5): Warning : Retrying the sync because a socket error (10054) occurred.
2>Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 2 of 10.
After abort, restart of VS, and retry, it continues where it left off only to hang again:
2>Start Web Deploy Publish the Application/package to http://52.8.131.99/MSDEPLOYAGENTSERVICE ...
2>Adding ACL's for path (NeoSmart)
2>Adding ACL's for path (NeoSmart)
2>Updating file (NeoSmart\bin\System.Net.Http.Formatting.dll).
2>Updating file (NeoSmart\bin\System.Web.Helpers.dll).
2>Updating file (NeoSmart\bin\System.Web.Http.Common.dll).
2>Updating file (NeoSmart\bin\System.Web.Http.dll).
2>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4270,5): Warning : Retrying the sync because a socket error (10054) occurred.
2>Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 1 of 10.
If the file it hangs on is too big to go through (for example, the latest version of the AWS SDK, weighing in at 6.3MiB), subsequent restarts won't help any - it hangs on the same file repeatedly:
2>Start Web Deploy Publish the Application/package to http://52.8.131.99/MSDEPLOYAGENTSERVICE ...
2>Adding ACL's for path (NeoSmart)
2>Adding ACL's for path (NeoSmart)
2>Updating file (NeoSmart\bin\System.Web.Http.dll).
2>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Web\Microsoft.Web.Publishing.targets(4270,5): Warning : Retrying the sync because a socket error (10054) occurred.
2>Retrying operation 'Serialization' on object sitemanifest (sourcePath). Attempt 1 of 10.
Deploying to a new EC2 instance takes care of the problem; only a day later I have the same issue and I need to deploy a new Server 2012 instance and deploy all over again. No way, no how.
To me, it looks like the connection is being dropped without acknowledgement somewhere along the line. I'm not sure how/why since I've tried deploying directly to the EC2 instance's public IP and to the ELB. I've tried with w3svc stopped and started, in case it was contention over the target files that was causing the issue, but to no avail. It's probably not on my end because creating a new EC2 instance and deploying from the same machine I'm on works without a problem.
Any idea how I can find out what's causing this? Nothing shows up in the event viewer. Is there a better alternative to the Web Deployment Service for pushing updates to ASP.NET websites on IIS?
Any insight would be most appreciated.
I get the following error when running NetSim v7.1 (from www.tetcos.com) via its command line interface. The input given is -
C:\Program Files\NetSim Standard\bin>NetSimCore.exe -apppath
C:\Program Files\NetSim Standard\bin -iopath
C:\Users\Sachin Kumar\AppData\Local\Temp\NetSim -license 5053#192.168.0.185
I/O warning:
failed to Load external entity C:\Users\Sachin "file:///C:\Users\Sachin/Configuration.xml"
I checked and the configuration file is present in the temp path (%temp%\NetSim)
Can someone please help?
Since the I/O path has white space, you should have it within double quotes. The correct way would be
C:\Program Files\NetSim Standard\bin>NetSimCore.exe -apppath ^
C:\Program Files\NetSim Standard\bin -iopath ^
"C:\Users\Sachin Kumar\AppData\Local\Temp\NetSim" -license 5053#192.168.0.185