I have a VM with Windows 2012 R2 installed on it, and today I started experiencing file copy problems.
These are the cases:
File Copy;
If I try to copy a folder full of files to another location, the processing is frozen in a random file for some seconds or minutes.
This issue continues randomly untill all the files are copied.
Unzip:
The same as above. If I try to unzip a file, the process in frozen in a random file for some seconds or minutes.
Delete folder:
The same as Copy Files. If I try to delete a folder, it takes looong to start deleting, then the process in frozen in a random file for some seconds or minutes.
RDC:
If I copy from local machine to remote machine using Remote Desktop, the upload is done until the 99%, when the process is frozen for seconds or minutes.
It started to happen today, yesterday was working fine.
Is this a hardware problem? May the disk dying? Or a software problem?
I have even started the Windows Update, but after 30 minutes or so, the downloading contines (0 KB Total).
Any ideas?
Note: there are no errors on Event Viewer.
Looks like the VM File server drive is acting up. Are you seeing this for any other VMs that you have ? Silly question, did you try restarting the VM ? May be some service is on a dead lock.
May be there was a service issue during the time the issue was happening, you should be able to check the state here if it is still happening for your region the VM is present.
https://azure.microsoft.com/en-us/status/
If it is an expendable VM you can try reimaging it.
If it still acting up, open a support ticket with Azure through the new portal,
To Open a Support Request
Go to the New Portal at https://portal.azure.com
Browse to your VM that is causing the Problem.
You should be able to see New Support Request on the Settings Blade of the VM.
Related
OS: Ubuntu 22.04 | CommandBox Version: 5.5.2 | Lucee Engine: 5.3.9+141
Having a really strange issue. I've installed CommandBox from scratch and am using the Lucee engine. Everything works fine until it's time to pull my web files from GitHub. Initially, all the files are served properly, but upon restarting the service, it is unable to start. I've tried a couple of things (changing user/group ownership, copying the files manually, even changing file permissions for the folder and everything inside) but it fails to start every single time.
I'm able to bring it up by deleting the web root folder and recreating it. I'm also able to run files that I create locally with echo/touch no problem. Kind of at a loss here as to where to go from here.
It sounds like the number of files in your web root are causing the XNIO directory watcher to take some time starting up. you can disable it like so:
server set runwar.args=['--resource-manager-file-system-watcher=false']
And the restart the server. Please note, this setting will actually be disabled by default in the next version of CommandBox due to occasional issues like this.
I have an issue with Volume Shadow Copies (VSS). This issue started a few days ago. I’ve tried MANY things from Google but cannot find a solution.
What’s frustrating (and surprising) is that even after I restored the computer to a sector-by-sector image backup, to a time that this issue was not existent, I still get this issue.
SYMPTOMS:
When trying to create an image in Macrium Reflect, it can’t, gives
error: VSS_E_UNEXPECTED_PROVIDER_ERROR.
When trying to run “check” on any disk from “tools,” I get “Windows
was unable to scan the drive”
From Windows Events: Volume Shadow Copy Service error: Error calling
a routine on a Shadow Copy Provider
{b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details Cannot ask
provider {b5946137-7b9f-4925-af80-51abd60b20d5} if volume is
supported. [0x8000ffff] [hr = 0x8000ffff, Catastrophic failure”
FACTS:
When I try cmd: “vssadmin delete shadows /all” (to clean up any dead
VSS snapshots) I get “No items that satisfy the query.”
The only VSS provider in the registry
(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers)
is Microsoft V1.0
CMD command, VSSADMIN LIST PROVIDERS, only shows Microsoft.
Services “Microsoft Storage Spaces SMP”, “Microsoft Software Shadow
Copy Provider” and “Volume Shadow Copy” services are set to automatic and run ok.
THINGS I’VE TRIED (not a complete list)
I Re-registered the VSS components with a bat file.
Tried resizing the VSS with “vssadmin Resize ShadowStorage /For=C: /On=C: /Maxsize=25GB” in cmd, I get “The shadow copy provider had an error.”
In safe mode, I ran chkdsk /f, SFC /SCANNOW, and DSIM.
In safe mode, I ran VSS repair and WMI repair via “Tweaking.com Windows Repair (All in One)” software.
All disks are reported ok in CrystalDiskInfo.
In HKEY_LOCAL_MACHINE\SYSTEM\Setup, SystemSetupInProgress is set to 0.
When running “vssadmin list writers” in CMD, they all say “no error.”
I am lost at what to do next.
Some UpperFilters value in the registry got deleted for some reason.
Carry out the following steps:
Open a new Notepad window
Copy and paste the below script into Notepad, and save as vss_fix.reg:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{71a27cdd-812a-11d0-bec7-08002be2092f}]
"UpperFilters"=hex(7):76,00,6f,00,6c,00,73,00,6e,00,61,00,70,00,00,00,00,00
This will update the UpperFilters value at this location to be volsnap (the hex code decodes to volsnap). Once you've copy/pasted the registry key, save this in a location you can easily access (e.g. desktop), and double click on the script to run the fix.
You will need to restart your machine once the fix has run.
I'll share my event log error when I tried and failed to run windows backup in case it helps searchers find this post.
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details IVssSnapshotProvider::IsVolumeSupported() failed with 0x8000ffff [hr = x8000ffff, Catastrophic failure].
FWIW- I don't know what messed it all up. I had installed AOMEI Backupper right before it- aiming to use it to clone to a new flash drive. I didn't actually use it since it was a pay version, but I did install and run the app. I'm highly suspect of it playing a role here. I've seen others have similar problems with Acronis utilities, Truecrypt, etc.
An automated Windows update this morning left my Windows Server 2012 R2 Classic Virtual Machine on Azure in a semi-crashed state. The VM is a web server, and all the files and applications in it are still accessible via the browser. In other words, IIS and a number of other services are still running. Unfortunately, however, the VM is not accessible via Remote Desktop and is unresponsive to commands from the Azure management interface on the portal.azure.com website.
This type of error is quite common and can be found reported on many other websites. The error has been happening to Windows users (not just Windows Server) for many years already, and none of the solutions online will work for Azure users, because they involve restarting from a CD, pressing shift-f8 during boot, issuing DOS commands, restoring from backup, or unchecking certain properties in VMWare or other software.
Does anybody have a real solution for this problem on Microsoft Azure?
After struggling with this for weeks, I think I was able to fix this with the help of Microsoft support! I decide to post the solution here in case it can help someone in the future. Here are the three things that you need to do to fix this:
1-Restore the VM from a backup prior to the crash. The VM with the "Undoing Changes" crash is pretty much toast at this point. Now, proceed to steps 2 and 3 to ensure that the next batch of Windows Updates won't crash it again!
2-On your new VM, ensure that the Environment Variables for TEMP and TMP both point to C:\Windows\TEMP. In my case, they were both pointing to a temporary folder in the logged in user's profile.
3-Ensure that C:\Windows\TEMP is always empty. I achieved this by setting up a scheduled task that runs a simple BAT file that deletes all files and folders inside of the C:\Windows\TEMP once a day. I spoke with a Microsoft representative who said that even though you may have plenty of hard drive space in your C:\ drive, the Windows TEMP folder is really not supposed to get much bigger than 500MB. When it gets very large you may have some issues with Windows Updates (mine was just under 500MB when the updates were failing).
I would recommend contacting Azure support as something may have to be done by an engineer to fix the issue and unfortunately classic VMs don't have the redeploy feature.
I've added only InboundPort 3389 RPD, and works well now.
We are using MS Azure Backup to backup our files from a specific folder on a local disk to an Azure backup service however it is not updating the cloud version of some files when they have been updated locally.
The errlog has recorded a number of the following errors
Failed: Hr: = [0x80070005] : CreateFile failed \?\Volume{...}\ with error :5
More worryingly the jobs in question on the jobs list show successful with no indication of any issues.
I only discovered this because 1 job from 3 days ago was tagged as having warning which appears to be a connectivity issue somewhere and came across these entries in the log.
Would someone be able to
Indicate how we can get these changed files to be backed up?
Answer why the MS Azure Backup jobs are listed as successful when these warnings have been recorded?
Thanks
Gavin
It seems like there is a permission issue to the files and folders which you are tying to backup to Azure. Please check if the folders or the drive you are backing up is formatted in NTFS.
Thanks
Hope this help.
I'm brand new to Azure. I'm trying to get a Cloud Service running with 3 web roles.
Last night I created the .cspkg and .cscfg files, exported the certificates and uploaded everything to Azure manager. The manager said my Cloud Service was successful, however for the last 10 hours when I click on "Cloud Services" in the manager it shows my service, but it says "Creating" with wait gif under "SERVICE STATUS".
Is it really still creating? Or did it fail? Is it possible to view more detailed information about the creation process and/or any log files?
Thanks,
Something "bad" has happened. Service Spin up time should be at most a few minutes.
I've seen it take up to 10-15 minutes depending on the hosting center and the number of scaled instances that need to come up but 10 hrs something has definitely gone wrong.
I would delete the service and start again. If you experience the same problem, have a look in your service start up code and make sure that there's no exceptions/infinite loops, other problems in there that might be causing problems.
It may miss any assembly references. If you included any assembly references(packages that are not part of .net) then please ensure that its copy to local attribute is set to true.