Troubleshooting WET - WET

WET RPC Issues

When I start my system, I get an error that reads Could not start RPC Server. WET will not work as expected. If there are stale ruby processes please kill them manually / restart you system and try!. As a result, WET doesn't work.

When I try to start the WET UI, I get the message RPC server is not running! Core parts of WET UI will not work without the RPC server running. Please start the RPC server using the tray application. Do you still want to continue?

The above messages are indicative of problems in the WET RPC communication layer. The WET Script Assistant UI is heavily dependant on the RPC communication to interact with the core layer and almost nothing in the WET UI will work without this communication layer. If you run into this issue, then please follow the below mentioned steps:

First off all exit the RPC Tray Manager Application by right clicking the WET tray icon and clicking Exit.
Kill stale ruby processes, if any! To do so, activate the task manager and kill all the ruby process that you are not expecting to be running.
Navigate to your <wet_install_dir>\ruby (if you are using a version greater than 0.9.8 then this will be <wet_install_dir>\core). You should see a batch file called StartWetRpc.bat. Run that batch file.
Wait for a minute or two and check the console output. You should see something like:

C:\svn_wet\main\openqa\core>ruby XmlRpcServer.rb 12987
12987
[Thu Oct 26 12:22:14 2006] HttpServer 127.0.0.1:12987 start
Depending on your ruby version, there may be other debug messages, but there should be NO ERROR messages. If you see any error messages here, stop and send the console output to the community forum. One of the community members will help you.
Leave the above console running.
Create a new ruby file with the following code:

##==================================
require "xmlrpc/client"

puts Time.now
server = XMLRPC::Client.new2( "http://localhost:12987")
result = server.call("wet.ping")
puts result
##==================================
Run the above code. On the console 'Pong' should be printed out.
If you dont see 'Pong' but some other message instead, please copy the messages from both the consoles (The rpc server console that is running and the ruby console from the previous step) and send it. Someone should be able to help you
If you do see the 'Pong' message, then leave this console running and try to start the WET UI. Check to see if you are still seeing the same problems as before. If the problem has dissappeared, then you probably have found a bug. Please attach allthe required logs and report a problem in the issue tracker. If the problem still exists,then send the console messages from the RPC server that you have started manually to the user forum.

1.While installing the new build (after uninstalling the older version from the computer)you get the error message shown below:

Work Around: The above problem commonly occurs after you uninstall the existing version in the computer to install the new version. The preventive step is to make sure that you exit the Rpc server if it is still running or appearing in the system tray even after uninstalling the current version. Then proceed with the installation process.

2.While trying to open some web pages from the UI, Internet Script Error window pops-up as shown below:

Work Around: You get the internet script error when you try to open those web pages with faulty HTML tags and attributes which is not recognized by Wet. Since it is the problem with the web page, there is no work around for this problem.

3.When two or more web pages are opened in the browser while testing with Wet, you can not continue as it gives an error(unhandled exception) as show below:

Work Around: You can test the web page in Wet by obtaining the proxy UI in sync with the browser. Wet core which is the Ruby layer generates scripts for all the actions performed on the proxy UI. Hence when a few web pages are opened in the browser, Wet will not be able to handle it.

4.If two or more Internet Explorer windows are open when you are trying to open the Wet UI, then Script_assistant error appears as shown below:

Work Around: For the same reason that is mentioned in the previous problem, the script assistant will not be able to run when too many web pages are open.

5. When you try to perform actions on the web page in the proxied UI, you wont be able to proceed or the Proxied UI just hangs.

Work Around: The above problem occurs because of the stale server, i.e if the Rpc Server is up and running for a long time. The work around for this issue would be to stop and restart the Rpc Server.

6. The web page with multiple frames does not open through the proxied UI, sometimes.

Work Around: The above problem has been fixed, however, you can close the script assistant and then open it again if it occurs.