DirectoryServices Exception with Release Build

So I'm using DirectoryServices.AccountManagement to query information from AD. This works fine when running the application with the Visual Studio debugger (Debug config) but not with (Release). Similarly, starting the application from the .exe (Release,
Debug, or the Deployed application) results in throwing the same exception: System.DirectoryServices.AccountManagement.PrincipalServerDownException: The server could not be contacted. ---> System.DirectoryServices.Protocols.LdapException: The LDAP server
is unavailable.
What is it about starting the application in Visual Studio that allows the AD server to be reached but not when running directly from the built exe? Anyone familiar with this?
Thanks in advance.

Hi HarCom,
>> This works fine when running the application with the Visual Studio debugger (Debug config) but not with (Release).
When you debug your program with release, was there any error information about why it did not work? I think the link below might be useful to you:
# Debugging Release Mode Problems
http://www.codeproject.com/Articles/140/Debugging-Release-Mode-Problems
>> the same exception: System.DirectoryServices.AccountManagement.PrincipalServerDownException: The server could not be contacted. ---> System.DirectoryServices.Protocols.LdapException: The LDAP server is unavailable.
I think the links below might be useful to you：
# A note on SSIS and Active Directory
http://blogs.rolandsanidad.com/category/programming/c/
In addition, it would be helpful if you could share us more information about your program.
Best Regards,
Edward
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click HERE to participate the survey.

Similar Messages

Export release build failed with an error message: complilation failed while excuting : compile-abc

I updated air sdk from 4.0 to 16.0 beta to fix apple app store submitting bug. I can build the project and run it on simulator without any problem. But when I tried to export the ios release build, I got this error message: complilation failed while excuting : compile-abc.
I use commmand line to excute compile-abc.exe with the parameters that adt gives it, but it failed without any error message.
Here is the command line:
compile-abc.exe -mtriple=armv7-apple-ios -filetype=obj -sdk "C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.5\sdks\4.5.1 - air16\lib\aot/lib/avmglue.abc" -fields "C:\Program Files (x86)\Adobe\Adobe Flash Builder 4.5\sdks\4.5.1 - air16\lib\aot/lib/air-fields.arm-air.txt" -O3 -abc-file-list=E:\MyApp\bin-debug\AOTBuildOutput8184169967790207636.tmp\ABCFilesList.txt
There's a empty file AOTBuildOutput-0000001821_1821.o left in the command line workaroud path. I opened file AOTBuildOutput-0000001821.abc, but didn't get any clue. How can I trace this problem?

Still having similar issues - seems to be when I embed an image - but works for every release except for release build
Tried your work around but doesnt seem to make a different
[Embed(source = "/../assets/[email protected]")]
protected static const ATLAS_IMAGE:Class;
[Embed(source = "/../assets/[email protected]", mimeType = "application/octet-stream")]
protected static const ATLAS_XML:Class;
[Embed(source = "/../assets/iconMap.png")]
protected static const ATLAS_IMAGE_LOW_RES:Class;
[Embed(source = "/../assets/iconMap.xml", mimeType = "application/octet-stream")]
protected static const ATLAS_XML_LOW_RES:Class;
if(Starling.current.viewPort.width > 320)
atlas = new TextureAtlas(Texture.fromBitmap(new ATLAS_IMAGE(), false), XML(new ATLAS_XML()));
}else{
atlas = new TextureAtlas(Texture.fromBitmap(new ATLAS_IMAGE_LOW_RES(), false), XML(new ATLAS_XML_LOW_RES()));

Export release Build failed.

https://www.dropbox.com/s/kt6m03xmj5vee35/Aquarium.zip
Fast & Standard version is OK.
Error occurred while packaging the application:
Exception in thread "main" java.lang.NullPointerException
     at adobe.abc.Block.succ(Block.java:150)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
     at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs_visit_el(Algorithms.java:194)
          at adobe.abc.Algorithms.dfs_visit(Algorithms.java:204)
          at adobe.abc.Algorithms.dfs(Algorithms.java:214)
          at adobe.abc.GlobalOptimizer.sccp(GlobalOptimizer.java:4672)
          at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:3546)
          at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:2247)
          at adobe.abc.LLVMEmitter.optimizeABCs(LLVMEmitter.java:532)
          at adobe.abc.LLVMEmitter.generateBitcode(LLVMEmitter.java:341)
          at com.adobe.air.ipa.AOTCompiler.convertAbcToLlvmBitcodeImpl(AOTCompiler.java:533)
          at com.adobe.air.ipa.BitcodeGenerator.main(BitcodeGenerator.java:80)
