Website Will Not Open Server Error In '/' Application No TNS Listener
search cancel

Website Will Not Open Server Error In '/' Application No TNS Listener

book

Article ID: 19847

calendar_today

Updated On:

Products

CA Business Service Insight

Issue/Introduction

Description:

This Document was created as a guide to explain how to troubleshoot the error no tns listener when trying to open bsi.

Website will not open server error in '/' application.

Solution:

TNS:no listener

Purpose: This Document was created as a guide to explain how to troubleshoot the error no tns listener when trying to open bsi.

<Please see attached file for image>

Figure 1

Solution and Prevention:

Firstly, check your windows services to see if the tns listener is started and set to automatic.

If not start it and retry opening the bsi application.

<Please see attached file for image>

Figure 2

If you still get the error no tns listener then you may have a corrupt tnsnames.ora and should recreate the listener and bsi service:

  1. First open start menu and open net configuration manager.

    <Please see attached file for image>

    Figure 3

  2. Choose listener configuration first. We want to delete the current listener.

    <Please see attached file for image>

    Figure 4

  3. Select delete

    <Please see attached file for image>

    Figure 5

  4. Select the current bsi listener and delete it.

    <Please see attached file for image>

    Figure 6

  5. Add a new listener

    <Please see attached file for image>

    Figure 7

  6. Click next

    <Please see attached file for image>

    Figure 8

  7. Create a name for listener

    <Please see attached file for image>

    Figure 9

  8. Click next to finish

    <Please see attached file for image>

    Figure 10

  9. Now delete the old service name

    <Please see attached file for image>

    Figure 11

  10. Select delete

    <Please see attached file for image>

    Figure 12

  11. Select your bsi service name and click next to delete

    <Please see attached file for image>

    Figure 13

  12. Now add a service name for BSI

    <Please see attached file for image>

    Figure 14

  13. Create a name

    <Please see attached file for image>

    Figure 15

  14. Click next

    <Please see attached file for image>

    Figure 16

  15. Add your host name and click next to finish

    <Please see attached file for image>

    Figure 17

After completion of these steps you should have test that you can tnsping your new service name in cmd.

Open cmd and execute: tnsping bsi (Or whatever you named the service name)

If you can connect the error should go away.

Environment

Release:
Component: OBLCRE

Attachments

1558718092574000019847_sktwi1f5rjvs16ut0.gif get_app
1558718090632000019847_sktwi1f5rjvs16usz.gif get_app
1558718088597000019847_sktwi1f5rjvs16usy.gif get_app
1558718086574000019847_sktwi1f5rjvs16usx.gif get_app
1558718084817000019847_sktwi1f5rjvs16usw.gif get_app
1558718082949000019847_sktwi1f5rjvs16usv.gif get_app
1558718081010000019847_sktwi1f5rjvs16usu.gif get_app
1558718078979000019847_sktwi1f5rjvs16ust.gif get_app
1558718076998000019847_sktwi1f5rjvs16uss.gif get_app
1558718075104000019847_sktwi1f5rjvs16usr.gif get_app
1558718073330000019847_sktwi1f5rjvs16usq.gif get_app
1558718071336000019847_sktwi1f5rjvs16usp.gif get_app
1558718069394000019847_sktwi1f5rjvs16uso.gif get_app
1558718067601000019847_sktwi1f5rjvs16usn.gif get_app
1558718065761000019847_sktwi1f5rjvs16usm.gif get_app
1558718063787000019847_sktwi1f5rjvs16usl.gif get_app
1558718061550000019847_sktwi1f5rjvs16usk.gif get_app