Hi Roy,
I got this error today and I resolved it changing the Mid-Tier password under the Server Information > Connection Setting > Mid-Tier Administrator Password and them went to the Mid-Tier configuration to change the password there. I haven't time to work further on this but I'll investigate this latter, my clues are: 1) The password defined during the installation process gets truncated or something like that; 2) This can be related to the Mid Tier password complexity or length. I realized that the issue was on the password side because during my initial investigation to resolve the issue I went on the AR Server Settings on the Mid Tier Configuration Tool and tried to change the Pre-Load option(or any other modification), after that when I tried to save the change I got this same error [103] there. Regards, Tales Parreiras da Silva. -----Mensagem original----- De: Action Request System discussion list(ARSList) [mailto:[email protected]] Em nome de Ashcraft, Roy W CTR USAF AFWA 2 SYOS/SYOE Enviada em: quarta-feira, 1 de dezembro de 2010 17:00 Para: [email protected] Assunto: ARERR 103 I'm attempting to setup a demonstration server for the ITSM suite for management. My configuration: Windows 2003 Enterprise Server R2 AR System 7.06.03 Atrium CMDB 7.06.03 ITSM Change/Asset, etc. v7.06.03/02 as appropriate for all the pieces Plus a number of pieces I'm probably forgetting. The problem that I'm running into is that when a user (Demo, the only user on the system at the moment) attempts to log in through the browser client, they receive ARERR 103 ARERR Name parameter (or name field in a parameter) is longer than the maximum allowed length. However, the same user can login through the thick client without issue. To get this up and running, I've read most of the installation guides and followed this install path - Java JDK/JRE 1_6_22 (both 32 and 64-bit) SQL Client Tools Tomcat 6.0.29 BMC Atrium Core Services (CMDB w/Product Catalog, Impact Simulator, Integration Engine, Web Services, Registry) BMC SMPM BMC ITSM Asset and Change I know that with everything installed on one box, this will be extremely slow, however, this is just for demonstration. If this goes into production, the services will be split between numerous different servers, especially the web components. The Knowledge Base at the BMC support site has yielded the usual wealth of information, meaning, no matches that even resemble the problem that I'm seeing from any search base that I've tried so far. The most recent version of AR System that I have experience with is 7.1, meaning, the numerous changes with 7.06.03 are completely new to our environment. Can someone point me to something that would help me troubleshoot this? At least someplace to start looking? Thanks, Roy \\SIGNED\\ ROY ASHCRAFT, Contractor, 2 SOS/SYOE Remedy ARS Support, SAIC (402) 294-8225, DSN 271-8225 [email protected] ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
