Error occurred while saving the configuration make sure that it is possible to create

Allowlisting IPs: Error “An error occurred while saving the configuration”

Hi there, hope all is good.

I’m getting an error when trying to add Serpstat IPs to the Allowlist…

“An error occurred while saving the configuration: Please make sure you separate your IP addresses with commas. The following allowlisted IP addresses are invalid:…”

I’ve tried the IPs on separate lines and comma-separated. Same error each time. I’ve confirmed with Serpstat the IPs are valid.

Please can you help?

Hi @8persap, thanks for getting in touch.

Could you possibly add the IP addresses here in a code block so I can try them myself on my configuration? What you have provided in the screenshot seems valid but the contents of the textbox might hold a clue as to why this error message appears, so it’d be good to try replicating myself.

Thanks for the quick reply,Peter 👍

Hi @8persap, sorry for the delay.

There seem to have been hidden characters in the list of IPs provided that may be whitespaces, tabs or new line characters. Every time I copied the provided list in, I was also receiving the same error even after copying to Notepad and editing it manually.

To solve, I added commas and pasted the list into https://www.browserling.com/tools/remove-all-whitespace and was then able to save. I will provide this list again below, but if the forum adds any formatting characters you may have to run it through the link again as I did.

Edit:

I was able to paste the contents of the above quote directly from the forum into Wordfence and it saved successfully.

Failed to save configuration #1991

Comments

TomVandermeeren commented Feb 8, 2018

Plugins: Currently none
Mods: Minecraft, Minecraft Coder Pack, Forge Mod Loader, Minecraft Forge, SpongeAPI, SpongeForge, AE2 Stuff, Actually Additions, Advanced Generators, Ambience, Applied Energistics 2, Aroma1997Core, AromaBackup, AromaBackuprecovery, AutoRegLib, BD Lib, Baubles, Better Builder’s Wands, BetterBedrockGen, Block Armor, Botania, ChickenChunks, Chisel, Chunk Pregenerator, CoFH Core, CoFH World, CodeChicken Lib, Compact Solar Arrays, ComputerCraft, CraftTweaker JEI Support, CraftTweaker2, Cucumber, Cyberware, DeepResonance, ElecCore, Extended Crafting, External Tweaker, Extra Cells 2, Extra Utilities 2, Extreme Reactors, Gravestone Mod, ICBM-Classic, Industrial Foregoing, IndustrialCraft 2, InstantUnify, Iron Chest, IvToolkit, Loot Bags, LootTweaker, MTLib, Magical Psi, Mantle, Mekanism, MekanismGenerators, MekanismTools, MmmMmmMmmMmm, Moar Tinkers, Mod Tweaker, Modern Warfare, OMLib, Open Modular Turrets, OpenBlocks, OpenComputers, OpenComputers (Core), OpenModsLib, OpenModsLib Core, OreExcavation, PlusTiC, ProjectE, Psi, Quick Leaf Decay, Random Things, Redstone Arsenal, Redstone Flux, Refined Storage, SanAndreasPs Mod Library, SanAndreasPs Player Model, Secret Rooms 5, Shadowfacts’ Forgelin, SimpleInventoryStarter, TATW, Tesla Core Lib, Tesla Core Lib Registries, The Lost Cities, Thermal Cultivation, Thermal Dynamics, Thermal Expansion, Thermal Foundation, Tinker I/O, Tinkers Tool Leveling, Tinkers’ Addons, Tinkers’ Construct, UniDict, Voltz Engine, WanionLib, Zero CORE, mob_grinding_utils

Whenever the server launches this error will sometimes appear and this issue does not happend if sponge ain’t present https://pastebin.com/S5jkn7pR

This issue occurs at random during startup and i currently have no logs about it available except from the pastebin above.

The text was updated successfully, but these errors were encountered:

Zidane commented Feb 8, 2018

I ran a server with just Sponge on my desktop in a folder (to match how you are doing things here) and I cannot reproduce this issue. Even added multiple dimensions just because.

You’ve got a FileSystem issue or a rare edge case that can fail in Configurate.

TomVandermeeren commented Feb 9, 2018

All file permissions are default

ryantheleach commented Feb 11, 2018

Has this issue persisted since you restarted your computer?

TomVandermeeren commented Feb 11, 2018