Compilation failed while executing : ADT

Still having similar issues - seems to be when I embed an image - but works for every release except for release build
Tried your work around but doesnt seem to make a different
[Embed(source = "/../assets/[email protected]")]
protected static const ATLAS_IMAGE:Class;
[Embed(source = "/../assets/[email protected]", mimeType = "application/octet-stream")]
protected static const ATLAS_XML:Class;
[Embed(source = "/../assets/iconMap.png")]
protected static const ATLAS_IMAGE_LOW_RES:Class;
[Embed(source = "/../assets/iconMap.xml", mimeType = "application/octet-stream")]
protected static const ATLAS_XML_LOW_RES:Class;
if(Starling.current.viewPort.width > 320)
atlas = new TextureAtlas(Texture.fromBitmap(new ATLAS_IMAGE(), false), XML(new ATLAS_XML()));
}else{
atlas = new TextureAtlas(Texture.fromBitmap(new ATLAS_IMAGE_LOW_RES(), false), XML(new ATLAS_XML_LOW_RES()));

I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device

I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device (iPhone) using debug build. When running with a release build, the result handler is never called (nor is the fault handler called). Viewing the BlazeDS logs in debug mode, the call is received and send back with data. I've narrowed it down to what seems to be a data size issue.
I have targeted one specific data call that returns in the String value a string length of 44kb, which fails in the release build (result or fault handler never called), but the result handler is called as expected in debug build. When I do not populate the String value (in server side Java code) on the object (just set it empty string), the result handler is then called, and the object is returned (release build).
The custom object being returned in the call is a very a simple object, with getters/setters for simple types boolean, int, String, and one org.23c.dom.Document type. This same object type is used on other other RemoteObject calls (different data) and works fine (release and debug builds). I originally was returning as a Document, but, just to make sure this wasn't the problem, changed the value to be returned to a String, just to rule out XML/Dom issues in serialization.
I don't understand 1) why the release build vs. debug build behavior is different for a RemoteObject call, 2) why the calls work in debug build when sending over a somewhat large (but, not unreasonable) amount of data in a String object, but not in release build.
I have't tried to find out exactly where the failure point in size is, but, not sure that's even relevant, since 44kb isn't an unreasonable size to expect.
By turning on the Debug mode in BlazeDS, I can see the object and it's attributes being serialized and everything looks good there. The calls are received and processed appropriately in BlazeDS for both debug and release build testing.
Anyone have an idea on other things to try to debug/resolve this?
Platform testing is BlazeDS 4, Flashbuilder 4.7, Websphere 8 server, iPhone (iOS 7.1.2). Tried using multiple Flex SDK's 4.12 to the latest 4.13, with no change in behavior.
Thanks!

After a week's worth of debugging, I found the issue.
The Java type returned from the call was defined as ArrayList. Changing it to List resolved the problem.
I'm not sure why ArrayList isn't a valid return type, I've been looking at the Adobe docs, and still can't see why this isn't valid. And, why it works in Debug mode and not in Release build is even stranger. Maybe someone can shed some light on the logic here to me.

Export Release Build error - Exception in thread "main" java.lang.Error: Unable to find named traits

I've been developing an AIR application for Android and iOS. During development, I've run the application (in debug mode) in the desktop simulator as well as on an iPhone 4 and a Nook Tablet.
However, I recently tried to "Export Release Build" for iOS and hit the following error: (I've stripped out the package and class information in the error message below)
!ENTRY com.adobe.flexbuilder.project 4 43 2012-04-06 13:09:15.516
!MESSAGE Error occurred while packaging the application:
Exception in thread "main" java.lang.Error: Unable to find named traits: valid.package.path.here::ValidClassName
          at adobe.abc.Domain.resolveTypeName(Domain.java:231)
          at adobe.abc.Domain.resolveTypeName(Domain.java:148)
          at adobe.abc.GlobalOptimizer.sccp_eval(GlobalOptimizer.java:6665)
          at adobe.abc.GlobalOptimizer.sccp_analyze(GlobalOptimizer.java:5909)
          at adobe.abc.GlobalOptimizer.sccp(GlobalOptimizer.java:4628)
          at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:3514)
          at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:2215)
          at adobe.abc.LLVMEmitter.optimizeABCs(LLVMEmitter.java:526)
          at adobe.abc.LLVMEmitter.generateBitcode(LLVMEmitter.java:336)
          at com.adobe.air.ipa.AOTCompiler.convertAbcToLlvmBitcodeImpl(AOTCompiler.java:472)
          at com.adobe.air.ipa.BitcodeGenerator.main(BitcodeGenerator.java:82)
