AIR debug launcher doesn't start in CS5.5 - fixed

Just wanted to pass this on if anyone else runs into it...
After upgrading from CS5 to CS5.5, I ran my flash program for AIR 2.6 as normal, but the ADL (Air Debug Launcher) never opened.
(CS5.5 automatically changed the publish setting from AIR2.5 to 2.6)
It turns out the app-xml format had changed, and the ADL wouldn't open the air app due to an unrecognized format (I assume this was the problem).
Specifically, I changed
<version>1.1.0</version>
To
<versionNumber>1.1.0</versionNumber>
... and it started working!
You may also have to change
<application xmlns="http://ns.adobe.com/air/application/2.6">
At the top so '2.6' reflects the version of AIR you are targeting. In my case I had to change 2.5 to 2.6
Good luck

Thank you for pointing this problem out. I've had the same problem with alignment and snap. It is a most serious problem. After days and nights trying to solve it with no success, and no sleep, my thoughts and feelings alternated between never using Illustrator again and suicide or both. Deadline for a school project is getting too close, and my time is almost out, due to no warning signs of horrible changes in CS5. When points, lines and shapes never snap in place or align, Illustrator becomes entirely useless and life has no meaning. There should have been warning signs and notifications, printed on the software package, and in the booklet and everywhere, and still this new feature sucks. Why make it default with no warning? Does Adobe want to force its users into suicide? This is more dangerous than one may think. Otherwise Illustrator is so perfect and makes life very meaningful indeed.

Similar Messages

AIR Debug Launcher Does NOTHING in cs5?

Hi All,
Running Flash cs5, windows 7 64bit
I go to test my movie in Flash cs5 no actionscript errors etc.. but it just hangs.. air debug laucher doesn't launch.. nothing happens AT ALL..
as documented here: http://www.kirupa.com/forum/showthread.php?365822-Flash-CS5-Air-Debug-Launcher-issue
I was wondering if there is a fix because I really need this movie out!

Hi Alfo,
Have you updated to the latest version of Adobe Flash Pro CS5 Extension for AIR 2.5? I'm using version 0.9.99 and the path to ADL field is no longer present. I'm going to try and record a short video that walks through the steps involved, but I found that on Windows 7 I had to disable the firewall for my home network to get my phone to connect to the remote debugging session.
Chris

Flash CS5.5 - Test movie in AIR debug launcher (mobile)

Okay, so I have searched the web high and low and cannot find the answer to this so I'm really hoping someone could please help me on these forums.
I am trying to test an iPad app I'm making.
I'm using AIR for iOS in my publish settings and Actionscript 3.0 in Flash CS5.5
When I test movie in AIR debug launcher (mobile), none of the mobile actionscript is working, such as gestures or tap and drags... nothing.
I've watched a stack of videos on Adobe TV and it seems to be so easy.
Does anybody know what am I doing wrong? Am I just missing something here?
Any help would be greatly appreciated.
Cheers

Relaxatraja, thanks for trying to help me with this. I've tried testing for Android and for iOS... here's an example of a mobile code snippet that doesn't work in the AIR debug launcher for a contact_mc button I've made.
Multitouch.inputMode = MultitouchInputMode.TOUCH_POINT;
contact_mc.addEventListener(TouchEvent.TOUCH_BEGIN, fl_TouchBeginHandler);
contact_mc.addEventListener(TouchEvent.TOUCH_END, fl_TouchEndHandler);
var fl_DragBounds:Rectangle = new Rectangle(0, 0, stage.stageWidth, stage.stageHeight);
function fl_TouchBeginHandler(event:TouchEvent):void
event.target.startTouchDrag(event.touchPointID, false, fl_DragBounds);
function fl_TouchEndHandler(event:TouchEvent):void
event.target.stopTouchDrag(event.touchPointID);
Am I missing something? Do I need to import classes? Can I only test Multitouch and gestures on an actual device?
Thanks

AIR Debug Launcher Closes on Button Click in AIR for iOS test fla

