Hi joelajean,
We had found that some environments had issues with MS Message Queue on installation. In the Visual Studio Plug-in v2.0 (that is now available in beta) we removed the Message Queue requirements.
I would recommend uninstalling the v1.2 and installing the v2.0 beta that has addressed many of these issues.
v2.0 can be found here:
http://na.blackberry.com/eng/developers/devbetasof
Hi Tim,
I uninstalled v1.2 and re-installed v2.0. Now, when I launch the plug-in the "Message Queue" error is no longuer displaying but I still get the following :
The "Start BlackBerry Simulator" is left hanging...
[Start BlackBerry MDS-CS] Starting ...
[Start BlackBerry MDS-CS] DONE!
[Start Device Simulator] Launching Fledge: Launch file - C:\Program Files\Research In Motion\BlackBerry Widget Packager\simpack\fledge.exe, Parameters - /app=Jvm.dll /handheld=9500 /app-param=DisableRegistration /app-param=JvmAlxConfigFile:9500.xml /app-param=JvmDebugModeOff /session=9500 /app-param=MdsDebug
ff /app-param=BrowserDebugPort:5557 /app-param=BrowserDebugn /app-param=NoTutorial /JvmDisableBacklightTimeout /pin=0x2100001A /app-param=BrowserDebugPort:5557, Skin - Default BlackBerry Widget Simulator 9500 (Version 5.0.0.307), PIN - 0x2100001A
[Start Device Simulator] Waiting for simulator to finish loading...
... if I cancel out, I get the following warning message "Failed to launch fledge" and than the simulator loads but I have to kill the "RIM.Net.Tools.ScriptHost.exe" process using the Task Manager. Once it's killed, the VS.Net debugger seems to attache itself but the demo web site does not load in the simulator. I get the following error on the BB simulator: "Unable to connect to the selected Mobile Data Service, please try again later."
Installed Production running on XP
Microsoft Visual Studio 2008
Version 9.0.30729.1 SP
Microsoft .NET Framework
Version 3.5 SP1
Installed Edition: Professional
Microsoft Visual Basic 2008 91605-130-0881902-60645
Microsoft Visual Basic 2008
Microsoft Visual C# 2008 91605-130-0881902-60645
Microsoft Visual C# 2008
Microsoft Visual C++ 2008 91605-130-0881902-60645
Microsoft Visual C++ 2008
Microsoft Visual Studio 2008 Tools for Office 91605-130-0881902-60645
Microsoft Visual Studio 2008 Tools for Office
Microsoft Visual Web Developer 2008 91605-130-0881902-60645
Microsoft Visual Web Developer 2008
BlackBerry® Web Plug-in – Browser Development 2.0.0.10
BlackBerry® browser development is a one of two components in the BlackBerry® Web Plug-in
BlackBerry® Web Plug-in – Widget Development 2.0.0.10
BlackBerry® widget development is a one of two component in the BlackBerry® Web Plug-in
Hi joelajean..
What I think you are seeing is actually two issues caused by the same thing. Some sort of connection issue seems to be interfering in communication between the various components of the BlackBerry Web Plug-in.
The first is the one that is causing the BlackBerry simulator to seem to go off into space and not display the web page on first run. In this case Visual Studio is waiting for a call back message from from the BlackBerry Simulator that it's not getting. When you reset the environment by cancelling the debug process and killing the scripthost and then rerunning.. it works the second time as Visual Studio detects the running BlackBerry Simulator.. (It doesn't wait for the callback)
Another way of doing the above without going through the headache of killing the scripthost is to do the following:
1) Browse to the following directory: C:\Program Files\Research In Motion\BlackBerry Widget Packager\simpack
2) Run the following from a CMD prompt: "fledge.exe /app=Jvm.dll /handheld=9500 /app-param=DisableRegistration /app-param=JvmAlxConfigFile:9500.xml /app-param=JvmDebugModeOff /session=9500 /app-param=MdsDebugff /app-param=BrowserDebugPort:5557 /app-param=BrowserDebugn /app-param=NoTutorial /JvmDisableBacklightTimeout"
3) This will start up the BlackBerry simulator manually.
4) From Visual Studio click to debug your demo website... You will get a message stating "You have selected a different skin than the one being used by the currently running simulator. Do you want to close the current simulator and start a new instance with the new skin 'Default BlackBerry Widget Simulator 9500 (Version 5.0.0.307)'?" You can click No to this and it Visual Studio will use the already started simulator.
The second issue I am still not too sure about. It appears that there is another communication issue, this time between the BlackBerry Simulator and the MDS Simulator.
Can you do the following... can you try debugging your demo website from a disconnected state?? Off the network I mean?? I would like to see if you what you are experiencing is being caused by a network problem.
Thanks for your patience..
Best Regards
Dave
Hi Dave,
Well, I’m one step further than last week 
!!!!
I tried the step above in a connected and disconnected environment and both test permits the Visual Studio debugger to attach itself to the simulator (Rim.NetTools.ScriptHost.exe).
If I run the VS.Net debugger without running the MDS Simulator I get the following error “Unable to connect to the selected Mobile Data Service, please try again later.”
Since the error was related to MDS, I figured that it needs the MDS Simulator running prior debugging… So I launched the MDS simulator, everything loads properly but I get an “HTTP Error 403: Forbidden” – “Not authorized to access localhost:80”
- I would assume the debugger would have launched the MDS simulator automatically, but I guess it as to be launched manually… Is this correct?
- My demo site runs locally off my local IIS server the default port 80. When I launch the local site in my IE or Firefox browser, it runs fine. I’m assuming there is an MDS configuration that is not configured properly… but not certain which one.
Since we have a proxy server to external internet, I added the following configurations to the rimpublic.property file found in the … BlackBerry Email and MDS Services Simulators 4.1.4\MDS\config directory
application.handler.http.proxyEnabled = true
application.handler.http.proxyHost=[proxy server]
application.handler.http.proxyPort=[proxy port]
With these settings, I can now access internet site (www.google.com) via the BB simulator. - I’m a bit confused with the local web servers… VS.Net runs off local IIS for debugging purposes, but the MDS simulator runs on Tomcat, if I’m not mistaking… how are the http request routed? Which Web Servers handles my debugging session?
Thanks & your help is very well appreciated !
Joel