Compilation failed while executing : ADT
!STACK 0
java.lang.Exception
          at com.adobe.flexbuilder.project.internal.FlexProjectCore.createErrorStatus(FlexProjectCore. java:1019)
          at com.adobe.flexbuilder.util.logging.GlobalLogImpl.log(GlobalLogImpl.java:66)
          at com.adobe.flexbuilder.util.logging.GlobalLog.log(GlobalLog.java:52)
          at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionWizard.doPackage (ExportReleaseVersionWizard.java:283)
          at com.adobe.flexbuilder.exportimport.releaseversion.ui.ExportReleaseVersionWizard.performFi nish(ExportReleaseVersionWizard.java:152)
          at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
          at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
          at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
          at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240)
          at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
          at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465)
          at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270)
          at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974)
          at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613)
          at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
          at org.eclipse.jface.window.Window.open(Window.java:801)
          at com.adobe.flexbuilder.exportimport.releaseversion.ExportReleaseVersionAction$1.run(Export ReleaseVersionAction.java:97)
          at com.adobe.flexbuilder.exportimport.releaseversion.ExportReleaseVersionAction.run(ExportRe leaseVersionAction.java:103)
          at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
          at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
          at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionI tem.java:584)
          at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
          at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java :411)
          at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
          at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480)
          at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465)
          at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270)
          at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974)
          at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613)
          at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
          at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
          at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
          at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
          at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
          at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
          at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
          at com.adobe.flexbuilder.standalone.FlashBuilderApplication.start(FlashBuilderApplication.ja va:108)
          at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
          at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:110)
          at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:79)
          at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
          at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:597)
          at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
          at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
          at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
The class the error message is referring to is defined with a SWC that my project links to. However, I've even tried to define a class with that same name (and location) within my project and it still fails to find it.
Why am I able to Project->Clean and run this project within the desktop AIR player (or on the device in debug mode) but unable to export it as a release build?
I have found a couple of threads mentioning a similar error but none of them have been marked as resolved.

