2 Replies Latest reply on Sep 26, 2011 12:20 PM by orafad

    Remedy issue URGENT!! Please help

    636919
      Hi All,

      I am not able to login to remedy client as I'm getting the below error

      *‘RPC: Miscellaneous tli error - System error (Connection refused)’*

      We tried to restart the remedy process, that dont work, Getting the below SQL errorAction Request System initializing.
      Starting Remedy AR System server

      Also I have checked the network/firewall as there is no issues with their end.
      Please anyone help me to resolve this issue.

      Error while restarting the remedy process

      Action Request System(R) Server Version 4.05.02 patch 1025
      Copyright (c) 1991 - 2001 Remedy Corporation. All Rights reserved.

      Copyright (c) 1989 - 2001 Verity, Inc. All rights reserved.
      Reproduction or disassembly of embodied programs and databases prohibited.

      Verity (r) and TOPIC (r) are registered trademarks of Verity, Inc.


      390600 : SQL database is not available -- will retry connection (ARNOTE 590)

      Notification System Server Version 4.05.02
      Copyright (c) 1994 - 2001 Remedy Corporation. All Rights reserved.
      110902110300- 24733: Initializing process 24733
      110902110300- 24733: DISPLAY_CONFIGURATION===================================
      110902110300- 24733: EXTERNAL START (-X) FALSE
      110902110300- 24733: RESTART (-r) FALSE
      110902110300- 24733: Check-Users: (-c) FALSE
      110902110300- 24733: Debug-Level: (-d) 21
      110902110300- 24733: Disable-Shared-Memory: FALSE
      110902110300- 24733: Hold-Time: (-h) 2592000 seconds = 30.0 days
      110902110300- 24733: Max-Users: (-u) 1000
      110902110300- 24733: Notifier-Outbound-Port: 0
      110902110300- 24733: Notifier-Specific-Port: 0
      110902110300- 24733: Private-RPC-Socket: 0
      110902110300- 24733: Private-Specific-Port: 0
      110902110300- 24733: Register-With-Portmapper: FALSE
      110902110300- 24733: Send-Timeout: (-t) 7
      110902110300- 24733: TCD-Specific-Port: 32768
      110902110300- 24733: ========================================================
      110902110300- 24733: AR System server: remedy01
      110902110300- 24733: AR ServerNameWithDomain: remedy01.ndc.lucent.com
      110902110300- 24733: HostnameWithDomain: remedy01.ndc.lucent.com
      110902110300- 24733: StartServerDaemons

      Notification Send Server Version 4.05.02
      Copyright (c) 1991 - 2001 Remedy Corporation. All Rights reserved.
      110902110300- 24736: Initializing process 24736
      110902110300- 24736: ProcessFiles: called with loginFd(0)=9 and notificationFd(1)=10
      110902110300- 24736: ProcessFiles: start Notifications at offset 0.
      110902110300- 24736: ProcessFiles: reopening nfyfile (new notificationFd=10)
      110902110302- 24733: StartServerDaemons daemon 0 started

      Action Request System(R) Mail Daemon Version 4.05.02
      Copyright (c) 1991 - 2001 Remedy Corporation. All Rights reserved.
      MailFileName: /usr/mail/fxbrophy
      Action Request System initialization is complete.


      390600 : Cannot initialize contact with SQL database (ARERR 551)
      Stop server

      390600 : AR System server terminated -- fatal error encountered (ARNOTE 21)

      Action Request System(R) Server Version 4.05.02 patch 1025
      Copyright (c) 1991 - 2001 Remedy Corporation. All Rights reserved.

      Copyright (c) 1989 - 2001 Verity, Inc. All rights reserved.
      Reproduction or disassembly of embodied programs and databases prohibited.

      Verity (r) and TOPIC (r) are registered trademarks of Verity, Inc.


      390600 : SQL database is not available -- will retry connection (ARNOTE 590)

      Thanks,
      Sajith
        • 1. Re: Remedy issue URGENT!! Please help
          636919
          All,Pease help
          • 2. Re: Remedy issue URGENT!! Please help
            orafad
            Why are you posting this on the Oracle forums, shouldn't you be talking to Remedy or BMC or whoever provides support for the product?

            Also this (or other public forums) is generally not the place for urgent production issues. There are paid support channels for such issues.


            Anyway, a hint:
            I would probably dig into the very vague "SQL database is not available" message. Does the system have details in logs? What clues does the actual/underlying error messages provide? Is the database in question actually up and reachable from the client (i.e. app server) host?

            Edited by: orafad on Sep 26, 2011 2:20 PM