Hi,
I'm working with a Flash CS5.5 AIR for iOS fla using AIR 3.0. Test Movie ---> AIR Debug Launcher (Desktop) worked as expected for a couple of weeks then suddenly began to malfunction. The debug launcher fires up correctly but anytime a button is clicked in the test movie, it closes (but does not shut down completely). I don't know if I've selected something by accident but I can't get it to stop. No problems testing in Flash Professional using an ordinary AS3 fla. Any ideas?
Thanks!

Relaxatraja, thanks for trying to help me with this. I've tried testing for Android and for iOS... here's an example of a mobile code snippet that doesn't work in the AIR debug launcher for a contact_mc button I've made.
Multitouch.inputMode = MultitouchInputMode.TOUCH_POINT;
contact_mc.addEventListener(TouchEvent.TOUCH_BEGIN, fl_TouchBeginHandler);
contact_mc.addEventListener(TouchEvent.TOUCH_END, fl_TouchEndHandler);
var fl_DragBounds:Rectangle = new Rectangle(0, 0, stage.stageWidth, stage.stageHeight);
function fl_TouchBeginHandler(event:TouchEvent):void
event.target.startTouchDrag(event.touchPointID, false, fl_DragBounds);
function fl_TouchEndHandler(event:TouchEvent):void
event.target.stopTouchDrag(event.touchPointID);
Am I missing something? Do I need to import classes? Can I only test Multitouch and gestures on an actual device?
Thanks

Macbook Pro Retina (July 2014) will not register TOUCH events when going through the AIR DEBUG LAUNCHER for MOBILE

I recently purchased a MACBOOK PRO with a retina screen and have started to transition to it as a primary work computer.
I have a game that is built on another Macbook Pro (non retina) that works fine in the AIR debug launcher for mobile but when I launch it from the RETINA device, the touch events seem to not register correctly.
Has anyone else experienced this issue?

To further clarify, it appears the touch simulator is cutting everything in half, maybe because of the pixel density?

Adobe AIR Debug Launcher has stopped working Error on Flash Builder 4.6

