Webmatrix fails to publish my local Drupal website on a Azure server. The log reads:
11:07:01: The file 'MSDeploy.Continous/dbFullSql[#path='data source=.\SQLExpress;initial catalog=XXXXXXX;user id=XXXXXX']/sqlScript' is too large for file parameterization.
11:07:01: Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_PARAMETERIZATION_LIMIT_EXCEEDED.
But there is no mention of the error at the given URL.
The error could be related to my account since I get the same error with other projects and on other computers.
I switched my subscription from "Free trial" to "Pay as you go" and the issue went away. So, the blocking probably happened because I hit some subscription-ceiling.
(Why can't Microsoft document the error properly? It could only improve their sales and I would have saved time).
Related
My first publish attempt (for a site that I've been publishing for months with no problem) post-.NET 6 is generating this error.
Unable to perform the operation ("Create File") for the specified directory ("C:\inetpub\ECM2\wwwroot\Identity\lib\bootstrap\LICENSE")
I'm publishing as the Administrator and, as indicated, this has been working for months.
I was having the same issue. I'm using web deploy from VS to an Azure App Service, changing the setting 'Remove additional files at destination' to true fixed it. It's found in the settings for the publishing profile.
My first inclination was to tick the 'remove files' box as well. This allowed me to publish the site but it also had a follow-on effect (for anyone else with this issue).
I didn't consider that this would also delete the web.config file, the absence of which caused a very ambiguous 403 error.
Reconstituting web.config on the server took care of that.
Here's the error I received as well. I clicked on "Remove extra files" in the publisher profile and the error went away.
I have been struggling to get pst files uploaded to my azure storage. I have talked with Microsoft support on the phone, at length, and it just feels like guesswork from their end so I thought I would try here.
I have the Office 365 business essentials package. The domain that the current Exchange 2010 Server is on is a .local domain, so I am abandoning it in favor of our new .com domain. I already have O365 configured with the new domain. We only have 15 users so I figured pst files would be the simplest way to do it. This is also my first time using Office 365 and Azure so I have been attempting to follow MS procedures wherever possible.
The issue is whenever I run the azcopy.exe command with my parameters, I get an error 404 not found. Here is the command I am using (I’ve changed a few elements of this command in case I accidentally give away any personal data.):
azcopy.exe /source:C:\psts /Dest:"https://f47hr7hfh74hf4747fh74fh74.blob.core.windows.net/ingestiondata?sv=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
randomnumbersletteretc" /V:c:\365uplog\log1.txt
Here is the resulting error:
Error parsing destination location "https://f47hr7hfh74hf4747fh74fh74.blob.core.windows.net/ingestiondata":
Failed to validate destination: One or more errors occurred. The
remote server returned an error: (404) Not Found. The specified
resource does not exist.
I just had the same issue! I uninstalled the new version and reinstalled from an older version of the AZcopy tool "MicrosoftAzureStorageTools.msi" and it is now working correctly. It looks like an issue with the new client.
Version 5.0.0 works and 5.1.0 looks to be having issues.
I am trying to install Umbraco by using the Azure Marketplace. There they offer a template for it. I am always receiving the error below. I tried to install it a couple of times now but I always get the same error.
Does anybody know what this error message means? Is anybody able to install Umbraco by using the template in the Azure Marketplace?
]
You're asking 2 questions above.
Please see my answers and proposed troubleshooting guide/workaround below:
The error message means that the MSDeploy process failed due to some error which renders it unable to deploy the web deploy package for your Umbraco web app.
Yes I am able to provision a Umbraco web app from the Azure Market successfully (Location: Central US) and couldn't reproduce your issue
Troubleshooting Guide:
Append .scm in front of the azurewebsites.net of your Umbraco Web App as shown below and go to the Url.
Click on the Diagnostic Dump. You will be prompted to download a .zip file
Extract the zip file. You should see 2 folders at root level
Go into
LogFiles\SiteExtensions\MSDeploy
You should see the detail log files for MSDeploy
Detailed MSDeploy log messages are in the appManagerLog.xml file.
If it is related to client side issue which can be resolved by yourself, you can try to resolve it and try again.
If it is related to server side issue, you should create a support ticket for Microsoft to look into with the detailed MSDeploy log which pinpoints the root cause which will help them a lot.
Hope this is useful.
A Microsoft employee confirmed this is a bug in the application currently. I have to wait for a fix.
I have encountered numerous problems with the Azure installer of Umbraco, try setting it up in VS2015 then publishing it to Azure. I have found that this works well.
It looks like I have just happened to find an easy reproducible solution for infamous:
'Load operation failed for query 'GetUser'.
The remote server returned an errror: NotFound'
issue for WCF RIA Services (Silverlight 5) web setup: when using VS2012 Web Publishing Wizard with 'Precompile during publishing' option checked-on then the issue does raise its ugly head. When the 'Precompile during publishing' option is checked off then deployed WCF RIA Services works well with Silverlight client. Please check on your system.
I have used fuslogvw etc.etc. - nothing helped. Never used Web Publishing Wizard before - xcopy was my friend, this time I wanted to automate the whole deploying process - and lost a couple of hours of precious time.
I still don't know what is the cause of the issue but I can proceed with my work. Next time when there will be more free time I will probably use this technique to localize the causes of the subject issue.
Edit for clarification: I have effectively solved the subject issue on my localhost but I have it still appearing in one program but not in another when releasing on an external web hosting environment, and I'm yet to find what causes this issue - do you know any good sources where this issue's various solutions are classified and accompanied with solution walk-throughs?
I got a backup of a Sharepoint 2010 site that I created from our client's production server so that I can make some new changes to it on my staging server.
I can restore the site collection from the backup without a problem but when I try to create a backup of the same site on my staging server, I always get the error "Operation is not valid due to the current state of the object".
Before the error is given however, a small part of the backup file is created. If I try to run the Backup-SPSite again, it always fails at the same point and the corrupt backup files are always the same size.
Going through the logs it looks like the problem might be related to user permissions. I wonder if it's possible that the user permissions, user data, etc that came over from the client's production server are somehow screwing the backup process now because the same data cannot be found on my staging server.
The same error is mentioned here http://technet.microsoft.com/en-us/library/ee748617.aspx but UseSqlSnapshot parameter doesn't work anyway in my case.
I've been hitting my head against the wall with this problem and would appreciate if anyone has any advice on what might help! :)
The setup:
Windows Server 2008 R2
Sharepoint 2010 Server (no SP1 because it hasn't been installed on the client's production server)
Microsoft SQL Server Express Edition
Cheers!
The backup process started working after I checked in a file that had been checked out by a user on my client's production server.
I found out what file that was by opening the corrupted backup file and looking at the title of the last entry.