Thanks, that where I was headed, but I know little about SQL and didn't know if it's possible to restore a single table (as opposed to the entire database). It's something I'd have the DB admin do, in any case.
What we did end up doing is rename "shortAuthString" to "authString", as the columns were otherwise the same, and everything immediately worked again. It doesn't address what happened, nor does it prevent a future occurrence. We're good for now. Thanks! -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Grooms, Frederick W Sent: Tuesday, July 08, 2008 1:31 PM To: [email protected] Subject: Re: [ARSLIST] ARERR 552: authString problem Look in the server SQL log file to see what table the error is from. If it is indeed from the user_cache table you can just restore that table and then run an arreload (ConfigGuide-630.pdf Page 319) to rebuild the user_cache. You are correct in that my 6.3 user_cache table only has AuthString. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe Castleman Sent: Tuesday, July 08, 2008 11:17 AM To: [email protected] Subject: ARERR 552: authString problem System info: Windows 2k3 server ARS 6.3 patch 22 MS-SQL 2005 9.0 Yipes! Several users, including myself, are receiving the following error while attempting to perform any sort of action in Remedy: ARERR [552] Failure during SQL operation to the database : Invalid column name 'authString'. (SQL Server 207) The "authString" sounds like a column in the dbo.user_cache table. When I check, I don't see that column, which would certainly explain the error. However, I now have TWO columns called "shortAuthString" and "longAuthString". My question is "why?" I searched the archives for ARERR 552 and it seems that the database would make such a change during an upgrade to 7.0. I can assure you that I've made no such attempt, in fact I've been away from the system most of the morning (ha, that'll show me!). I see nothing relevant in the arerror or aruser.log files (and since I'm getting the error, I can't turn the logs on or off via the admin tool). The SQL log file only shows that a transaction log was successfully backed up - no errors or anything that suggests "dropped column, inserted 2 columns." Same with the Windows event viewer. The one thing I notice is that around the last transaction log backup ballooned to 800MB, normally it sits around a few MB depending on the level of activity. Anyone seen this? Any ideas? Mine right now is restore to the transaction log before the 800MB one, which I assume to be good. And of course this is without knowing what happened. Thanks in advance for any insight. ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