Hi,
Maybe you could help me out here as I’ve search the web and Adobe forum but could not find any answer.
I just installed Flash Builder 4.6 (after uninstalling 4.5.1), now when I run my app, the adl.exe crashes (error details below). I thought because I have an app that was created with 4.5, but then I created a new app with this version and it still crash. I have Windows 7 64-bit PC.
Thanks so much. Any help is greatly appreciated.
Error details:
Problem signature:
Problem Event Name:     APPCRASH
Application Name:     adl.exe
Application Version:     3.1.0.4880
Application Timestamp:     4eb7612e
Fault Module Name:     Adobe AIR.dll
Fault Module Version:     3.1.0.4880
Fault Module Timestamp:     4eb75fb9
Exception Code:     c0000005
Exception Offset:     000a8a5b
OS Version:     6.1.7600.2.0.0.256.48
Locale ID:     1033
Additional Information 1:     0a9e
Additional Information 2:     0a9e372d3b4ad19135b953a78882e789
Additional Information 3:     0a9e
Additional Information 4:     0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0×0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
And this is the crash log:
Version=1
EventType=APPCRASH
EventTime=129672424273270780
ReportType=2
Consent=1
ReportIdentifier=3f7d7727-1c55-11e1-a8fc-705ab656b183
IntegratorReportIdentifier=3f7d7726-1c55-11e1-a8fc-705ab656b183
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=adl.exe
Sig[1].Name=Application Version
Sig[1].Value=3.1.0.4880
Sig[2].Name=Application Timestamp
Sig[2].Value=4eb7612e
Sig[3].Name=Fault Module Name
Sig[3].Value=Adobe AIR.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=3.1.0.4880
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4eb75fb9
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000a8a5b
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.0\bin\adl.exe
UI[3]=Adobe AIR Debug Launcher has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.0\bin\adl.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\syswow64\USER32.dll
LoadedModule[5]=C:\Windows\syswow64\GDI32.dll
LoadedModule[6]=C:\Windows\syswow64\LPK.dll
LoadedModule[7]=C:\Windows\syswow64\USP10.dll
LoadedModule[8]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[15]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[16]=C:\Windows\system32\msi.dll
LoadedModule[17]=C:\Windows\syswow64\ole32.dll
LoadedModule[18]=C:\Windows\system32\IMM32.DLL
LoadedModule[19]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[20]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[21]=C:\Windows\syswow64\NSI.dll
LoadedModule[22]=C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.0\runtimes\air\win\Adobe AIR\Versions\1.0\Adobe AIR.dll
LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[24]=C:\Windows\system32\VERSION.dll
LoadedModule[25]=C:\Windows\system32\WINMM.dll
LoadedModule[26]=C:\Windows\system32\OLEACC.dll
LoadedModule[27]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[28]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[29]=C:\Windows\system32\MSIMG32.dll
LoadedModule[30]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[31]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_ 5.82.7600.16661_none_ebfb56996c72aefc\COMCTL32.dll
LoadedModule[32]=C:\Windows\syswow64\WININET.dll
LoadedModule[33]=C:\Windows\syswow64\urlmon.dll
LoadedModule[34]=C:\Windows\syswow64\iertutil.dll
LoadedModule[35]=C:\Windows\system32\mscms.dll
LoadedModule[36]=C:\Windows\system32\USERENV.dll
LoadedModule[37]=C:\Windows\system32\profapi.dll
LoadedModule[38]=C:\Windows\system32\Secur32.dll
LoadedModule[39]=C:\Windows\system32\DSOUND.dll
LoadedModule[40]=C:\Windows\system32\POWRPROF.dll
LoadedModule[41]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[42]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[43]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[44]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[45]=C:\Windows\system32\WINNSI.DLL
LoadedModule[46]=C:\Windows\system32\DNSAPI.dll
LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[48]=C:\Windows\system32\dbghelp.dll
LoadedModule[49]=C:\Windows\system32\uxtheme.dll
LoadedModule[50]=C:\Program Files (x86)\MMTaskbar\shellhook.dll
LoadedModule[51]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[52]=C:\Windows\system32\mlang.dll
LoadedModule[53]=C:\Windows\system32\dwmapi.dll
LoadedModule[54]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_ 6.0.7600.16661_none_420fe3fa2b8113bd\comctl32.dll
LoadedModule[55]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[56]=C:\Windows\system32\apphelp.dll
LoadedModule[57]=C:\Users\joel.badinas.ENTICENT\AppData\Roaming\Dropbox\bin\DropboxExt.14. dll
LoadedModule[58]=C:\Users\joel.badinas.ENTICENT\AppData\Roaming\Dropbox\bin\MSVCP71.dll
LoadedModule[59]=C:\Users\joel.badinas.ENTICENT\AppData\Roaming\Dropbox\bin\MSVCR71.dll
LoadedModule[60]=C:\Windows\system32\EhStorShell.dll
LoadedModule[61]=C:\Windows\system32\PROPSYS.dll
LoadedModule[62]=C:\Windows\system32\ntshrui.dll
LoadedModule[63]=C:\Windows\system32\srvcli.dll
LoadedModule[64]=C:\Windows\system32\cscapi.dll
LoadedModule[65]=C:\Windows\system32\slc.dll
LoadedModule[66]=C:\Windows\system32\credssp.dll
LoadedModule[67]=C:\Windows\SysWOW64\schannel.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Adobe AIR Debug Launcher
AppPath=C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.0\bin\adl.exe

Dear, I had the same problema.
Was the sandbox from firewall.
I disabled and worked.

Adobe AIR Debug Launcher has stopped working in League Of Legends

I am a player of League Of Legends,and I always get the crash with a message of "Adobe AIR Debug Launcher has stopped working" in the game lobby .This is annoying and affect me so much.
As I found ,the LOL client is using the AIR of 3.1.0.4880. i have tried to update the AIR to 3.4 and copy the file to the LOL folder,but it is useless .can someone help me to solve it?

I think this thread is talking about the issue you are facing:
http://forums.adobe.com/message/4517944#4517944
Hitomi

Adobe Air debug launcher has stopped working

