WSUS error

Dear Experts,

We are using SCCM 2012 . For the last one week i am getting the error Failed to delete orphaned content folder \\sccm servername\WSUS\UpdateServicesDbFiles, error 0x20. when i open wsyncmgr.log it shows this error.I have also attached the screen shot of the error.

Regards,

JCT
Wsus-Error.jpg
LVL 1
jct_777Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jcimarronCommented:
jct_777 --
Since you are getting no response here are some wild guesses.  When do you get this error?   Only when you open the wsyncmgr.log ?  Can you delete the orphan file manually?  (right click|Delete)

Do these reference offer any help
http://www.3ait.co.uk/blog/solved-shrink-a-wsus-database-susdb-mdb-to-almost-nothing-2/

http://henkhoogendoorn.blogspot.com/2013/01/remote-configuration-failed-on-wsus.html
0
jct_777Author Commented:
Hi ,

Yes when i open wsyncmgr.log its shows that particular error. But synchronzing is getting succeded. Is it ok if i right click susdb.mdf & then delete.

Waiting for your reply.

Regards,

JCT
0
jct_777Author Commented:
Hi ,

I am unable to delete by right clicking the Susdb.mdf file . It says the file is open in the Windows internal database(Mocrosoft ## SSEE). Close the file & try again.

Regards,

JCT
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

jcimarronCommented:
jct_777--
" It says the file is open in the Windows internal database(Mocrosoft ## SSEE). Close the file & try again."

Did you do that?

If still no success and this error is occurring only when you open the wsyncmgr.log  and synching is proceeding normally otherwise, perhaps do not worry about the error.
I assume the two references I provided did not help.
0
jct_777Author Commented:
Hi,
Above mentioned  error is occurring only when I open the wsyncmgr.log. Normally synchronizing is working fine.

Above references did not helped.

Regards,

JCT
0
jct_777Author Commented:
Dear Experts,

I want to close this question as presently there are no errors.

Regards,

JCT
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jct_777Author Commented:
After updating the windows & restarting the server presently there are no errors.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server Apps

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.