I have a web app (.Net 4.6.2) running on an Azure App Service with Application Insights. I'm using SQL Azure as a back end. When Application Insights logs sql dependencies, the command text isn't included, just the server name and the database name shows up under 'Command'
I've uninstalled and reinstalled the extension and seem to have exhausted online sources. Can anybody suggest where else I look for a solution?
Is this how you install the extension? (Just double checking) And you tried removing/adding back the extension?
Also - does you application refer to SDK in source code already? (via nuget)
Related
I am trying to configure application insights for one of my WCF project. I did the configuration using visual studio and redeployed the application in IIS. But it is not sending any request Data to application insights. I have used same configuration method on a sample WCF application and I got request information in my app insights. I have referred some documentation for troubleshooting. It is showing to add appinsights.wcf package from Myget. But I don't have access to that in My workstation. Without Microsoft.ApplicationInsights.Wcf package I have successfully connected my demo application to application insights. Please share your suggestion for implementation. My main application is using .net 4.6.1 framework and my sub project has dependencies with another sub projects. Any suggestions is appreciated. Thanks in advance.
If your data is not sending into application insights, please go through the SO Thread.
I hope you are looking for without using Microsoft.ApplicationInsights.Wcf package in your project.
But without using this package it is not possible to send Telemetry data into application insights. Which is the must requirement to use the recent or prerelease Microsoft.ApplicationInsights.Wcf package in your project.
Refer here for more information
I'm trying to publish an ASP website with a Azure SQL database to Microsoft Azure using Visual studio 2015 community. Its getting stuck at a certain point and taking too much time. Screen is shown below.
Screenshot of Output window
From the deployment screenshot, it seems your application takes too long time to update file CustomerCarePortal.dll. If this file is too big, it is normal to take some time to upload. If this file is not big, please try to delete this file via ftp, then deploy again to see whether it will reduce your deployment time. You could also try to deploy the application to a new clean Web APP to check whether it related with Azure Web APP environment. If you have some deployment issue, please have a look at this article. The detailed log information may be help to find out the reason.
We are developing a Dynamic Web project using RAD which will run on WAS 7.0. We have configured WAS 7.0 within RAD to run the application directly from RAD. We also have
a web server setup and we need the static files in our Dynamic Web project to be served from Web server.
Unfortunately when we run the application from RAD, it doesn't add the information in plugin.xml file of web server. So we checked this in <WebApplication_Name>/Manage Modules section
in WAS Admin console. We are not able specify the web server target also there.
Is there anything that we can do to tell RAD to publish the application both to WAS and IHS? Could you please assist?
I am afraid this cannot be done using the RAD IDE out-of-the-box, as it just publishes your appication to WAS.
A solution to this would be to build and publish the application using a tool like Ant and place in your build script an extra step to appropriately change the plugin-cfg file.
I have deployed my web application in the folder
C:\Sybase\UnwiredPlatform\Servers\UnwiredServer\deploy\webapps
of SUP server. I have stoped and restarted the server. But it is not working.
i have also checked the server error log file it is not showing any error.
I have tested the same in tomcat server 6.0 it is working fine.
I am new in SUP2.0 environment. Please help me in deploying web application also let me know if i am following the right procedure..
thanks in advance
Pratap Kumar Panda
The suggested way to deploy a webapp is though Eclipse. (with the sybase plugin installed)
See these series of tutorials
http://www.youtube.com/watch?v=ls-swn433g0
I'm stumped. There are several threads out there that reference a similar problem, but not the same one. I'm trying to get a simple WCF service up and running in Azure, but my problem is happening before I even deploy. I'm following this article:
https://azure.microsoft.com/en-us/documentation/articles/cloud-services-how-to-create-deploy/
Which says to create your project, build the "Hello World" service interface and class, and then start your project locally. I get a 403 error when I try to start my project.
The only step I'm not following exactly is that I don't have a "Start Without Debugging" option (I'm using Visual Studio Express Web Developer), so I just push "Start Debugging."
Why would I get a 403 error on my own machine? I am running Visual Studio as Administrator.
On the WebRole project right click on your .svc (Service1.svc) and choose "Set As Start Page" And then run the project. Make sure to do this on the WebRole project not the Azure Cloude Project.
Is the Azure project the default project or is the WCF Web Role? If it's the role itself, that may be your issue - it's trying to access the root of virtual directory containing the web service versus running the cloud app in the local emulator. If you browse to http://127.0.0.1:81/Service1.svc in a new browser window do you still get the 403?
It seems VS has lost the its project settings. Bring up "Properties" page on the web service in VS. Go to the "Debug" tab. Under Servers/Virtual Path: my configuration was set to just "/". Put the name of your server back in there "/Service1.svc" and it should work from the debugger now. This fixed the problem for me.
The problem went away when I upgraded to VS 2010 Pro. I never fixed it on Express, but after upgrading the problem was gone ... I had the "Start without Debugging" option in the Pro edition, so I suspect that the problem may have been specific to Express.