SMS Collection problem

[sobak]

Okay, I had one of my engineers setup a secondary site wrong an set the master site as the Site Server. After I found out what had happened I removed both secondary sites that were setup incorrectly. The problem now is most of my collections have locks and there is no way to view the collection. I waited (thinking that it was a replciation issue) for about a week now and my locks are still there. Short of doing a restore of my SQL database is there anything that I need to go clean up when the secondary site was incorrectly assigned?

david e
[red]*[/color][blue]end users are just like computers, some you can work with...others just need a simple reBOOTing to fix their problems.[red]*[/color]

 

[tbrennans]

I'm not sure i am understanding what you are asking.

You mean your central site has locks on it? Its normal for child sites to have the padlock icon by the collections, other than ones created on them.

If it is your central site, and you re-made the secondaries, as a child of another lower level primary site, did you remove the sender from the central site that linked the secondary in the 1st place, I'm guessing but I could see that being a problem as the central site would never be able to synch up.

 

[sobak]

My Collections are being locked at my Primary Site (but not all of them). The secondary sites that were causing problems have been deleted. I'm not going to set them back up until this problem has been resolved.

I can't find much information on this problem. All the solutions that I find state this is a replication issue and it will clear up when replication happens again. My issue is that it's been going on over a week.

I only have one SMS Parent, all my other sites are secondary to the parent. When I open the SMS Management Console and navigate to Collections some (but not all) of my collections have locks. This is not normal and I have never seen this before so I'm lost as to a solution.

Hope this clears up the question a little, my desire is to get the locks off the collections so my Helpdesk Engineers can start using them again and we can start to deploy software.

david e
[red]*[/color][blue]end users are just like computers, some you can work with...others just need a simple reBOOTing to fix their problems.[red]*[/color]

 

[tbrennans]

when i said sender i meant addresses for the senders of the secondary sites..

The only thing I've seen on something like this was a guy that deleted then remade his senders, but I cannot speak from experience on this at all as I havent run into it.

Take a look on your primary site at the Hman.log, Colleval.log, and maybe the despool log and see if any errors are popping up in there.

Perhaps someone else has some thoughts on it.

 

[tbrennans]

have you synched and removed the sites with preinst yet?

http://support.microsoft.com/default.aspx?scid=kb;en-us;212978&sd=tech