Fellow listers:
I saw another post where a user was having a similar issue (see thread- Q:
Urgent - user_cache), but they seemed to be able to run the arreload without
encountering the ARERR 92 error. This is my first post so I apologize in
advance if I was suppose to continue his thread instead of starting my own.
Our current configuration is a AR Server version 7.0 patch 8, which is
connecting to SQL Server 2003 database on a separate server. We are about to
do a massive overhaul of our User IDs. Moving from an old format to
requiring a User ID based on a valid email address. Currently we have over
640,000 user records.
On a development server I was able to convert our current records to the new
format with little problem via a SQL update to the User_x view. After the
update on that development server none of our testers could log in with
their new email format User IDs. I verified that their user records on the
User form showed them with the email address format. However, they could log
in with the same User Name and password that worked before the update was
made. I was able to save my user record with the new format and from then on
log in using the email address format. But saving each record manually with
this many records is not plausible.
I saw that the information on the user_cache did not match the information
on the user_x, so I attempted to run the arreload.exe runing each of the
following three commands in order:
cd c:\program files (x86)\ar system\servername\ (current location of
arreload.exe)
set artcpport=20000 (current portmapper port)
arreload -u User -f -a adminaccount -p adminpassword -d –s servername
This seemed to run as desired, but took over three hours. When it
“completed” I got the following message:
Updating ‘target’ server -- servername
Deleting existing user cache entries on servername
FAILED!
Timeout during database update – the operation has been accepted by the
server and will usually complete successfully servername <ARERR 92>
I ran this twice so far and both times got the same results. I think this
might be too many records for the arreload to handle at one time. Is there
another way to get the desired results without running arreload? Or do I
need to do something differently to get arreload to work as desired?
--
View this message in context:
http://old.nabble.com/Arreload-timing-out-%28ARERR-92%29-tp27349269p27349269.html
Sent from the ARS (Action Request System) mailing list archive at Nabble.com.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
