Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Problem with QC
#1
Not Solved
Hi

I am new to QTP and QC. I installed QC and QTP on the same machine. I installed QC with the Jboss server as Webserver on port 8080. But when I double click on Mercury Quality Center icon on the same machine where I installed QC, it says the page cannot be displayed. Whats wrong with QC. QC should be accessed only from another machine as this worked when I installed QC on one machine and accessed it from another machine in my office by typing the address of the other machine in the browser. Can't I open it from the same machine were I installed? Any inputs on this please.

Regards
Srinivas Aditya
Reply
#2
Not Solved
First make sure your webserver is up and running.
Reply
#3
Not Solved
Hi,

Before starting QC,you need check all add-ins are installed or not..

Regards
MVChowdary
Reply
#4
Not Solved
Hi

Thanks a Lot for the Replies. The problem lies with the Jboss webserver. I didn't start it. So I went to C:\Program Files\Mercury\Quality Center\jboss\bin\. I ran the run.bat file and it launched the cmd prompt and started the Jboss. But when I close the cmd opened by run.bat QC is not working. Is there anyway to run the webserver in the background without the cmd window.

Regards
Srinivas
Reply
#5
Not Solved
The below notes came from the Install.pdf file that goes with TestDirector for Quality Center.

JBoss Does Not Start
If you are using a JBoss application server, and you get a message that JBoss
does not start, check that JBoss works, check the JBoss service user, check
there are no JBoss script errors, and check that IIS was configured
successfully.
To check JBoss works:
1 Wait about 20 minutes in case the machine is slow, or JBoss and IIS are
working slowly.
2 Open your Web browser and type your JBoss URL. By default, this is
http://localhost:8080/qcbin.
3 Check if the Quality Center Welcome page is displayed.
If the Welcome page is displayed, the problem is within IIS.
If the Welcome page is not displayed, the problem is within JBoss. Check the
other JBoss troubleshooting options.

Maybe that will help.
Reply


Forum Jump:


Users browsing this thread: 5 Guest(s)