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.
Related
I am trying to deploy an application to the Azure Service Fabric using the release definition task. When it gets to the task to deploy the server is returning the following error:
The type initializer for 'Microsoft.ServiceFabric.Powershell.Constants' threw an exception
I checked the Endpoint configuration and it appears to be set up as it is supposed to be:
No Authentication (this is an internal text box)
Cluster endpoint: tcp://[service fabric server]:19000
It downloads the artifacts without a problem, but in deploy it searches for the paths for publish profile and application package and finds them. After it finds them it throws the error. I have tried replacing TCP in the endpoint with http, added and removed the :19000 as well and all I get is this error. I have been searching online with little success. Any help to this end is much appreciated.
John
After lots of researching trying every suggestion I could find, we decided try and connect to the machine via Powershell on the box and it too was returning this error. So we uninstalled the SDK and re-installed it and the connection could be made and the builds started to work. I don't know exactly why it failed, but apparently a re-install did the trick. It may have been a bad install, or it could have been a versioning problem. Either way, try a re-install first.
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).
I got an error while trying to register plugin using the plugin registration tool in the SDK. The problem comes out of nowhere since before today I always able to do plugin registration using the tool with ease.
The error message is this:
Unhandled Exception: System.ServiceModel.Security.MessageSecurityException:
An unsecured or incorrectly secured fault was received from the other party.
Inner Exception: System.ServiceModel.FaultException: An error occurred when verifying security for the message.
I've done my searching and already try some steps that commonly suggested which are:
Deleting the LiveDevice.xml file under Users{username}\LiveDeviceID
Deleting the Connections.config file within the Plugin Registration Folder
Reboot the PC
Making sure the discovery url is correct (using: https://disco.crm5.dynamics.com/XRMServices/2011/Discovery.svc)
Download and using the latest SDK.
My environment is Windows 8 64-bit.
However, it didn't resolved my issue.
Is there any steps or things that I've missed or may done wrongly?
Following Guido comments about date & time of PC, I check the Dynamic CRM Online 2011 timezone, turns out it is set to (GMT +8 Krasnoyarsk), since I live in Singapore I changed it into (GMT +8 Singapore, Kuala Lumpur).
It is a long shot since the GMT is the same (+8), but I try it anyway and turns out it fixed the problem, I double check and change it again into Krasnoyarsk and again it's not working.
I'm not sure why this is causing it, since it is the same GMT, but for now I'll settle with this, maybe I'll raise a new topic for this later.
Thanks!
We use TFS2012 and VS2012 (some people use Update1 and some Update2). ). In some people's machines, we get:
TF400324: Team Foundation services are not available from server vstfps\Protection.
Technical information (for administrator):
Page not found.
This happens on any source control access, both in VS2012 and when running "tf.exe get". However, other TFS services work fine, for example work item queries.
I've uninstalled and re-installed VS (this time without Update2), and the problem persists.
I found a similar problem report, though it's somewhat different, and either way has no fix.
Debugging with Netmon, I noticed that affected machines use a different URI:
Good: /tfs/Protection/VersionControl/v4.0/repository.asmx
Bad: /tfs/Protection/VersionControl/v5.0/repository.asmx
What determines the URI the machine uses?
How can I change that?
Workaround: Close Visual Studio and related apps, then delete %LocalAppData%\Microsoft\Team Foundation\4.0\Cache.
Reason: (reconstructed from reports from my sysadmin...)
My TFS2012 RTM server was cloned from an existing server, keeping the same collection GUID. Effects:
The old server had Update1 installed and uninstalled. TFS2012 RTM only supported v4.0 URI, while TFS2012 Update1 added v5.0. So sometimes, clients would get confused and go to the old server, get the v5.0 URI, and keep that cached in ...\Cache\<guid>\LocationServiceData.config.
We've had TFS builds fail with "Can't copy activity logs", since they tried to copy to the old server.
Fix: Change the collection GUID at the new server, by running:
tfsconfig ChangeServerID /sqlinstance:<SQLInstanceName> /databasename:tfs_configuration
afterwards, people need to clean the cache one last time and that's it.
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.