I'm trying to publish an application I am working on and am receiving the following error...
Error 1 Failed to connect to 'C:\Users\me\Desktop\' with the following error: Unable to create the Web site 'C:\Users\me\Desktop'. Unable to create the Web site location 'C:\Users\me\Desktop'. Access is denied.
I am not trying to publish to a website so don't understand why it is presenting this problem?
Check that you have chose the right application for the project in the first place. but the error is indicating that its trying to load a website, while your writing or normal programming application. Hope that helps
I have checked and cannot identify the problem.
If you're running you program from a network location, as I am, you can change your Install Mode Mode and Settings to "The application is available online only".
Open your Project
Click the "Project" menu
Select "Properties" as the last item in the drop down menu
Select "Publish" from the list on the left
Change your Install Mode & Settings.
This worked for me...
Related
I am trying to enable my bot for "Everyone in your own domain". An getting this error.
If I enable it via "Specific people and group in your domain" - it works.
Does anybody have an idea what I missed?
When using the HEAD deployment, Apps script bots cannot be shared across an entire domain.
Though subtle, it is mentioned in the docs at https://developers.google.com/hangouts/chat/how-tos/bots-apps-script.
Image of description here
To fix this you can just create a new deployment and it should run just fine.
Go back to your Apps Script project
Click on Publish > Deploy from Manifiest
Click "Create"
Use the new Deployment ID for your project.
I am trying to connect to Googlefit but i am getting a strange error code as below
E/GooglePlayServicesUtil﹕ Unexpected error code 5005
Does anybody have any idea about this.Thanks In advance
I solved the error with the help of the answer in this post:
https://stackoverflow.com/a/28391583/2977169
#Sumoanand:
I also faced similar problem.
This issue occurs if app is not registered properly in google developer console.
I think you have registered app on Google developer Console using production keystore certificate fingerprint(SHA1) where as you are testing it on app which has debug keystore.
Perform following steps:
Create one more client Id using debug keystore certificate fingerprint(SHA1).
Uninstall existing app.
Install app & connect to Google fit.
Check under google fit app & make sure that your app is listed as a connected app (... > Settings > Connected apps > Connected apps & devices).
Now run the above code & it will work !!!
I had this error and the consent screen had been filled in correctly. The only way I could get around this was to delete the project and re-create it.
I changed my device date time to past time before connect to Google Fit and I got error 5005.
After changed to current time, it works :)
I have followed the PlayFramework 2.1's tutorial and when I was running the application ,the index page shows normally,but when I click the Button "Create" to create the task,it didn't work,and the console shown that #6ddhe2a72 - Internal server error, for (GET) [/tasks].
I'm puzzled now.
Please help me.
You should run playframework in development mode to see the full error. We cannot help you without that.
Instead of play start, simply launch play run (read this page for more details)
You could also see the stacktrace in the file log/application.log.
I followed the help page here
and I created my application through the eb tools command line tools. I can see the application on command line, however when I log into my AWS Management console and select the region area, and click on "elastic beanstalk" I see the welcome screen asking me to create a new application,my question is why cant I see my application on the web interface? Also the application is running on the web because when I visit the url the link is active, but I see this message "Could not find rake-10.0.2 in any of the sources (Bundler::GemNotFound)" (which if anyone knows how to fix that would also help)
Thanks in advance
It turns out that somehow amazon changed my secret keys, and my instanced where not showing. When I updated the keys on my local machine everything began working correctly.
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.