Something went wrong with my BizTalk applications; I am unable to delete them and at the same time unable to deploy the latest from Visual Studio. I am working with BizTalk 2009.
The error being displayed on Visual Studio:
A referenced BizTalk project is being in use by other process and thus is unable to update it
My host instance and the application are in stopped state. I tried deleting the dll s from GAC, but no use.
Have you checked that you don't have any suspended instances associated with any of the orchestrations, ports and schemas the app had?
Related
As the title says: every time I deploy from Visual Studio to BizTalk 2013 R2 the orchestration gets unbounded and unenlisted. The receive/send port looses its pipeline.
I have tried to clean cached bindings on C:\Users\<your_user>\AppData\Roaming\Microsoft\BizTalk Server\Deployment\BindingFiles and do a redeployment on everything, but no success.
Any ideas on how to solve this?
Export the bindings before the deployment and re-import them after the deployment.
Another option is to install BizTalk Deployment Framework which has an option to Quick Deploy, that just simply re-GACs the DLLs, useful for when making small changes to existing objects that don't need to update the BizTalk DB
In a project I have tried to install Application Insights, but that failed with an error message and installation of it stopped. I don't remember the exact errormessage, but it was something like "Namespace/_defaultaApplidation was not found" It was not clear to me what it meant.
'
After that the App (Windows 8.1 StoreApp) would not start anymore. Message (and I can repeat that!) sounds: "Unable to activate Windows Store app". This will not go away.
I have uninstalled Aplication Insights via 'Tools | Extensions ad updates' and removed every trace of Application Insights via Nuget Package Manager. I have rebooted my system between every step.
It has come to a situation where now not a single Store App will start. Even if I start with a new Empty App template, the App comes with the same dreaded error message. I have deleted Bin and Obj folders, built, rebuilt and that ends successfully. But the App won't start....
What do I do now?
Grtz
This is a difficult problem to diagnose. Uninstallation of the ApplicationInsights NuGet package, and removal of the ApplicationInsights.config file should remove all changes. And I'm not sure how the AppInsights packages could be impacting other new projects.
It perhaps sounds like you have a broken Visual Studio environment. Trying to reset or repair your Visual Studio environment would be my recommendation.
I've been trying to install the new Microsoft Release Management app that has just been released to MSDN and am having issues
It consists of a server side component for TFS 2013, and a client side component for VS2013
The server side component runs through and says that it is installed fine, but then i can't seem to connect the client side part up to it
After a bit of investigation it seems that the web services site that is installed on the server side is not working properly
It is installed on a Windows 2012 box that is also running TFS 2013, SQL 2012, and SharePoint 2013
If i browse to the newly created ReleaseManagement website I get a 503 (Service Unavailable) message.
I checked out IIS and the app pool had stopped
in the application event log I could see a load of messages saying "current configuration only supports loading images for x86 processor architectures"
I thought this was possibly to do with the "Enable 32-bit Applications" option in the IIS app pool (was set to FALSE)
I changed that to true and tried the site again. This time the app pool doesn't crash, but I get ASP.NET errors stating "Could not load file or assembly 'Interop.ActiveDs' or one of its dependencies. An attempt was made to load a program with an incorrect format."
Has anyone managed to install this yet? Any ideas on what's going wrong here?
I know it's very new, but I'm struggling to find much information about the product at all
Thanks a lot
Here is a link towards some documentation regarding this problem. As pointed out in the comments, it is related to a bug caused by SharePoint: http://support.inreleasesoftware.com/entries/24794668
Interesting section:
The request failed with HTTP status 503: Service Unavailable.
This error message usually means that the InReleaseAppPool application
pool is stopped. Please ensure that it is started. If the application
pool stops after some time by itself, it might be due to a bug caused
by SharePoint 2013. Validate your problem by looking at the Event
Viewer. Confirm that your error is similar to the following:
Event Log Error Event ID 2282
The Module DLL 'C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\15\isapi\spnativerequestmodule.dll' could not be
loaded due to a configuration problem. The current configuration only
supports loading images built for a x86 processor architecture. The
data field contains the error number. To learn more about this issue,
including how to troubleshooting this kind of processor architecture
mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.
We can apply a quick fix using this command
appcmd.exe set config -section:system.webServer/globalModules
/[name='SPNativeRequestModule'].preCondition:integratedMode,bitness64
Or you can manually enter the preCondition entry in the
ApplicationHost.config file
More information can be found here:
http://blogs.flexnetconsult.co.uk/colinbyrne/2012/11/11/RunningA32bitApplicationAlongsideSharePoint2013Problems.aspx
FIX:
the user which you specified to run the TFS service needs "log on as a service" and "Log on as batch job" permissions. I've set that up via GPO.
This solution worked for me. I execute this command
appcmd.exe set config -section:system.webServer/globalModule/[name='SPNativeRequestModule'].preCondition:integratedMode,bitness64
in C:\Windows\System32\inetsrv and C:\Windows\System64\inetsrv.
I'm getting an Object reference not set to an instance of an object error when trying to publish a ASP.net web application to Windows Azure in Visual Studio 2010. I am able to run this application in IIS, and the Azure emulator, without error.
I've gone through and checked all my references, checked the Azure configuration settings, and the web.config and can't figure out what's going on. I have another application which isn't that different from this one, which has not problem publishing to Azure.
This is coming from Windows Azure Activity Log in Visual Studio. It seems as though it's coming right around the time when it is about to verify the storage account. Maybe it's related to that?
11:08:46 AM - Warning: There are package validation warnings.
11:08:46 AM - Preparing deployment for Repnet - 11/9/2012 11:06:35 AM with Subscription ID '********-****-****-****-************' using Service Management URL 'https://management.core.windows.net/'...
11:08:46 AM - Connecting...
11:08:48 AM - Object reference not set to an instance of an object.
11:08:48 AM - Deployment failed with a fatal error
Check your <connectionStrings>
element in the web.config file. If it has a ''<clear/> element remove it, afterwords publishing should work.
See Link
I'm using biztalk 2009 and trying to deploy via vs.net 2008.
My project is just an empty BizTalk application with an empty orchestration. I've created a strong name key file and selected it in the Project properties under "Signing". I've also specified an application name.
When I deploy I get the error:
Error 1 Failed while Updating the Application 'BizTalk.System'. Permission denied. The current user does not have privilege to complete the operation. 0 0
Any ideas on what this means and what I'm doing wrong? From what I know it's not supposed to be updating BizTalk.System at all.
The BizTalk.System application is read-only so it can't be updated, but I doubt that you would be trying to update it without knowing it, especially with such a simple sounding project. Your new application should be referencing BizTalk.System though... maybe there is a problem creating this dependency?
These are some of the initial steps I would take to troubleshoot:
Check the BizTalkMgmtDb database to make sure you have the appropriate permissions
Check the EventViewer logs for more details about the Access Denied error
Try creating an empty application manually in the BizTalk Admin Console, see if you get the same error
If you can create the application manually, try deploying the project via VS 2008 to the empty application and see if you get the same error
Hopefully one of these will help pinpoint what the problem is (or even better, hopefully you've alreadty resolved the issue :) )
I agree that you shouldn't be deploying to the BizTalk.System application.
To check that you are deploying to the correct place, open your BizTalk project properties and click on the 'Deployment' tab (I'm making the assumption above that you are deploying locally, in which case the BizTalk Group Server and Configuration Database should already be set).
Under BizTalk Group, set Application Name to 'Test Application' (this can be changed later to something more meaningful); ensure all of the other boolean properties on the Deployment tab are set to true, with the exception of the Enable Unit Testing property.
When you now deploy the project from Visual Studio (by right clicking the project name and selecting 'Deploy', the new BizTalk Application will be created and the project deployed as a resource to that Application. Watch the VS Output window to check that they deployment is successful.
Once the deployment has completed, open the BizTalk Server Administration Console and expand the Applications node, you should now see a new application called 'Test Application'. If you expand the new app and take a look in Resources, you will see your recently deployed project.