I am trying to publish a django app on azure using Visual Studio 2015 Pro. and the azure tools. The publishing completes successfully but when I try to access the application online; I get this:
When I run my local server, the app runs with no problem and I can see the contents without exceptions or errors, but the published version of the app is giving me that error. Please help me solve this problem
Related
I'm attempting to run ColdFusion Builder 2016's built-in Security Analyzer. It's not working.
Here's my setup
I installed ColdFusion Builder 2016 along with ColdFusion Server 2016, by using the CF Builder installer on Windows 10. I have a valid registration serial for Builder, so this is not a demo version.
I set up ColdFusion 2016 as a Windows service so that it starts up with Windows on my dev machine, and I connected it to the locally running IIS web server. I added a second registration for a ColdFusion server in my CF Builder servers panel so that I could manage the Windows service from Builder. Both of the servers (one marked as a Windows service, one not) show as running in Builder's "CF Servers" panel.
I've run the Security Analyzer before, and had no errors with it. I don't know why it doesn't work today.
Duplicating the error
When I right-click on my project, a directory, or a file, then navigate to Security Analyzer, and try to run the security analyzer, I receive this message in an alert window:
Server error: Security Code Analyzer is not available in this edition of the ColdFusion Server.
Here's what I've tried
I edited my project properties to choose the service, then to choose the non-service. Both of them produced the same error.
I noticed that CF Builder's server registrations did not have "2016" as the version number. One was blank, the other was set to "11". I changed them both to 2016 and restarted CF Builder. I switched my project to each server, back and forth, with a combination of restarting Eclipse between tests. Same error.
I also tried changing the server's port from 8600 to 80 for the Windows service, but that resulted in an expected 404 error.
I restarted my local ColdFusion server and retried the above items. Same error.
Thought
At first I thought this might be that CF Builder thinks this is a server version error. At this point, I'm wondering if the Security Analyzer does not run on the development CF Server, even though I've had it running locally before. I can't connect it to any other CF2016 servers because we have a very, very large installation of CF11 enterprise servers, and have not begun to make a server infrastructure move to CF2016 yet.
The ColdFusion 2016 Code Securiy Analyzer is only available with an Enterprise edition license. However, the EULA for ColdFusion 2016 appears to allow you to use the same license key from a production server to activate a "development" server, so you should still be able to run the Security Analyzer on your development machine.
Summary:
I have an Office 365 E3 account where I'm trying to deploy a Word task pane app that will read some SharePoint list data. Right now, I'm just trying to get the task pane app to load, however, it shows the Office 365 login page (in the pane) but does not do anything after clicking Login.
Details:
I went through the instructions provided here:
http://msdn.microsoft.com/en-us/library/office/fp179815.aspx
Basically, I create an App for SharePoint configured as SharePoint-hosted, then in the same project, added an App for Office (Task Pane App for Word only). The SharePoint app also has a custom document library.
I am able to install the app to my App Catalog, and it correctly shows up in Site Contents where I see it being provisioned to the app web. I can also launch Word 2013 with the Trusted App Catalog configured correctly, and I am able to see my Task Pane App and insert it. When I click Insert, it loads it but prompts for credentials.
I am using the same credentials all throughout this exercise so by virtue of being able to install and deploy the SharePoint app, you can trust that I'm providing the right credentials.
It also appears the custom document library is never created - I wonder if both suffer from the same underlying issue.
I encountered the same problem and the solution provided in the answer below did not help.
After some desparation i created a taskpane app using the Napa Cloud App, opened the application in Visual Studio and went looking for differences.
In the Taskpane app manifest.xml file i found the following entries which were missing in my own application manifest:
<AppDomains>
<AppDomain>https://login.microsoftonline-int.com</AppDomain>
<AppDomain>https://login.microsoftonline.com</AppDomain>
</AppDomains>
This solved my problem and cured one horrible friday.
I was able to get this to work. It turns out doing a Deploy from Visual Studio (whether you right-clicked Deploy or F5-debug), the installation of the app isn't enough.
To make it work, I skipped doing a Deploy all together, but instead published my app. I then took the .app file and loaded it in my App Packages folder, and then deployed it from there.
Unfortunately, I don't know the difference between the two, but I'm assuming it has something to do with provisioning the app web for the Office App.
After a Windows 7 fresh restart, I open the Visual Studio 2010 as administrator, create a new project of Windows Azure Project with ASP.NET Web Role, then at the WebRole1 project I add a WebService1.asmx and press F5 (run).
The Windows Azure services starts OK and the browser open the http:/127.0.0.1:8080/WebService1.asmx perfectly. But when I click at Invoke button to test the webservice method I always receive a Bad Request - Invalid Hostname, with a http:/127.0.0.1:8081/WebService1.asmx/HelloWorld.
The most likely cause is ASMX's WSDL file doesn't stand by load balanced environment such as Windows Azure. The test feature relies on WSDL. You will see similar issues if you add a web/service reference. It is recommended to upgrade to WCF. In WCF, you can use useRequestHeadersForMetadataAddress (http://msdn.microsoft.com/en-us/library/ee816894.aspx) to fix the issue. If you need to use ASMX, please try to manually provide a correct WSDL file.
I have configured an SQL Server 2008 R2 db for ELMAH as described and works fine on development but not production. Both development and production connection string targets to same db, profiler shows nothing for the insert SP if I run production web site. I do not think its a SQL related problem. I have read some posts like
Elmah not working on IIS7 server
Elmah 1.2 does not log to SQL on Windows 2008 IIS7.5 Integrated mode (but works locally)
but even we have same problem, none of them helped me.
Both websites work on Windows Server 2008 R2 / .net 4.
Any ideas? TIA.
UPDATE : The only difference is my web site works integrated mode on development, and classic on on production. If I change classic to integrated it works fine.
So ELMAH doesn't work on classic mode?
it's probably problem with permissions to stored procedure.
use following script to give execute permission to the user (from connection string in productive system)
GRANT EXECUTE ON ELMAH_GetErrorsXml TO USER_NAME
GRANT EXECUTE ON ELMAH_GetErrorXml TO USER_NAME
GRANT EXECUTE ON ELMAH_LogError TO USER_NAME
I am working on Silverlight client to Microsoft Team Foundation Server. I am using an ASMX web service to make the actual calls using the TFS api.
Everything works fine when I run it with the visual studio development server, but I cannot figure out how to deploy the app to IIS.
I can get the ASMX web service to work unless it is a call that uses the TFS api. I have tried putting all of the TFS api DLLs in like every directory that I can think of, and even installing the visual studio sdk. Nothing works!
UPDATE 11/15/09 7:50PM EST:
Turns out that the TFS api was trying to create a cache at c:\Documents and Settings\Default User\Local Settings\Application Data\Microsoft\Team Foundation\2.0\Cache\, and the IIS_WPG user didn't have access to do so. Easy fix.
The only supported way of installing the TFS API is to install Team Explorer. You could try to GAC just the assemblies you need, but you're on your own [and technically violating the EULA]...
Other things to check:
IIS is running in 32 bit mode
Impersonation is working correctly
Proxy settings
What error do you get? Have you tried attaching a debugger to IIS?