TomVandermeeren commented Feb 12, 2018

What other information could i possibly give?

ryantheleach commented Feb 12, 2018

If we knew, we would have asked.

This issue occurs at random during startup and i currently have no logs about it available except from the pastebin above.

I ran a server with just Sponge on my desktop in a folder (to match how you are doing things here) and I cannot reproduce this issue.

You’ve got a FileSystem issue or a rare edge case that can fail in Configurate.

It’s unsolvable until someone who knows how to debug the issue can either reproduce it, or get reproduction steps that hint to what the problem is, thus, «more information needed» It’s not a slight against you, it’s a label to show the status on the main issue list until more information is turned up (either by you, a dev, or someone with a similar issue).

dualspiral commented Feb 12, 2018

For what it’s worth, Nucleus had a bug like this because I (currently) use Configurate for saving data, though I do plan to move away from that. It might be this, but I cannot be sure. Just hope this sheds some light on this.

In my case, it was due the file trying to load and save at the same time. In my system, I have a loading cache with a removal listener. In the case where an item was evicted, it would save, but sometimes it would tell the cache to re-add it. The result was that Configurate was trying to save and load at the same time. It’s a bug on all platforms, but manifests more verbosely on Windows based systems.

On Linux, this isn’t so much of an issue, because of the way the file handling works. If a file is being loaded and written, the handle is held, even though the file might be overwritten. The file path doesn’t matter once the inode is located (good SO explanation here) because read operations then work on the inode, not the file name, so even if the file name was redirected to a different inode, the loading process doesn’t care at that point (though may get outdated data).

Windows is a different story. The file gets locked during access and cannot be overwritten at that time. It’s the same cause as the infamous «this file is locked and cannot be removed» scenario. When reading the file, the file name is still important, so Windows locks the file. The save operation then comes in and fails because the file is locked, which results in an AccessDenied exception.

While I imagine the save and load happens on the same thread, I suspect the locks last longer than the code because Windows performs delayed write, causing the file to be locked for longer.

The first place to look is at the config saving/loading code. Is it loading and saving every time? If so, then that’s probably the culprit and it needs to be rationalised.

«An error occurred while saving the configuration prope

Hi,
I have installed the latest Jazz server but it apparently is having problems saving config info.When performing setup, I get this error message when, for example, when enabling email notifications:

«An error occurred while saving the configuration properties. Please check your server log for more details.»

Neither the WebSphere nor the jazz logs, which are working fine, indicate an error. Thus I do not know further details.

I am using WebSphere 6.1 with the fix pack described in the FAQ :
https://jazz.net/wiki/bin/view/Main/WASSetupFAQ

I have also specified file URLs as specified in the aforementioned FAQ.

Also, I have checked the file permissions on teamserver.properties. Java 2 security is turned off.

Any ideas where the problem could be?

3 answers

We are investigating another report of a very similar issue. I will
update this thread with more information soon.

Thanks!
Kristen Balhoff
Jazz Server Team

Hi,
I have installed the latest Jazz server but it apparently is having
problems saving config info.When performing setup, I get this error
message when, for example, when enabling email notifications:

«An error occurred while saving the configuration properties.
Please check your server log for more details.»

Neither the WebSphere nor the jazz logs, which are working fine,
indicate an error. Thus I do not know further details.

I am using WebSphere 6.1 with the fix pack described in the FAQ :
https://jazz.net/wiki/bin/view/Main/WASSetupFAQ

I have also specified file URLs as specified in the aforementioned
FAQ.

Also, I have checked the file permissions on teamserver.properties.
Java 2 security is turned off.

Any ideas where the problem could be?

