synchronization never run shows on wsusadmin page

[Aleksey "Carcass" Melnick]

i saw this quiestion in another thread, but it has no answer.
so situation:
wsus on win2003 box with full version of sql server 2000. according to
event logs, synchronization seems to running fine and all of updates is
fully synchronized, but the wsusadmin interface shows what synchronization
never run. also on the reporting tool web interface that server marked as
failed synchronization.
attaching the database to the test wsus server give no results.
so the question is how to repair database and save all the settings
(computers, groups, approvals) without recreating it.

[Lawrence Garvin (MVP)]

Can you post the content of the Event Logs that leads you to believe the
synchronization is "running fine"?

Can you also expand on what you mean by: "...attaching the database to the

test wsus server give no results".

Can you describe what you're doing with the database files, and how you have
your WSUS server and database(s) configured.

The way to "repair" the database is to uninstall and reinstall WSUS, and
rebuild the database by configuring WSUS, recreating your target groups, and
performing a synchronization. If you're using client-side targeting, the
clients will auto-populate the correct target group. If you're using
server-side targeting, you'll need to manually repopulate the groups.

Since I have no way of telling how your database is "corrupted", or even if
it -is- corrupted, there's no real guidance I can give you on "repairing" it
except the option to reinstall.

"Aleksey "Carcass" Melnick" <d9-...@mail.ru> wrote in message
news:op.s1zct5g8r50b11@carcass...

[Aleksey "Carcass" Melnick]

On Tue, 20 Dec 2005 05:04:52 +0300, Lawrence Garvin (MVP)
<onsi...@news.postalias> wrote:

> Can you post the content of the Event Logs that leads you to believe the
> synchronization is "running fine"?

runnin' fine means what i idd new category such as drivers to
synchronization settings and they successfully synchronized.

>
> Can you also expand on what you mean by: "...attaching the database to
> the
> test wsus server give no results".

i mean what i attach the full "susdb" database to another server

> Can you describe what you're doing with the database files, and how you
> have
> your WSUS server and database(s) configured.

doing nothing.
just apply dec'13 patches and reboot.

> The way to "repair" the database is to uninstall and reinstall WSUS, and
> rebuild the database by configuring WSUS, recreating your target groups,
> and
> performing a synchronization. If you're using client-side targeting, the
> clients will auto-populate the correct target group. If you're using
> server-side targeting, you'll need to manually repopulate the groups.
>
> Since I have no way of telling how your database is "corrupted", or even
> if
> it -is- corrupted, there's no real guidance I can give you on
> "repairing" it
> except the option to reinstall.

i don't want to reinstall and reconfigure.
for fix i just move some tables through standard sql procedure from
product (corrupted) database to clean one and save all the settings.

[Lawrence Garvin (MVP)]

As much as I'm willing to help you, Aleksey....

Your answers were pretty vague, and did not actually provide the information
I requested, and this comment at the end:

> for fix i just move some tables through standard sql procedure from
> product (corrupted) database to clean one and save all the settings.

pretty much requires me to tell you that you're on your own.. if you're
mucking inside the database (definitely -NOT- recommended), then there's
nothing I can do to help you 'unmuck' it.

"Aleksey "Carcass" Melnick" <d9-...@mail.ru> wrote in message

news:op.s2c45ii6r50b11@carcass...