Discussion:
Cannot save configuration because the server is still processing a previous configuration change
(too old to reply)
Robert Hindla
2005-09-06 20:22:47 UTC
Permalink
Raw Message
Having recently installed WSUS, I was very pleased with it . . . Until I hit
my first error. I tried to change from manual to automatic synchronization,
but when I reopened the console the next day, I was told to "please wait
while your settings are saved." Restarting IIS and rebooting the server did
not help.

When I went to make another change, on another menu, I received "cannot save
configuration because the server is still processing a previous
configuration change."
Lawrence Garvin
2005-09-07 04:54:32 UTC
Permalink
Raw Message
Robert, I encountered this issue today while doing some testing and
research. While I don't think my scenario is similar to anybody elses (at
the time I encountered it, I had just Disabled the BITS service), my 'fix'
may well be relevant for anybody.

I closed the WSUS Admin console, (would have stopped BITS, but it was
already stopped), reset BITS back to Manual, and restarted the Update
Services service, which also restarted BITS. Then reopened the WSUS Admin
Console and the "settings are being saved" message was gone and
functionality was returned.

Rebooting the server should have accomplished the same thing, but perhaps
there is something in the dependencies and sequencing of startup/shutdown of
services that prevents it from resetting. It's also possible that simply
restarting the Update Services service won't help -- but it's worth a
shot -- as it did reset my one occurrence of the situation.
Post by Robert Hindla
Having recently installed WSUS, I was very pleased with it . . . Until I hit
my first error. I tried to change from manual to automatic
synchronization,
but when I reopened the console the next day, I was told to "please wait
while your settings are saved." Restarting IIS and rebooting the server did
not help.
When I went to make another change, on another menu, I received "cannot save
configuration because the server is still processing a previous
configuration change."
Lawrence Garvin
2005-09-09 04:20:08 UTC
Permalink
Raw Message
I have a followup to this message, with some additional details describing
exactly what I believe caused the situation in my case.

(1) Update Services did not start properly at system startup. (Not directly
a cause, but a contributing factor in this scenario.)

(2) Manually started Update Services, which would normally, then, start the
BITS service (from Manual mode).

(3) Before the BITS service got the chance to start up, I had reconfigured
it as Disabled. (Had Update Services started properly, then BITS would have
already been running and this issue would have never occurred at this
point.)

(4) This caused the Update Services service to fail its own startup,
ostensibly because dependent services did not start up.

This happened to me again, just moments ago. (I'm doing some research, so
I'm intentionally disabling BITS to reduce the overhead on my system since I
don't actually need to download the content.)

What I found was the Update Services service stopped. I restored BITS to
Manual mode, restarted the Update Services service, allowed the BITS service
to start up fully, then set the BITS service to disabled and stopped the
BITS service, leaving the Update Services service running. Restarted the
WSUS Admin Console and the "saving settings" message was reset.
Post by Lawrence Garvin
Robert, I encountered this issue today while doing some testing and
research. While I don't think my scenario is similar to anybody elses (at
the time I encountered it, I had just Disabled the BITS service), my 'fix'
may well be relevant for anybody.
I closed the WSUS Admin console, (would have stopped BITS, but it was
already stopped), reset BITS back to Manual, and restarted the Update
Services service, which also restarted BITS. Then reopened the WSUS Admin
Console and the "settings are being saved" message was gone and
functionality was returned.
Rebooting the server should have accomplished the same thing, but perhaps
there is something in the dependencies and sequencing of startup/shutdown
of services that prevents it from resetting. It's also possible that
simply restarting the Update Services service won't help -- but it's worth
a shot -- as it did reset my one occurrence of the situation.
Post by Robert Hindla
Having recently installed WSUS, I was very pleased with it . . . Until I
hit
my first error. I tried to change from manual to automatic
synchronization,
but when I reopened the console the next day, I was told to "please wait
while your settings are saved." Restarting IIS and rebooting the server
did
not help.
When I went to make another change, on another menu, I received "cannot
save
configuration because the server is still processing a previous
configuration change."
Robert Hindla
2005-09-12 18:06:08 UTC
Permalink
Raw Message
I removed WSUS and reinstalled it. That cleared up the "please wait while
you settings are saved" situation. I scheduled a synchronization and the
synchronizations succeeded. All was well until I pared the language
selection down to English. Right at that point, the "please wait while your
settings are saved problem" reintroduced itself. I will see if the synch
goes through tonight.
Post by Lawrence Garvin
I have a followup to this message, with some additional details describing
exactly what I believe caused the situation in my case.
(1) Update Services did not start properly at system startup. (Not directly
a cause, but a contributing factor in this scenario.)
(2) Manually started Update Services, which would normally, then, start the
BITS service (from Manual mode).
(3) Before the BITS service got the chance to start up, I had reconfigured
it as Disabled. (Had Update Services started properly, then BITS would have
already been running and this issue would have never occurred at this
point.)
(4) This caused the Update Services service to fail its own startup,
ostensibly because dependent services did not start up.
This happened to me again, just moments ago. (I'm doing some research, so
I'm intentionally disabling BITS to reduce the overhead on my system since I
don't actually need to download the content.)
What I found was the Update Services service stopped. I restored BITS to
Manual mode, restarted the Update Services service, allowed the BITS service
to start up fully, then set the BITS service to disabled and stopped the
BITS service, leaving the Update Services service running. Restarted the
WSUS Admin Console and the "saving settings" message was reset.
Post by Lawrence Garvin
Robert, I encountered this issue today while doing some testing and
research. While I don't think my scenario is similar to anybody elses (at
the time I encountered it, I had just Disabled the BITS service), my 'fix'
may well be relevant for anybody.
I closed the WSUS Admin console, (would have stopped BITS, but it was
already stopped), reset BITS back to Manual, and restarted the Update
Services service, which also restarted BITS. Then reopened the WSUS Admin
Console and the "settings are being saved" message was gone and
functionality was returned.
Rebooting the server should have accomplished the same thing, but perhaps
there is something in the dependencies and sequencing of startup/shutdown
of services that prevents it from resetting. It's also possible that
simply restarting the Update Services service won't help -- but it's worth
a shot -- as it did reset my one occurrence of the situation.
Post by Robert Hindla
Having recently installed WSUS, I was very pleased with it . . . Until I
hit
my first error. I tried to change from manual to automatic
synchronization,
but when I reopened the console the next day, I was told to "please wait
while your settings are saved." Restarting IIS and rebooting the server
did
not help.
When I went to make another change, on another menu, I received "cannot
save
configuration because the server is still processing a previous
configuration change."
Loading...