Hi htere
I am constantly getting this error "Adove Air debug launcher has stopped working" at times on my League of Legends client. I have updated Adobe Air to the latest version and I even went ahead and made sure everything is ran as administrator.
http://i47.tinypic.com/33usf8i.jpg
Problem signature:
Problem Event Name:     APPCRASH
Application Name:     LolClient.exe
Application Version:     2.0.2.12610
Application Timestamp:     4c00573a
Fault Module Name:     Air.dll
Fault Module Version:     0.0.0.0
Fault Module Timestamp:     511c7eb4
Exception Code:     c0000005
Exception Offset:     00002e72
OS Version:     6.1.7601.2.1.0.768.3
Locale ID:     3081
Additional Information 1:     0a9e
Additional Information 2:     0a9e372d3b4ad19135b953a78882e789
Additional Information 3:     0a9e
Additional Information 4:     0a9e372d3b4ad19135b953a78882e789

This thread seems to have a lot of helpful answers: http://forums.adobe.com/message/5359944#5359944
specifically, a video recorded that covers most/all the issues: http://youtu.be/uX0mMgJUyG0
Hope this helps anyone else finding issues!

Adobe Air Debug Launcher a cessé de fonctionner... y a des logs ?

Moi j'ai une application AIR qui provoque sans doute un crash du Air Debug Launcher... mais comment débugger ??? Est-ce qu'il y a un log du Air Debug Launcher quelque part ?
J'utilise AIR 2.5 SDK sous windows 7 home familiale 64 bits.
Je ne suis pas sûr si l'application est fautive. Les crash surviennent a différents moments... Des fois, dès le démarrage de l'appli et aucun log ne sortent. Des fois, des logs sortent, puis il y a un crash.
Je viens de tester avec AIR 2.7 SDK. Il y a toujours des crashs.

That is what im getting from the windbg... but dont know to use it so much... does it help anybody ?

Air Debug Launcher

HI could someone help me setup the runtime directory for the AIR Debug Launcher?
I thought It would be just a case of...
adl -runtime C:\Program Files\Common Files\Adobe AIR\Versions\1.0
But I get the error "please use -runtime to specify the location of the runtime"
What am I doing wrong?
Thanks
Aidan

Have you tried putting quotes around the path to the runtime? it may be breaking because of the space in Program Files in your path.
Assuming you've got the right path to your runtime, you could try:
adl -runtime "C:\Program Files\Common Files\Adobe AIR\Versions\1.0"

Adobe Air 2.5 and AIR Debug Launcher (ADL) from AIR 1.5.3 SDK

I am having some issues with the differences between running my Air Desktop application with the ADL from within my IDE and actually running it as an packaged air application that is installed. Everything functions as it should in the IDE when run with ADL, but once it is packaged the drag and drop functionality no longer works correctly.
I was able to get this to work when Adobe Air 1.5 runtime was installed, instead of 2.5. I am aware that there were a lot of changes made with this last update, but I am unsure of how to proceed, as I am unable to debug the packaged air application to see what is actually happening.
One solution that I could see would be to install the Adobe Air 2.5 SDK and use that to debug with.
If anyone has any insight to why drag and drop works in the ADL and the runtime, your feedback would be much appreciated.
Also, I am using Flash Builder 4, with the Flex 3.5 SDK

Hi,
We have same problem. On AIR 2.0.4 the drag&drop works correctly but with version 2.5.1 is problem. Do you found some solution for it?
Thanx

Bridge CC doesn't start, how do I fix it?

Initial installation of Brige CC worked fine. Installed the Bridge CC Output Module with result that Bridge CC won't execute. Have uninstalled, used the Cleaner utility to reset the Creative Cloud App Tab, and then installed Bridge CC once again. Same result, doesn't execute. Spent about eight hours online while Adobe Tech-Rep tried to resolve the problem using screen and desktop sharing but his result was worse than mine because he uninstalled my Photoshop and Bridge CS6 applications without asking me and failed to fix Bridge CC.
Here's how I stand-
a. Bridge CC doesn't execute
b. I'll have to spend eight to twelve hours installing my PS 7.0 disk and all of the upgrade disks needed to get Photoshop CS6 and Bridge CS6 back on my deskop.
I'm a patience man and I realize that, so far, this misadventure has only cost me $9.99 for the first month of my Creative Cloud experience with Photoshop CC and Bridge CC,; not counting time lost serving my clients and reinstalling CS6 applications that didn't need to be uninstalled.
Come now, surely there's a corrective procedure that I can carry out that will resolve the problem and I don't mean "Uninstall Bridge CC and reinstall it."
Hello?

