Guest kerrymoralee9280 Posted January 24, 2008 Posted January 24, 2008 Hey guys, I need help. All of a sudden machines started removing every network package after a reboot. We haven't changed anything. The strange thing is, we can't reallocate them after - the packages are not available in the management console (cc3), although they are available in the q: drive still (rm packages). Any ideas?
rusty155 Posted January 24, 2008 Posted January 24, 2008 Try updating the package list in the management console. So are any packages at all showing up in the management console or not?
Guest kerrymoralee9280 Posted January 24, 2008 Posted January 24, 2008 Tried doing that (may be the cause of it haha). There are packages left, but only a handful and only the ones that arent being uninstalled. If it has been uninstalled then it doesnt exist in the console.
rusty155 Posted January 24, 2008 Posted January 24, 2008 Have you run a D:\RMNetwork\RMManage\Station Manager\Healthcheck.exe from the server?
bizzel Posted January 24, 2008 Posted January 24, 2008 This reminds me of an RM article: DWN96091. That problem was fixed in SR3 though, what version are you on?
Diello Posted January 24, 2008 Posted January 24, 2008 Q:\PackageControl there and .ini files present for all of your stations?
Guest kerrymoralee9280 Posted January 25, 2008 Posted January 25, 2008 We're on SR6 - And we ran a health check on logging level 4. Nothing showed up. I rang my old network manager and he said it sounded like DNS issues. The packages need to be exactly the same on all DC servers. This wasn't so yesterday and when I came to build a package and subsequently updated the package list, everything went pear shape. I'm thinking this hasn't been right for a while and was triggered by updating the package list. We have ITSS coming out this morning to see if they can see and DNS replication errors and put them right.
russdev Posted January 25, 2008 Posted January 25, 2008 @kerry keeps upto date as will be interested in what caused it.
mwnci Posted January 25, 2008 Posted January 25, 2008 We had this exact problem recently. The problem occured when updating the package list - and this seemed to erase the contents of the station.ini in Q:\PackageControl file for each workstation. Once the workstations were restarted, AD repopulated the ini file but put uninstall_pending after each package. It could be a corrupt package. Check your package names in AD under Establishments and Locations to check that none have them have got strange characters at the end.
ThatBoringBloke Posted January 25, 2008 Posted January 25, 2008 We're on SR6 - And we ran a health check on logging level 4. Nothing showed up. I rang my old network manager and he said it sounded like DNS issues. The packages need to be exactly the same on all DC servers. This wasn't so yesterday and when I came to build a package and subsequently updated the package list, everything went pear shape. I'm thinking this hasn't been right for a while and was triggered by updating the package list. We have ITSS coming out this morning to see if they can see and DNS replication errors and put them right. Kerry, have you logged the call with ITSS? Can't find it in the system.
Guest kerrymoralee9280 Posted January 25, 2008 Posted January 25, 2008 Yeah, we've just had a gent out to have a look. Bill took the call from Richard but I think Bill thought it was a leaked system admin password so it may be logged under something like that. We've had an in depth look at DNS and we think we may have sorted it, just waiting for replication to take place. Should the packages replicate automatically? Or do they only replicate when the 'update packages' button is clicked in RM MMC. Cheers for all the help, will keep everyone posted.
Guest kerrymoralee9280 Posted January 28, 2008 Posted January 28, 2008 UPDATE: We manually copied the packages from the PDC to the other DC's and updated the package list - this displayed the packages in RM MMC once more and everthing looked like it had returned to normal. So we started allocating applications back out in the hope everything would be sorted for today. However, when RM AppAgent loads on startup it doesnt install anything. It stays on for a split second then goes to the log on screen. We have tried logging on and manually running it too. Any ideas?
Diello Posted January 28, 2008 Posted January 28, 2008 What server are the Q drives on your workstations mapped to? Or do you have them load-balanced? Be useful to see one of the station INI files from PackageControl.
01hanstu Posted November 26, 2009 Posted November 26, 2009 Do you have a multi-site config setup? In our Multi-Site setup we have this happening every tuesday, and its due to "Update Package List". We are starting to update the package list on the server just to see if RM Web Launch package on the client PC's is corrupt. Hope it helps. 01HanStu
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now