This has happened to us AGAIN. [3 times so far, about a month apart...]
Spoke too soon, back to square one again
andyturpie (22nd January 2013)
will give that a look at cheers! Also our replica DC had just recovered from a BSoD.... why meeeeeeeeeeeeeeeeeeeeeeeeeeee!
Looks like our issue was DNS related, RM found out that DNS on our replica domain was listening over 3 different ranges 192.x.x.x 172.x.x.x and 10.x.x.x. This was changed to only listen on 172.x.x.x and then RMDatabase could then be reached. Shutdown Friday and restarted to find the same settings replicated back to our Domain Controller - hows our luck!
I always thought the best way to break CC4 was to install CC4 ?
When I was working at the school, we were fortunate not to get CC4 (due to RM agreeing that my network was running smoothly and without any issues). The other schools however were not that fortunate and had endless calls about CC4 issues..
That being said, CC4 seems to be one of those products where every single install is different and whilst 3 schools in the area have issues, the other 10 wont - despite it being an almost identical set-up.
Downside to my school not getting CC4 (and my subsequent falling out with a few people before I left) was that I didn't get a chance to learn it hands on -so its difficult for me to help with it or form a proper opinion of its stability, usability and other pros and cons...
CC4 is a great concept, it's a shame that it is so clunky and full of bloated software,
We often have this build failure with "installing additional packages" it is a random occurence and all the "solutions" still don't explain why after repeated attempts with the same workstation it will suddenly complete the build.
Sometimes it is caused by outstanding MS updates on server, sometimes it is caused by network traffic and timeout issues, sometimes it is the weather!!
There are currently 1 users browsing this thread. (0 members and 1 guests)