I deinstalled everything and set up WebSphere as described in technical
note, «TN0033: Installing Jazz Team Server with WAS»
(https://jazz.net/learn/tech-notes/). Then I installed Jazz afresh and
things worked.

If I may make suggestions:
— Documentation is spread around somewhat. Ideally, the online
InfoCenter topic, «Setting up a WebSphere Application Server» would link
to the aforementioned technote or even integrate its info so that all
WAS stuff is in one place.I just happened across the tech note somehow.

— Would be helpful if the initial error message would reflect the actual
source of problem, ie, that I had not configured a user registry.

Definitely thanks for your fast response and asking the key question on
user rep!

Kristen Balhoff wrote:

We are investigating another report of a very similar issue. I will
update this thread with more information soon.

Thanks!
Kristen Balhoff
Jazz Server Team

cgiblin wrote:
Hi,
I have installed the latest Jazz server but it apparently is having
problems saving config info.When performing setup, I get this error
message when, for example, when enabling email notifications:

«An error occurred while saving the configuration properties.
Please check your server log for more details.»

Neither the WebSphere nor the jazz logs, which are working fine,
indicate an error. Thus I do not know further details.

I am using WebSphere 6.1 with the fix pack described in the FAQ :
https://jazz.net/wiki/bin/view/Main/WASSetupFAQ

I have also specified file URLs as specified in the aforementioned
FAQ.

Also, I have checked the file permissions on teamserver.properties.
Java 2 security is turned off.

Any ideas where the problem could be?

I’m glad you’re configuration is working, and I appreciate your
suggestions. I opened the following work items to follow-up on them:

66948: Detect webserver running without security, warn user in Admin &
Setup Wizard

66944: Integrate or cross-reference installation info/technotes/FAQ for
Jazz Server on WebSphere

Kristen Balhoff
Jazz Server Team

Chris Giblin wrote:

I deinstalled everything and set up WebSphere as described in technical
note, «TN0033: Installing Jazz Team Server with WAS»
(https://jazz.net/learn/tech-notes/). Then I installed Jazz afresh and
things worked.

If I may make suggestions:
— Documentation is spread around somewhat. Ideally, the online
InfoCenter topic, «Setting up a WebSphere Application Server» would link
to the aforementioned technote or even integrate its info so that all
WAS stuff is in one place.I just happened across the tech note somehow.

— Would be helpful if the initial error message would reflect the actual
source of problem, ie, that I had not configured a user registry.

Definitely thanks for your fast response and asking the key question on
user rep!

Kristen Balhoff wrote:
Hi Chris,

We are investigating another report of a very similar issue. I will
update this thread with more information soon.

Thanks!
Kristen Balhoff
Jazz Server Team

cgiblin wrote:
Hi,
I have installed the latest Jazz server but it apparently is having
problems saving config info.When performing setup, I get this error
message when, for example, when enabling email notifications:

«An error occurred while saving the configuration properties.
Please check your server log for more details.»

Neither the WebSphere nor the jazz logs, which are working fine,
indicate an error. Thus I do not know further details.

I am using WebSphere 6.1 with the fix pack described in the FAQ :
https://jazz.net/wiki/bin/view/Main/WASSetupFAQ

I have also specified file URLs as specified in the aforementioned
FAQ.

Failed to quiesce the virtual machine – ESXI 6.5 – Windows 2012 R2

An error occurred while taking a snapshot: Failed to quiesce the virtual machine. ESXi 6.5 – Windows 2012 R2

Issue: the Virtual machine has physical RDM (Raw Device Map) attached when taking backup or manual snapshot, You will see the following error

“An error occurred while quiescing the virtual machine. See the virtual machine’s event log for details.
An error occurred while taking a snapshot: Failed to quiesce the virtual machine.
An error occurred while saving the snapshot: Failed to quiesce the virtual machine.”

An error also appears in event viewer application logs of system

” Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\fdc#generic_floppy_drive#6&2bc13940&0&0# <53f5630d-b6bf-11d0-94f2-00a0c91efb8b>– 00000000000004DC,0x00560000,0000000000000000,0,0000023AEBCEF9B0,4096,[0]). hr = 0x80070001, Incorrect function.
Operation:
Exposing Recovered Volumes
Locating shadow-copy LUNs
PostSnapshot Event
Executing Asynchronous Operation
Context:
Device: \\?\fdc#generic_floppy_drive#6&2bc13940&0&0#
Examining Detected Volume: Existing – \\?\fdc#generic_floppy_drive#6&2bc13940&0&0#
Execution Context: Provider
Provider Name: VMware Snapshot Provider
Provider Version: 1.0.0
Provider ID:
Current State: DoSnapshotSet ”

Solution: There can be multiple reasons for this error to appear.
Method 1:

Method 2:

vSphere ESXi 6.5, 6.7, 7.0 – Unable to take quiesced snapshot

On VMware vSphere ESXi 6.5, 6.7, and 7.0, a condition exists where one is unable to take a quiesced snapshot. This is an issue that effects quite a few people and numerous forum threads can be found on the internet by those searching for the solution.

This issues can occur both when taking manual snapshots of virtual machines when one chooses “Quiesce guest filesystem”, or when using snapshot based backup applications such as vSphere Data Protection (vSphere vDP), Veeam, or other applications that utilize quiesced snapshots.

The Issue

I experienced this problem on one of my test VMs (Windows Server 2012 R2), however I believe it can occur on newer versions of Windows Server as well, including Windows Server 2016 and Windows Server 2019.

When this issue occurs, the snapshot will fail and the following errors will be present:

Performing standard troubleshooting, I restarted the VM, checked for VSS provider errors, and confirmed that the Windows Services involved with snapshots were in their correct state and configuration. Unfortunately this had no effect, and everything was configured the way it should be.

I also tried to re-install VMWare tools, which had no effect.

PLEASE NOTE: If you experience this issue, you should confirm the services are in their correct state and configuration, as outlined in VMware KB: 1007696. Source: https://kb.vmware.com/s/article/1007696

The Fix

In the days leading up to the failure when things were running properly, I did notice that the quiesced snapshots for that VM were taking a long time process, but were still functioning correctly before the failure.

This morning during troubleshooting, I went ahead and deleted all the Windows Volume Shadow Copies (VSS Snapshots) which are internal and inside of the Virtual Machine itself. These are the shadow copies that the Windows guest operating system takes on it’s own filesystem (completely unrelated to VMware).

To my surprise after doing this, not only was I able to create a quiesced snapshot, but the snapshot processed almost instantly (200x faster than previously when it was functioning).

If you’re comfortable deleting all your snapshots, it may also be a good idea to fully disable and then re-enable the VSS Snapshots on the volume to make sure they are completely deleted and reset.

I’m assuming this was causing a high load for the VMware snapshot to process and a timeout was being hit on snapshot creation which caused the issue. While Windows volume shadow copies are unrelated to VMware snapshots, they both utilize the same VSS (Volume Shadow Copy Service) system inside of windows to function and process. One must also keep in mind that the Windows volume shadow copies will of course be part of a VMware snapshot since they are stored inside of the VMDK (the virtual disk) file.

PLEASE NOTE: Deleting your Windows Volume Shadow copies will delete your Windows volume snapshots inside of the virtual machine. You will lose the ability to restore files and folders from previous volume shadow copy snapshots. Be aware of what this means and what you are doing before attempting this fix.

7 Responses to “vSphere ESXi 6.5, 6.7, 7.0 – Unable to take quiesced snapshot”

I am noticing very odd behaivor on 6.5. Basically I have a zfs zvol presented to esxi as an iscsi target via scst. For whatever reason when deleting a snapshot it causes a thin vmdk file to grow to its provisioned size.

for example i had a server using 700gb of data. The snopshot was 10gb. When i told vcenter to delete the 10gb snapshot it took hours and the vmdk grew to 4tb (the provisioned size). I was just curious if you have seen anything like this.

That’s actually crazy! I haven’t heard of, nor seen that happen.

I’m just curious, is your ESXi host running 6.5 fully patched (I think there’s been a few updates released that I’ve recently seen/deployed via vSphere Update Manager)?

Also, I’m just curious: Does SCST use/provide VAAI? Usually I see Lio-Target being used for iSCSI targets on Linux based storage hosts (since it provides multiple host access and VAAI)?

I’m actually not that familiar with SCST as far as VMware compatibility, VAAI, and clustered file system access on it…

Great catch on how Microsoft shadow copies impact VMWare snapshots. Helped to solve my problem. I think it is a “bug” on VMWare side and nobody reported it to VMWare (on not enough reports for them to spend time on fixing this problem). Technology….;)

I had the same issue but mine was an old backup agent on the machine.

Anything that interfaces, uses, or messes with the Windows VDS providers (such as your old backup agent), can cause this as well!

My issue was similar, but I worked out that my shadow copies were being taken exactly the same time as the snapshot was being created by the storage! So I altered the VSS times and its been fine ever since. But your article pointed me in the right directions, many thanks.