Brett
Awesome that you’re following up!
I had comments from people who had the same problem and cleared the problem by removing the module, so I’m comfortable with and confident in the fact that I wasn’t the only one experiencing this issue.
I run fully updated Win7-64bit (FYI, ASUS p6X58D-Premium motherboard, 6GB RAM, two MSI nVidia 460 1GB video cards driving four 21” monitors, Crucial SSD prime drive).
BTW, there is an error in the instructions you provide:
2.             Copy the Adobe Output Module folder (not the AOM_Package_[OS] folder) into the Bridge CC Extensions folder in the appropriate location:
        Windows 64-bit: C:\Program Files (x86)\Common Files\Adobe\Bridge CC Extensions
        Windows 32-bit: C:\Program Files\Common Files\Adobe\Bridge CC Extensions
This is exactly backwards for Windows, “. . . ‘Program File’ folders that are listed are for 32 bit and 64 bit version of Windows 7. The folder with (x86) is for 32 bit version.” The source for this info is Microsoft: http://answers.microsoft.com/en-us/windows/forum/windows_7-files/programs-files-vs-program -files-x86/7d631676-e688-472a-a1bb-eefccfeca6d7 and can be confirmed in myriad other places including the fourth paragraph at http://en.wikipedia.org/wiki/Program_Files. Rather a critical and basic error . . .
I’ve installed it correctly, putting the 64bit Bridge CC files in the proper (by Microsoft) subdirectory, and it seems to work.
Thanks for the info and for following up — that’s uncommon with Adobe in my experience, which started when Adobe started. It makes me happy that maybe Adobe is movign to being more proactive and responsive. Cheers!
Thanks,
Jerry
Fifth Street Designstrategic marketing & branding
Jerry Clifton Meek
voice 406.586.2341 • mobile/text 510.414.8035 • toll-free 866.256.8393
65 west kimberly court • bozeman • montana 59718-9182 usa
<http://www.fifthstreet.com/> www.fifthstreet.com

AIR 2.7 debug launcher crashing sometimes (AIR.Ordinal function)

Hi,
I've been experienced some crash with the AIR debug launcher 2.7 SDK under win7 home familial x64 bits.
I m writting a link to the original post with a windows crash dump file so the dev team can have a look.
http://forums.adobe.com/thread/885589?tstart=0
From what i saw debugging with windbg, the AIR!Ordinal function is calling by the end ntdll32!RtlIntegerToUnicodeString and its crashing. I should said that it is not calling it directly, but a call to AIR!Ordinal4 is finishing by a crash on ntdll32!RtlIntegerToUnicodeString, dont know why.
Can someone have a look ?
From what i see the crash dump isnt showing totally the same bug from my windbg session. But in both, the Ordinal function is called first.

Hello,
Thank you for reporting this. Would you be willing to open a bug and provide some sample code in addition to the dump files in your other post? I can then attach a symbolicated stack trace to our internal bug. This should allow you to see the progress we make and allow our engineering team to contact you with additional questions.
Thanks,
Chris
Ps. Does your app use database calls? From my initial inspection of the dmp it looks like some of the last AIR calls are in SQL.

Dreamweaver CS5 doesn't start, cannot find configuration file