At this point I feel I am talking to myself, but I will share my work-around in case it helps another who may stumble across this post.
In my particular case, both my main AIR application and my ANE wrapper library were referencing the same external Flex library (same revision). Both projects had the library linkage set to merge. Changing the linkage to "External" on one of the 2 libraries (it doesn't seem to matter which) and leaving the other as "Merged into code" enabled the export to complete without the bizarre "Unable to find named traits" error.

IOS Export Release Build hangs with FB4.7

I recently updated to FB4.7 running AIR 3.4 on my Macbook Air under Lion 10.7.5.
My project contains a large number of embeded files and when debugging under FB4.6 I was often encountering Java Heap Errors and lots of out of memory errors. However, I was able to put up with those errors and still export working release builds.
Under FB4.7 I am able to compile DEBUG builds now without the problems I was having under FB4.6. However, when I attempt to export an iOS release build using the IDE under FB4.7 the process always just hangs (at Packaging 0%) and never completes (even after waiting hours).
If I create a small test project under FB4.7, I am able to export a release build successfully. So I believe my FB install is working.
I've tried bumping up the xms and xmx settings in the Flash Builder 4.7.ini file to 2048m, but that has made no difference to the problem.
I suspect that the large number of embeded files that I have in my project may be contributing to the problem. The embeded files are primarily all UI artwork as my app supports all the different iOS screen resolutions.
Short of restructuring my entire project to remove all the embeded files (which I really do not want to do at this point) is there anything else that can be done to get FB4.7 to succesfully export an iOS release build?

Hi Sanjay,
Thanks for the quick reply! Hereby the extra info:
1. -Xmx2048m
2. We are using ATF files with all three textures included (around 14 MB for @2x and 8 MB for @1x). We could exclude the DXT and ETC ones, but than we need to create them for all separately. Thereby we are not done with the project so the size will still increase, than it is a solution for a short time.
3. I just tried with the following results:
At the beginning it is giving some warnings:
Exception in thread "main" com.adobe.air.ipa.ProcessError: Assembler failed
          at com.adobe.air.ipa.AOTCompiler.launchProcess(AOTCompiler.java:271)
          at com.adobe.air.ipa.AOTCompiler.compileModule(AOTCompiler.java:1444)
          at com.adobe.air.ipa.AOTCompiler.compileBitcodeImpl(AOTCompiler.java:1342)
          at com.adobe.air.ipa.ASMGenerator.main(ASMGenerator.java:68)
Exception in thread "main" com.adobe.air.ipa.ProcessError: Assembler failed
          at com.adobe.air.ipa.AOTCompiler.launchProcess(AOTCompiler.java:271)
          at com.adobe.air.ipa.AOTCompiler.compileModule(AOTCompiler.java:1444)
          at com.adobe.air.ipa.AOTCompiler.compileBitcodeImpl(AOTCompiler.java:1342)
          at com.adobe.air.ipa.ASMGenerator.main(ASMGenerator.java:68)
Undefined symbols for architecture armv7:
After that, a lot of lines are shown with this at the end:
ld: symbol(s) not found for architecture armv7
Compilation failed while executing : ld64
Any idea?
Thanks,
Ben

Export Release Build - Problem with Server Settings

Hello, i have a big problem and i searched the whole day yesterday but didnt found an answer...
I started a Flex Mobile and PHP Project. The Project has a Data/Services included wich loads some customer from a database (sql)... for the first a
used Zend and try it local (http://localhost and used the htdocs Folder of Zend)... EVERYTHING WORKS PRETTY FINE... so NOW my problem
I wanted to export this project to a release build for my android phone... so the first warning of Flash Builder ist that the project ist currently configured to access data services from a local url. Before exporting the application, you may need to deploy your services to a remote server, then change the server root URL for your project. Click here to change server settings.
When i click the button i get the server setting.
Web root: C:\Program Files (x86)\Zend\Apache2\htdocs
Root URL: http://localhost
whe i change it now i get an eror:"The selected web root folder does not exist (i attached i screenshot of it).
i entered de domain of my server (i also tried the ip) at Root URL. And i think there ist a problem with the Web root...? i get scary

i know WHY Flashbuilder tells me that i have to change the setting when i deploy on the device
my problem ist that i got this error...
and the domain wich i have in the screenshot should only explain how i tried it...
i entered my server url (the real domain) and i entered the folder "app" wich i have created via ftp on my server...
BUT i also get this error (lik in the screenshot)
i think at ROOT URL i cant make lot mistakes .... http://myserver.de or the ip
but i think maybe my web root ist incorrect? i entered here the folder wich is directliy on my server...?
i dont know exactly but i got an error like in the screen

FB4: Release build fails with RSLs using FlexSDK 3.5

Flash Builder 4 (v 4.0.1.277662) fails, when trying to do a release build with the following simple project setup:
- Flash library project with a simple test class (using the 3.5 Flex SDK which ships with FB4)
- Flex project with simple mxml-application (using the same SDK)
The Library is linked as RSL
When you try to export the release build of the project, you´ll get an unspecified error.
In the log file, you can found:
java.lang.NoClassDefFoundError: flex2/tools/oem/OEMException$CircularLibraryDependencyException
With some google search, I found out, that the error occured with FB 4 beta und should be already fixed.
That´s for sure true with SDK 4.0 oder SDK 4.1, but not SDK 3.5 (remember: it´s the version, which ships with the FB itself !!!).
After scanning the jar´s of the SDK 3.5 and 4.0, I found out, that the following 3 files are missing in the flex-compiler-oem.jar in SDK 3.5:
- OEMException$CircularLibraryDependencyException.class
- OEMException.class
- OEMException_en.properties
Adding these files to the jar of the 3.5 SDK, the release build will be successfully exported.
We were absolutely disappointed after realizing this issue. This has cost a lot of working time and was frustrating too.
Is there another way to get this working, without changing the SDK files?
Greetings, Jörg

Not sure of any workarounds apart from one what you have already tried, but can you file a Flex SDK bug for this to be fixed in the current version.
Thanks
-Sunil

Release build error with ANE "AOT Compilation has failed while optimizing function"

I'm trying to use the ChartBoost ANE which can be downloaded here https://github.com/freshplanet/ANE-Chartboost
When I do an Ad-hoc release build It keeps crashing and giving me the error below when packaging for iOS. But if I do a debug build that's a "fast" or "standard" build it compiles fine, and I can even see the ads.
Why would it crash when doing a release build? Does this ANE need an update?
I'm using FB 4.7 and AIR 3.8. Specifically, Apache Flex 4.10 Air 3.8
If I remove this 1 line of the Chartboost ANE code "AirChartboost.getInstance().showInterstitial();", the release build compiles fine and I can put it on the test iOS device.
"Error occurred while packaging the application:
AOT Compilation has failed while optimizing function public::AdsHelper.showFullscreenAd
Exception in thread "main" java.lang.NullPointerException
at java.util.TreeMap.getEntry(TreeMap.java:324)
at java.util.TreeMap.containsKey(TreeMap.java:209)
at adobe.abc.GlobalOptimizer.sccp_eval(GlobalOptimizer.java:6150)
at adobe.abc.GlobalOptimizer.sccp_analyze(GlobalOptimizer.java:6019)
at adobe.abc.GlobalOptimizer.sccp(GlobalOptimizer.java:4733)
at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:3615)
at adobe.abc.GlobalOptimizer.optimize(GlobalOptimizer.java:2309)
at adobe.abc.LLVMEmitter.optimizeABCs(LLVMEmitter.java:534)
at adobe.abc.LLVMEmitter.generateBitcode(LLVMEmitter.java:343)
at com.adobe.air.ipa.AOTCompiler.convertAbcToLlvmBitcodeImpl(AOTCompiler.java:611)
at com.adobe.air.ipa.BitcodeGenerator.main(BitcodeGenerator.java:104)
Compilation failed while executing : ADT"

I just encountered this error when building ad-hoc package, say that:
Error occurred while packaging the application:
AOT Compilation has failed while optimizing function apackage::AClass.aFunction
After several tries It turns out that the error was because the function aFunction has a return before some other code (for testing). I commented the code after the return then the packaging works fine.
FYI.

Problem with Export Release Build

My App works fine in the emulator and with the Apple development certificates when installed on my iPad.
Today I created the correct distribution credentials (certificates, etc.) to get it ready for the App store.
I go through the "export release build" process and FB does its thing.
What happens next is that the green status bar never goes past 0%.
It just sits there for about 5 minutes then the "export release build" dialog window goes away.
I get no errors or alerts of any kind.
It does create an .IPA file, but when I try to load it on my iPad I get a "failed to install" error.
Any suggestions on what I can do?
thanks

i know WHY Flashbuilder tells me that i have to change the setting when i deploy on the device
my problem ist that i got this error...
and the domain wich i have in the screenshot should only explain how i tried it...
i entered my server url (the real domain) and i entered the folder "app" wich i have created via ftp on my server...
BUT i also get this error (lik in the screenshot)
i think at ROOT URL i cant make lot mistakes .... http://myserver.de or the ip
but i think maybe my web root ist incorrect? i entered here the folder wich is directliy on my server...?
i dont know exactly but i got an error like in the screen

Export release build with latest nightly build

I picked up a night build this week and I noticed when I export release build now I get a bunch of framework sdks and swc files. I need to build something I can email to my supervisors for them to play with the gui I am building. If I try to run the swf it says it does not have permission to access the required framework swf. Is there some way to give it permission to do this? When I did a nightly build with beta2, it created an all encompased swf that I could mail people.
Thanks for the input.

Hi,
You need to go into your project settings a set the flex build path to merge code.
David

Has anyone been able to release-build their app with TLF 2.0?

I can build a debug build of my app just fine. TLF 2.0 features are working. However, when I try to export a release build I get:
    No signed digest found in catalog.xml of the library, /Applications/Adobe Flash Builder 4/sdks/4.1.0_tlf2.0/frameworks/libs/framework.swc. Compile the library with -create-digest=true and try again.
    No signed digest found in catalog.xml of the library, /Applications/Adobe Flash Builder 4/sdks/4.1.0_tlf2.0/frameworks/libs/rpc.swc. Compile the library with -create-digest=true and try again.
    No signed digest found in catalog.xml of the library, /Applications/Adobe Flash Builder 4/sdks/4.1.0_tlf2.0/frameworks/libs/spark.swc. Compile the library with -create-digest=true and try again.
    No signed digest found in catalog.xml of the library, /Applications/Adobe Flash Builder 4/sdks/4.1.0_tlf2.0/frameworks/libs/sparkskins.swc. Compile the library with -create-digest=true and try again.
To get TLF 2.0 working I followed the steps on the blog plus I had to change the linkage for textLayout.swc to merged to code.
I tried to modify the build.xml script in the frameworks directory to call compute-digest="true", but it didn't seem to make any difference.
Has anyone gotten this to work?

I'm using ant. It looks like the command you gave me is for building the textLayout.swc. I already have the textLayout.swc from the sourceforge download. I'm looking for a way to integrate it into the 4.1.0 (or 4.0.0) sdk. I followed the instructions on the TLF blog post, including running the ant command to rebuild spark.swc. However, when I try to do a release build of my project using that modified sdk I get the error message in the first post.

Export release build fails with project created by Launchpad

When I try to export a release build (using Flash Builder 4.5) of a project created in Adobe Air Launchpad (p8_3-0-1_081911) I get the following error message:
"error occurred while saving the project settings: 'default' build target cannot be found for the selected project"
Is this a bug or am I doing something wrong? Any help/ideas would be greatly appreciated!
Rob

I solved this by creating a new project and copying everything across. But it was time-consuming work - especially creating all the new value objects and data services. Air Launchpad is a great concept and has helped me a lot, but this particular forum is dead.
Rob

Issue With Report Builder After Installing SP3 for SQL 2008 R2

Hello. We are experiencing an issue with Report Builder 3.0 since installing SP3 for SQL 2008 R2 over the weekend. You can no longer launch Report Builder from the Reporting Services URL (http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application
      Server  : Microsoft-HTTPAPI/2.0
      X-AspNet-Version: 2.0.50727
Application url   :
http://dicomweb/ReportServer/ReportBuilder/RptBuilder_3/MSReportBuilder.exe.manifest
      Server  : Microsoft-HTTPAPI/2.0
      X-AspNet-Version: 2.0.50727
IDENTITIES
Deployment Identity  : ReportBuilder_3_0_0_0.application, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86
Application Identity  : MSReportBuilder.exe, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86, type=win32
APPLICATION SUMMARY
* Online only application.
* Trust url parameter is set.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of
http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application resulted in exception. Following failure messages were detected:
  + File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [10/15/2014 9:35:56 AM] : Activation of
http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application has started.
* [10/15/2014 9:36:29 AM] : Processing of deployment manifest has successfully completed.
* [10/15/2014 9:36:29 AM] : Installation of the application has started.
* [10/15/2014 9:36:31 AM] : Processing of application manifest has successfully completed.
* [10/15/2014 9:36:35 AM] : Found compatible runtime version 2.0.50727.
* [10/15/2014 9:36:35 AM] : Detecting dependent assembly Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil using Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a,
processorArchitecture=msil.
* [10/15/2014 9:36:35 AM] : Detecting dependent assembly System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089,
processorArchitecture=msil.
* [10/15/2014 9:36:35 AM] : Request of trust and detection of platform is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [10/15/2014 9:36:43 AM] System.Deployment.Application.InvalidDeploymentException (HashValidation)
  - File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
   at System.Deployment.Application.ComponentVerifier.VerifyComponents()
   at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification
notification, DownloadOptions options)
   at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
   at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
   at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Hi DMcGarveyt,
This is an known issue in SSRS 2008 R2 SP3. For this issue, Microsoft has published an article addressing this issue. It is not planning to release a fix for this defect. But there's workarounds for this issue. Please refer to the link below:
Report Builder of SQL Server 2008 R2 Service Pack 3 does not launch.
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Not using the most recent checked in version of the web app DLL in Release build

Hi folks
Got some peculiar behaviour - I have three build configurations set up within VS2K13 for Debug, Release and DebugOnLive.
There are some basic XML transformations to update emails, db-settings etc - all very simple and working.
Needed to do a DebugOnLive build to test an emergency fix and everything built fine. Tested on the pilot site, saw the fix was working and proceeded to rebuild for Release.
Everything seemed great except the web-app DLL with the fix in that was used for the release build was not the latest version even though the pilot build had used the latest version. I had to recheck in the DLL to get it to use the updated version!
Is this behaviour 'by design' - it seems peculiar you would have to re-check in to change the build if all you are doing is swapping some settings? You are fixed - all you are doing is building for a different configuration or am I misunderstanding?
mmacneill123 (MCP)

Hi Mmacneill123,
Thanks for your reply.
You said that “the issue is that I have already checked in the changes…”, and you said “if I check in before
EVERY build, everything works fine!” too.
You’re using the default build process template in your build definition? You configured these 3 configurations in your build definition to build your solution 3 times?
If you remove that DebugForLive configuration, only configure Debug and Release in your solution and build definition to perform build, everything will works fine?
After you changed the configuration from “DebugForLive” to Release, please check in on your solution first, then queue build definition to build your solution. After you changed the configuration each time, please check-in on your solution first,
then perform build.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

DirectoryServices Exception with Release Build

Similar Messages

Maybe you are looking for