My suggestion at that point would be to uninstall clean access agent and then clear the reg of all files associated with the agent and do a fresh install from there. We have been working on a reg fix here in our office, its still in beta but it will remove most of the files at this point, let me know if you have need of this and I will go about getting you a copy. The clearing of all the reg files should fix the problem though since cca installer doesn't actually repair all its reg files when it reinstalls. Let me know if theres anything else I can do for you. Theodore Gates CSU Housing Technologies Network Technician Fort Collins, Colorado 970-491-4734
On Tue, Aug 5, 2008 at 12:39 PM, Cat Hoffman <[EMAIL PROTECTED]> wrote: > It is popping up as an error in CCA, it is not replacing every line of > text. We are running CAM/CAS 4.1.3.1 with the 4.1.3.2 agent. Further > troubleshooting by the student at the help desk who emailed me about this > proplem stated the following: > > It seems that after downloading the latest update, CCA begins having > problems. If a copy of CCA has been installed prior, the user will get an > error saying that he/she's been blocked by administrator. After checking to > see if only the wireless network is enabled (and disabling all others), a > new error pops up saying "String Error."If the user simply downloads a fresh > copy, after updating the login box won't pop up. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Cat Hoffman > Network Infrastructure & Security Engineer > Office of Information Technology > Valparaiso University > 1700 Chapel Drive, B13 Kretzmann Hall > Valparaiso, IN, 46383 > Phone: (219) 464-6101 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > >>> > From: Teddy Gates <[EMAIL PROTECTED]> > To: <[email protected]> > Date: 8/4/2008 9:28 AM > Subject: Re: "String Error"? > > Rob,For the first string error the solution has seemed to be an update of > CCA from 4.1.3 to whatever upgraded version from Cisco we have at the time. > From best what I can tell is that CCA is having an actual error but for > some reason the file or key that the name of the error is associated with > is > missing from the persons personal computer. The update/reinstall normally > fixes both problems by replacing the file that is missing to name the error > and repairing whatever the error was showing. > The second string error problem was much odder and several people in my > office worked on it for awhile before finding the problem. Seems that > there > is the rare occasion where a computer will clear out a bunch of the > registry > files for CCA for seemingly no reason. Problem becomes that a reinstall > doesn't fix the issue because you can't get the computer to uninstall CCA, > the machine will act as if it doesn't see the program, however when > attempting to reinstall it requests to repair the program and then proceeds > to not have any reaction at all. So far the best method we have come up > with has been a complete clear of all registry files associated with CCA > and > then installing from scratch. > Both problems however don't seem to be actual errors for the agent just > notifiers that it cannot locate the name values from the programming as to > what it is suppose to be displaying. So, as far as we have gathered, clean > reinstalls of the program from a fresh image seems to be the only solution > since you cannot identify which error message is missing from the program > to > solve it. CCA still seems to work fine even if you don't address the > missing files but its next to impossible to figure out the actual error in > order to make the system work. Hope this helps. > Theodore Gates > CSU Housing Technologies > Network Technician > Fort Collins, Colorado > 970-491-4734 > > On Mon, Aug 4, 2008 at 6:47 AM, Rob Chee <[EMAIL PROTECTED]> wrote: > > > I've seen that problem sporadically, too, where it popped up as an error > > for CCA. In one instance a reinstall of the agent fixed the problem. > This > > was running version 4.1.3 on the manager and server . I was told that an > > upgrade to 4.1.3.1 could solve the problem. > > > > Teddy, I'd be really interested in hearing your solutions. > > > > Rob > > > > Teddy Gates wrote: > > > >> I have run into similar problems in the past at our network. To make > sure > >> before going into a long winded explanation is the 'string error' > popping up > >> as an error for CCA or is it replacing every line of text that should be > >> inside CCA with the words 'string error'. I only ask cause they are two > >> very different problems. > >> Theodore Gates > >> CSU Housing Technologies > >> Network Technician > >> Fort Collins, Colorado > >> 970-491-4734 > >> > >> On Sun, Aug 3, 2008 at 9:03 PM, Cat Hoffman <[EMAIL PROTECTED] > <mailto: > >> [EMAIL PROTECTED]>> wrote: > >> > >> I recently received an email from a student who works at our help > >> desk with this information below. Has anyone else seen anything > >> similar? > >> > >> > >> > >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >> Cat Hoffman > >> Network Infrastructure & Security Engineer > >> Office of Information Technology > >> Valparaiso University > >> 1700 Chapel Drive, B13 Kretzmann Hall > >> Valparaiso, IN, 46383 > >> Phone: (219) 464-6101 > >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > >> > >> > >> >>> > >> It seems that after downloading the latest update, CCA begins > >> having problems. If a copy of CCA has been installed prior, the > >> user will get an error saying that he/she's been blocked by > >> administrator. After checking to see if only the wireless network > >> is enabled (and disabling all others), a new error pops up saying > >> "String Error."If the user simply downloads a fresh copy, after > >> updating the login box won't pop up. > >> > >> Talking with the customers, it seems that not *everyone* is > >> getting this, but a lot of people are. CCA on our Windows laptop > >> seems to work fine, even after reinstalling it. > >> > >> As for the "String Error" message, the only thing I found on the > >> Internet was from Cisco's website, which seemed to indicate that > >> it has to do with the administration side of CCA. > >> > >> > >> >