Dreamweaver Could not locate the Resource file in the Configuration folder. This file is required to run Dreamweaver. Please reinstall the application.
Dreamweaver CS5 doesn't start due to the error message above.
Found the configuration folder but on my roaming profile on the server, not on C drive.
Note that I installed Dreamweaver on the second partition of the hard disk, not on C drive due to lack of space. Other Adobe CS5 software are running well such as Photoshop and InDesign.
I have tried to delete (after backup) the Configuration folder, as I read on this forum that it should be automatically recreated, but no success. Tried to copy the Configuration folder (in fact the entire Adobe folder) to the user profile on C drive, but no success.
On this PC, no previous version of Dreamweaver has been installed. However, I have used older versions on different computers, and there are in the Adobe folder on my roaming profile traces of CS4 and CS6.
Could you please advise?

Not sure which thread you have read on this forum but I suggest read this official document and then see if resolves any lingering problems.
<http://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver-cs4-cs5.html>
Good luck.

Help: Pointbase db doesn't start when launching SP4 portal

Hi,
I downloaded WL platform SP4 today and installed (before the installation I uninstalled SP2)in my laptop. When I launch the examples portal, the pointbase db doesn't start. I tried both SP2 and SP3 in my laptop and both worked. The error messages below are directly copied from the console. My understanding is the portal server startup will automatically start pointbase db (I didn't do any configuration yet). Anybody know the problem and solution?
My laptop config:
Win XP, SP2, 1.6 GHz, 1GB memory
I am the admin user.
Thanks a lot!!
Error messages from the launching console:
<Jul 6, 2005 6:00:54 PM PDT> <Warning> <JDBC> <BEA-001129> <Received exception w
hile creating connection for pool "cgPool": SQL-server rejected establishment of
SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
<Jul 6, 2005 6:01:28 PM PDT> <Warning> <JDBC> <BEA-001129> <Received exception w
hile creating connection for pool "portalPool": SQL-server rejected establishmen
t of SQL-connection. Pointbase Server may not be running on localhost at port 90
93.>
<Jul 6, 2005 6:01:34 PM PDT> <Alert> <JMS> <BEA-040052> <JMSServer "cgJMSServer"
store failed to open java.io.IOException: JMS JDBC store, connection pool = <cg
JMSPool-nonXA>, prefix = <weblogic>: connection pool does not exist.
java.io.IOException: JMS JDBC store, connection pool = <cgJMSPool-nonXA>, prefix
= <weblogic>: connection pool does not exist
at weblogic.jms.store.JDBCIOStream.throwIOException(JDBCIOStream.java:48
8)
at weblogic.jms.store.JDBCIOStream.checkPool(JDBCIOStream.java:1599)
at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:548)
at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
at weblogic.jms.backend.BEStore.open(BEStore.java:262)
at weblogic.jms.backend.BEStore.start(BEStore.java:151)
at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
at weblogic.jms.JMSService.addJMSServer(JMSService.java:2260)
at weblogic.jms.JMSService.addDeployment(JMSService.java:2031)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Depl
oymentTarget.java:337)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Dep
loymentTarget.java:597)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeploy
ments(DeploymentTarget.java:575)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(
DeploymentTarget.java:241)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMB
eanImpl.java:754)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl
.java:733)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(Configurat
ionMBeanImpl.java:509)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
60)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:15
28)
at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(Rem
oteMBeanServerImpl.java:988)
at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBean
ServerImpl.java:946)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:954)
at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanPro
xy.java:481)
at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(
ServerMBean_Stub.java:7691)
at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployment
s(SlaveDeployer.java:1304)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.j
ava:347)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resum
e(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
>

The exception doesn't tell me much more than the DB connection / pool couldn't connect to the db.
Sometimes solving these types of problems where it should work, this works everywhere else, so what could be wrong here... Let me suggest that you install a new domain using a new root directory. IE c:\bea814 and not reuse c:\bea.
I'm guessing that an essential script or property file was not overwritten by the 814 install.
JBTW, 814 pointbase is a new version and is run on a new port from prior 8.x versions, the new port is 9093, where prior versions was 9092.
A diag. is after you start via, startWebLogic.cmd, to open a DOS window and run this command:
netstat -an
Look for a LISTEN on port 9093
This would confirm that 814's pointbase is started and there's a configuration issue with the connection pools.
Good luck, curt

AIR debug launcher doesn't start in CS5.5 - fixed

Similar Messages

Maybe you are looking for