Category: Technical Solutions

Technical Solutions

OneDrive Error: “The cloud operation is not supported on…

Many of Horizon IT’s customers use cloud storage providers to share files within a smaller or remote office environment.
The 1TB of storage that is supplied with Office 365 is a simple choice for many, you may as well use what you already have.

What is often overlooked is that you should be backing up cloud stored files just as often and carefully as you would if files were on your own server.
Whilst, in theory, good old Microsoft’s platform is 100% available, their resilience doesn’t extent to restoring files from over 30 / 93 days ago, depending on your package.
What if a PC was infected with malware, it would encrypt OneDrive files, and they would be synced across the company.
What about malicious or accidental mass deletion?

So, for our desktop support customer we implement daily and monthly backups, typically to USB disk storage.
Last month, April 2018, our OneDrive backups started giving strange errors:

ERR 2018-04-20 00:34 An error occurred while compressing the file “GLOBALROOT\Device\HarddiskVolumeShadowCopy626\Users\zzzzzzzzzz\OneDrive\xxxxxxxxxxxxxxxxxx.docx”: The cloud operation is not supported on a read-only volume

We tracked this back to a OneDrive update that had, without informing the user, activated the “Files On Demand” setting.
Which basically only downloads the files to your PC when you request to open them.
So, we were trying to backup files that weren’t on the hard disk. Hmmmm…
Personally, we feel the users should have been given the option to store locally, or activate Files On Demand.
Naughty Microsoft!

Now, while we are in the settings, take a moment to head over to the “Office” tab, and then turn off “Use Office 2016 to sync files that I open”.
“Why?” we hear you ask, well…
When programs like Word are syncing to OneDrive, they do a lovely thing called auto-save, which automatically overwrites the file on OneDrive, even when you’ve not pressed the save button.
Now this becomes an issue when you are editing a document, to then Save As, because the original has already been overwritten, DOH!

And that brings us full circle as to why you should have a strong backup schedule on your cloud storage files.

If you need any assistance please contact Horizon IT.

Disable: Files on Demand

Disable: Use Office 2016 to Sync

Technical Solutions

Problem: Windows Process Activation Service (WAS) will not start

Windows Server IIS – Windows Process Activation Service (WAS) will not start.

So here at Horizon IT we run many web sites on our web servers, and after applying a recent Windows Update the IIS WWW, World Wide Web Publishing Service would not start.
It was saying the dependent service, Windows Process Activation Service (WAS), was not running, so then we tried to start that.
When we did that we had the usual cryptic Microsoft error:

“The Windows Process Activation Service encountered an error trying to read configuration data with AppHostProvider. The error message is: Bad Data. The data field contains the error number.”

Of course the error number means nothing!

So it’s 23:30 and we have 100 sites down and a server services that will not start.
We dive into Google and start hunting, after 45 minutes, with no success, we were about to consider rolling back the server to a previous back.
Then we found the article that changed the game!

We run a Plesk install on our server and earlier that day we had added a new web site for hosting.
We do that all the time, so nothing to worry about there….  Or maybe there is!!
It turns out that the site we added was the 101 site on the server, and guess what, there’s a buried setting that only allows WAS service to start if there are 100 sites in IIS or less!

Now we know that like us you a) Are baffled by such an arbitrary limit, and b) Stunned they couldn’t provide a meaningful error message.

So how do you fix it?
This link will give you the details:

Basically you:

  1. Open IIS Manager
  2. Select your IIS Server, then Configuration Editor
  3. Select the section system.applicationHost/webLimits.
  4. Change the value of dynamicRegistrationThreshold to a value greater than 100
  5. Start Windows Process Activation Service (WAS) service,
  6. Start WWW, World Wide Web Publishing Service.
  7. BOOM! sites up and running.






By continuing to use the site, you agree to the use of cookies. Privacy Policy

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.