Why does ESB application generates warning while trying to fetch "'mule-tracking-ee.xsd'" during deployment? - mule-esb

I am using Mule ESB 3.8.1 community Edition to create an application. While deploying the application in Mule ESB server, it tries to fetch the above xsd and generates the warning as follows:
WARN 2019-08-23 13:36:50,950 [WrapperListener_start_runner] org.springframework.beans.factory.xml.XmlBeanDefinitionReader: Ignored XML validation warning
org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://www.mulesoft.org/schema/mule/ee/tracking/current/mule-tracking-ee.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
This happens twice each time the mule service is started and caues delay in deployment. How can this issue be fixed?

Schemas (and components) with 'ee' means they are Mule Enterprise Edition (ee) only Features. They are not available in a Community Edition server. Remove the references from the schema and flow and it should deploy. You will not be able to use those feature though.

Related

KAA application Json/SDK JAVA

Am trying to create a new application on Kaa server, I'm facing the following issue:
--Can't upload a json file schema
>>>>>>ERROR: Provided parameters are invalid for requested operation: Failed to compile the schema: Compiler not found
--Can't generate Android or Java SDK
>>>>>>ERROR: Unexpected service error occurred: Compiler not found
--Can't delete an old Application, Schema or any configuration
You can change application configuration by adding new schema as describes in the create-schemas section of Your first Kaa application documentation. The capability to remove applications is not present in Kaa. See story for details.

Application Insights - No data for dependency duration

I am not getting data for any dependency calls (Azure SQL calls) in one of my clients' Application Insights which is running an Azure Web App. Initially, I thought the application is on older version of .Net (4.0), and then I created a sample Azure Web App with the latest ASP.NET 5 template with Azure SQL as database. Even for this one, no dependency call related data in Application Insights. Both the applications have been deployed successfully in Azure and I am checking the Application Insights data in the Azure portal. Any clue what is going on ..where should I check?
Please make sure you have Microsoft.ApplicationInsights.AspNet v.1.0.0-rc1-update3 installed (not that 1.0.0-rc1 that is default with VS2015). v.1.0.0-rc1-update3 should also install Dependency Collector module, so you should have HTTP/SQL dependencies collected by default for full framework. Just verified this is the case.

Visual Studio 2015 Web Deploy to SQL Server 2008

I was using VS2013 and i could publish successfully to my server which has SQL SERVER 2008.
Now i installed VS2015 and when i tried to publish my same project i am getting the below error.
Severity Code Description Project File Line
Error Web deployment task failed. (Could not deploy package.
Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database platform service.
Internal Error. The database platform service with type Microsoft.Data.Tools.Schema.Sql.Sql120DatabaseSchemaProvider is not valid. You must make sure the service is loaded, or you must provide the full type name of a valid database platform service.
Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXECUTING_METHOD.) 0

Error Publishing to Azure in VS 2010 - Object reference not set to an instance of an object

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

ESB Management Console (ESB Toolkit 2.1) not showing data

I successfully installed the ESB Toolkit 2.1 on top of BizTalk 2010.
Everything seems to work fine.
I created a sample app following Peter Kelcey's "BizTalk ESB Toolkit 2.0--Part 1: Dynamic Routing and UDDI Integration" (http://msdn.microsoft.com/en-us/biztalk/ee819071.aspx).
The message fails, but my problem is that I don't see anything in the ESB Management portal (or in the BAM portal, in the itinerary view).
I don't have any exception or anything, just no data.
I also checked the EsbExceptionDb database in SQL Server. And the connection strings in the portal web.config seem to be ok.
I must say that I installed the portal from the samples source, by rebuilding the solution and verifying all the configurations in IIS as per the documentation.
Thanks for any direction
Cos
Update on this:
I saw that I couldn't access the ESB.Exception.Service app from either VS or browsing from IIS
I rebuilt and republished the ESB.Exception.Service app.
Now the localhost/ESB.Exceptions.Service/ responds properly.
Also, I used the sample test app that calls the localhost/ESB.ExceptionHandlingServices/ExceptionHandling.asmx and now it is able to write to the database.
The ESB Portal shows the fault data now.
Basically rebuilding it fixed it, but I don't know what was wrong to start with.
Cos

Resources