App builder problem with Fuzzy Toolkit

Hi,
today I wanted to build an app (using LV2009) with some functions from "PID and Fuzzy Control Toolkit".
Now the app builder is searching for a type definition in vi.lib (as shown in the pic), but it doesn't find the CTL file - but the path used for searching is correct! Then I do the search manually, point to the requested CTL in the correct place (and with correct name of course), and the build will succeed.
What's up here?
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome
Solved!
Go to Solution.
Attachments:
check.png ‏18 KB

Hi,
thanks for your thoughts!
Answers:
- I use WinXP SP3, German settings
- I use LV2009SP1 for that project, toolkits are installed with that version (other LabVIEW versions are installed too, from LV8.5.1 to LV2010SP1)
- LabVIEW is installed in the "standard" path on drive C: (as can be seen on the attached pic of message #1)
- the app builder is unable to find the ctl file (the standard search dialog pops up), but the file is located on exactly the path used for searching (as can be seen on the picture)
- all I have to do (but this really annoys me) is to point LabVIEW to an item in a place it already knows...
- the type definition is part of the toolkit, it's installed/located in the standard folder of that toolkit, and I never changed/touched any path or file name
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Similar Messages

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

App build problem.

I am trying to build an application using Wavelet transforms (Signal
Processing Toolkit) with LabVIEW ver 7.
I wish to include the run-time files on disk along with executable, but
not actually have to install run-time engine on the target machine.
When I try to run said executable on target machine, it fails to load
upon not finding LVSPT.dll.
If I force LVSPT.dll by adding it as a support file or simply placing it
in required directory, I get ERROR...
"An error occured loading VI 'Read Filter Bank Coefficients.vi' LabVIEW
load error code 21: An external subroutine required for execution could
not be found"
This happens for Read Filter Bank Coefficients.vi, Decimation Filter.vi
and Interpolation Filter.vi. All else seems well.
Any suggestions.

Hello Guig,
Thank you for posting to the NI Discussion Forums. I am unaware of any “resource.dll” that is
needed for the toolkit. If this is
related to the above posts, the files needed for building an application with
the toolkit are outlined here (http://digital.ni.com/public.nsf/websearch/5ED3D385E2D3AAFA86256DAB00775919?OpenDocument).
You mentioned reinstalling LabVIEW, but
if the problems appear with toolkit VIs you
might want to consider reinstalling the toolkit. Make sure that when you remove the toolkit
you do so through Windows control panel in add/remove programs. Could you also provide us with some
additional information on the problem – such as software version information
(i.e. what version of LV,
what version of the toolkit, etc…), as well as some screenshots of any errors
you are encountering?
Hopefully we can help you to resolve this problem. Please let me know if you have any additional
information.
Travis M
LabVIEW R&D
National Instruments

Linux app builder hangs with daqmxbase 1.5.0-f2

Having a problem building apps on linux using daqmxbase 1.5.
Test machines are:
A fresh installation of Suse 9.2 (kernel 2.6.8) on a Dell SC420 to which I added Labview 7.1, Appbuilder and daqmxbase 1.5.0-f2. Building our app fails on the "Copying files to application" part - the progress bar hangs at about 40% complete. The Labview windows become unresponsive, disk i/o stops and the process has to be killed.
I tried building some of the NI examples to pin down a possible issue with our vi but the same thing seems to happen with any example that has a daq component.
Normalize Waveform example - builds and runs fine
Signal generation and processing example - builds and runs fine
Our app - hangs
USB-6008/9 Interactive Control Panel - hangs
Count digital events buffered continuous ext clk example - hangs
In case there was an issue with Suse or 2.6.8 I tried a fresh install of Redhat 9 (2.4.20) on a different box, added labview, appbuilder, daqmxbase 1.5 and the same thing happens - the builder hangs.
Figuring that the builder might need some hardware in order to build an app properly I also gave it a shot with a USB 6009 plugged in - same result.
Being new to labview I'm unsure whether there are any specific log files I can provide that will help track down this problem - /var/log/messages has nothing.
Any ideas?

I've tried different kernels (the machines are P4 w/HT so the installer defauls to an smp kernel). Currently running linux 2.6.8-24.10-default #1 Wed Dec 22 11:54:27 UTC 2004 i686 i686 i386 GNU/Linux. I've tried various other smp and non-smp kernels.
I've uninstalled and reinstalled Labview, app builder and daqmxbase in various sequences. I've even reinstalled the entire Suse 9.2 OS and played with various grub and BIOS options. I've tried with the vanilla OS install and after applying the available patches through YaST.
I should point out that the app runs fine in Labview itself and compiles without errors on Windows.
There were no errors reported when installing Labview or daqmxbase and nothing in the system log.
I'm at a complete loss. The app builder fails every time, on different boxes, and it 100% reproducable.
I guess I'll give Mandriva 10 a try. In the meantime.... help! Message Edited by PaulSmith on 06-17-2005 11:52 AM
Message Edited by PaulSmith on 06-17-2005 11:52 AM

App Store problem with update???

I have a problem with the app store. I have to update the application badge twitter. Twitter is not installed. When I click on update in the User ID field is already entered an email address that is strange to me. When i enter information for my ID and pass, i get an error on the app store. I can not install the tweeter nor do I delete a notification of the update.

https://discussions.apple.com/docs/DOC-5261

I am no longer being asked for a password when downloading an app, big problem with kids

I am no longer being asked for a password when downloading an app or music in iTunes, big problem with kids. How do I enable

To elaborate further, in those restrictions you can specify exactly what types of actions you would like to restrict.
I think you'll find this accomplishes your objective.

LabVIEW 8.5.1 Build Problem With LV2010 Installed

I am experiencing a problem when building an application installer using LabVIEW 8.5.1. I have built this application many time before but since installing LabVIEW 2010 I can no longer build the installer.
I have tried to buiuld the application on a Windows 7 PC and a Windows XP machine. My minimum requirment in my build options was Windows 2000, I changed that to XP but it made no difference.
I get the following error message:
CDK_Build_Invoke.vi.ProxyCaller >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_Build.vi >> NI_MDF.lvlib:MDFDistCopyList_GetCount.vi
Loading product deployment information
Adding files to installer
*** WARNING ***
Cannot enforce the requested minimum operating system restriction because the deployment engine only supports Windows XP or later. Resetting minimum restriction to Windows XP or later.
Done adding files
Preparing to build deployment
Copying products from distributions
*** Error: Fatal runtime error. (Error code -10)
*** Error Details:
Error in MDF API function: _MDFDistCopyList_GetCount
Access violation! Structured exception code 3221225477
*** End Error Report
Done building deployment
Has anyone else come across this?
Thanks in advance.

Thanks Andrew.
It didn't help. After three days of trying, I did get one system to build without error. I'm currently trying to get another system to build.
It looks like the Access violation is caused by the deployment utility not asking to change to DVD 3 for CVI after the product caches has been cleared (To fix the error code -40 problem). Restoring the CVI runtime (NI LabWindows_CVI 2009 Service Pack 1 Run-Time Engine [9.1.1450]) to the Product Cache seems to fix the problem.
The status log doesn't show enough information to figure out the problems. Looking at the end of the Detailed_Installer.log is pretty much manditory.
My recomendation is to build first with "Install TestStand Engine" and the various "Driver and Components..." turned off and then slowly enable the ones wanted.
Also, it saves a lot of pain and suffering to do at least one deployment with "Copy Installers to Product Cache by Default" turned on before doing an upgrade so you don't have to go search for old DVD's.
After a lot of trial and error, I believe these are the steps I went through to finally get it to work:
1. Close TestStand, LabView, and Deployment Utility
2. Delete all in C:\Program Files\National Instruments\Shared\ProductCache, except the CVI Runtime
3. Delete all in C:\Documents and Settings\All Users\Application Data\National Instruments\MDF\ProductCache, except runtime 7.1.1
There seems to be something wrong with the .NET language pack installation. It always seems to generate errors.
3. Run DotNet20x86langpack.msi on the Device Driver DVD at Products\DotNet20langpack_x86_Installer\ and uninstall.
4. Run DotNet20x86langpack.msi and install.
5. Put DVD 1 back in.
Got an error with the .Net installer so. . .
6. Uninstall at D:\Distributions\LV\Products\DotNet20_x86_Installer\DotNet20x86
7. Install at D:\Distributions\LV_SE\Products\DotNet20_x86_Installer\DotNet20x86
8. Again Install at D:\Distributions\LV\Products\DotNet20_x86_Installer\DotNet20x86
9. Run TestStand, LabView (if using VI's), and the Deployment Utility.
Runtime 8.5.1 should install automatically and ask to reboot the system. Go ahead reboot and run Teststand, etc. again.
10. In global settings, 'clear prompt before'. . . , and select 'copy installers to product cache by default'
11. On Installer Options tab, clear "Install TestStand Engine".
12. Build - ALWAYS 'remove all files from this folder before building'
It "should" build. If not, fix any errors.
12. Select Install TestStand Engine.
13. Select Engine Options... and clear all check boxes (except runtime 7.1.1)
14. Build again (make sure DVD 1 is in)
15. Install other Engine Options, Drivers and Components.
16. Build again (make sure DVD 1 is in)

Build problem with Hello1 example.

Hi,
I have installed j2ee1.4 and trying to run the j2eetutorial1.4
I am facing a problem in building the hello1 example.
1) When I build the hello1 example, the build fails with the following error message
C:\java-works\j2eetutorial14\examples\web\hello1>asant build
Buildfile: build.xml
init:
prepare:
copy:
build:
[javac] Compiling 2 source files to
C:\java-works\j2eetutorial14\examples\we
b\hello1\build
BUILD FAILED
file:C:/java-works/j2eetutorial14/examples/web/hello1/build.xml:52:
C:\java-work
s\j2eetutorial14\examples\web\hello1\${j2ee.home}\lib not found.
Total time: 1 second
2)) Editing the build.proerties file to include the j2ee.home property.When I save the file it gets a .txt extension.Could this cause a problem , while I try to build the examples? if so How can I avoid this?
Could anyone please help me in this?
Thanks,
Ann

To save the file without .txt extension
just enclose the file with double quotes
"build.properties" in the File save dialog box

Build problem with Maven

Hi.
I have upgraded from 1.5 APT to the 1.6 method of doing compile time annotations, and I am runing into a problem trying to build a jar containing my annotations processor.
I get the error from maven (mvn package)
[INFO] Compilation failure
error: Bad service configuration file, or exception thrown while constructing Processor object: javax.annotation.processing.Processor: Provider annotations.processing.processors.CodeAnnotationProcessor not found
I have the following directory structure
src
--main
----java
------annotations
--------processing
----------processors
------------CodeAnnotationProcessor.java
----------annotations
------------CodeAnnotation.java
----resources
------META-INF
--------service
----------javax.annotation.processing.Processor
I build this with the following with maven
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>mygroup</groupId>
    <artifactId>annotations-processor</artifactId>
    <packaging>jar</packaging>
    <version>1.0.0</version>
    <name>annotations-processor</name>
    <url>http://maven.apache.org</url>
    <dependencies>
        <dependency>
            <groupId>com.sun</groupId>
            <artifactId>tools</artifactId>
            <version>1.4.2</version>
            <scope>system</scope>
            <systemPath>C:/Java/jdk1.6.0_10/lib/tools.jar</systemPath>
        </dependency>
    </dependencies>
    <build>
        <plugins>
            <plugin>
                <artifactId>maven-compiler-plugin</artifactId>
                <configuration>
                    <source>1.6</source>
                    <target>1.6</target>
                </configuration>
            </plugin>
        </plugins>
    </build>
</project>The javax.annotation.processing.Processor file contains
annotations.processing.processors.CodeAnnotationProcessorAny my
package annotations.processing.processors;
import javax.annotation.processing.AbstractProcessor;
import javax.annotation.processing.RoundEnvironment;
import javax.annotation.processing.SupportedSourceVersion;
import javax.annotation.processing.SupportedAnnotationTypes;
import javax.lang.model.element.TypeElement;
import javax.lang.model.SourceVersion;
import java.util.Set;
@SupportedAnnotationTypes(
        "annotations.processing.annotations.CodeAnnotation")
@SupportedSourceVersion(SourceVersion.RELEASE_6)
public class CodeAnnotationProcessor extends AbstractProcessor {
    public boolean process(Set<? extends TypeElement> annotations,
                           RoundEnvironment roundEnv) {
        return true;
}And my CodeAnnotation is as follows
package annotations.processing.annotations;
import java.lang.annotation.Target;
import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
@Target(ElementType.TYPE)
@Retention(RetentionPolicy.SOURCE)
public @interface CodeAnnotation {
}

Milesy wrote:
Hi.
I have upgraded from 1.5 APT to the 1.6 method of doing compile time annotations, and I am runing into a problem trying to build a jar containing my annotations processor.
I get the error from maven (mvn package)
[INFO] Compilation failure
error: Bad service configuration file, or exception thrown while constructing Processor object: javax.annotation.processing.Processor: Provider annotations.processing.processors.CodeAnnotationProcessor not foundFor me it worked when I used the settings
<plugins>
<plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-compiler-plugin</artifactId>
      <configuration>
        <source>1.6</source>
        <target>1.6</target>
        <fork>true</fork>
        <executable>${java.home}/../bin/javac</executable>
        <compilerArgument>-proc:none</compilerArgument>
      </configuration>
    </plugin>
</plugins>
...Forking the compiler is perhaps not the best option, but its just for the annotation processor.

Hi! Missing disk utility apps and problems with external disc

Hi everybody! after installing snow leopard, as a way to get to lion, I dont have the disk utility apps.
Besides Im having a lot of problems with an external new Toshiba 1T disc that I try to use with Time machine cause I daily receive the OSX msg CANT REPAIR THE DISK REFORMAT IT!
Thanks a lot to all of the community
I do love Apple product. And counting the days for the iOS 6 upgrade!!

hugorodri wrote:
Hi everybody! after installing snow leopard, as a way to get to lion, I dont have the disk utility apps...
Before you go to Lion, just a reminder. I know you recently moved up to Snow Leopard. Be sure that everything you were running in Leopard, and now in SL, will work for you in Lion.
Remember, Rosetta and all PPC apps are gone (Word 2004, some versions of PhotoShop etc) Check the compatibility list before you ditch SL.
As far as your Disk Utility problem, how hard is it to reinstall SL?
I've taken a screen shot of my Utilities folder to show you what you are looking for. The Utilities folder as mentioned above is in the Aplication Folder (or you may have pulled it out to the side bar as well, in which case there will be an icon and the word Utilities in Places in the side bar.
Mrs H

Build problem with FlexBuilder 3 Plugin

Hi,
I am using the FlexBuilder 3 plugin with Eclipe Europa. I created a Flex project with J2EE backend and WTP support, so that I have both the Flex stuff and the J2EE stuff within the same project. I imported some mxml, as, and java files I had, and I was able to build and run my app using the default Eclipse build/deploy process. Everything worked except the BlazeDS (messagebroker servlet) part, so I decided to delete the Tomcat server (the Eclipse proxy of it), and start again with a new server config.
This somehow totally broke the build process. Some of the new config used port 8080 instead of 8400. And the only part of my app that was correctly deployed was the java files in the src folder. Properties files were not deployed, jar files were not deployed, even web.xml was not deployed.
After copying files manually into the Eclipse Tomcat proxy, everything worked fine, including object remoting and HTTPService invocation.
Can anyone share their experience with the FlexBuilder plugin for java webapps? What is the correct way to set it all up?
Thanks,
Miguel

Milesy wrote:
Hi.
I have upgraded from 1.5 APT to the 1.6 method of doing compile time annotations, and I am runing into a problem trying to build a jar containing my annotations processor.
I get the error from maven (mvn package)
[INFO] Compilation failure
error: Bad service configuration file, or exception thrown while constructing Processor object: javax.annotation.processing.Processor: Provider annotations.processing.processors.CodeAnnotationProcessor not foundFor me it worked when I used the settings
<plugins>
<plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-compiler-plugin</artifactId>
      <configuration>
        <source>1.6</source>
        <target>1.6</target>
        <fork>true</fork>
        <executable>${java.home}/../bin/javac</executable>
        <compilerArgument>-proc:none</compilerArgument>
      </configuration>
    </plugin>
</plugins>
...Forking the compiler is perhaps not the best option, but its just for the annotation processor.

Flex 3 App having problems with Vista/Flash10

Hello Forum Folks,
I have a small little wizard/form app in Flex 3.0 that runs wonderfully in Flash 9 on a Windows XP box. However, when I try to run it on a Vista/Flash 10 box, the VBox that contains the wizard is a blank screen. I get the blank screen only when I return to the wizard from being in it previously (while staying inside the Flex app). I can see that the wizard code is pulling data from my server with no problem when the blank screen occurs. However, the browser (I'm using Firefox 3.0.1) states that it is still downloading data from my server. Using HttpFox I can see that all requests to server are answered with an HTTP 200 (OK) response, so I don't think it's the server/client communication....
Anyone run into this before? Any idea on how to force the VBox to display or refresh? I've tried invalidateDisplayList - but no positive results.
Thanks in advance,
--Andy

Not really a solution but a work-around for the problem: When I revisist the wizard, I made the handle holding the wizard equal to null, then created a new wizard and re-attached it as a child:
this.wizardHandle = null;
this.wizardHandle = new WizardApp();
this.addChild(this.WizardHandle);
This kept the blank screen from appearing... which is good, but doesn't fix the underlying problem... whatever that happen to be. So if anyone still has a guess I would be glad to hear it.
Thanks,
Andy

App Store problem with Yosemite

After installing Yosemite, the App Store told me I had 5 updates waiting:
In a box by itself at the top, it showed iTunes.
Then in a single box below it, it listed: iPhoto, Pages, Numbers, and Keynote.
I clicked "update all" and it started at the bottom of the list, and worked upwards to iPhoto. For the bottom three I got a message in red saying it couldn't do the update, I should go to the "Purchases" page for the update. Then it stopped on iPhoto.   I left the mac for over an hour, and when I returned, the spinning cursor was still spinning, and nothing else had happened. I quit the App Store and rebooted so that nothing else was running, and started App Store again. It still tells me that I have 5 updates, but now the "Updates" window is empty, and once again App Store has stopped responding.
I'm assuming there is a config file somewhere that's messed up, but I have no idea how to fix it.
Help, please!
Walt

Thanks, Linc. Logs follow:
10/20/14 4:16:14.300 PM Dock[353]: LaunchPad: __53-[LPAppManager(StoreSupport) _acceptStoreConnection:]_block_invoke app store xpc message error: Connection invalid
10/20/14 4:19:30.405 PM App Store[1693]: Unknown class 'FRPageController', using 'NSObject' instead. Encountered in Interface Builder file at path /System/Library/PrivateFrameworks/StoreUI.framework/Resources/Base.lproj/FRStor eViewController.nib.
10/20/14 4:19:30.407 PM App Store[1693]: Failed to connect (delegate) outlet from (NSObject) to (FRNavigationController): missing setter or instance variable
10/20/14 4:19:30.407 PM App Store[1693]: Failed to connect (view) outlet from (NSObject) to (FRWindowBackgroundView): missing setter or instance variable
10/20/14 4:19:30.407 PM App Store[1693]: Failed to connect (pageController) outlet from (FRNavigationController) to (NSObject): missing setter or instance variable
10/20/14 4:19:30.622 PM App Store[1693]: NSWindow warning: adding an unknown subview: <_NSThemeCloseWidget: 0x60000019a000>
10/20/14 4:19:30.625 PM App Store[1693]: Call stack:
    0   AppKit                              0x00007fff9289eb2c -[NSThemeFrame addSubview:] + 107
    1   AppKit                              0x00007fff9228dc6f -[NSView addSubview:positioned:relativeTo:] + 208
    2   StoreUI                             0x000000010eb6a13a -[FRWindow handleToolbarViewChangedNotification:] + 1085
    3   CoreFoundation                      0x00007fff93826cbc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
    4   CoreFoundation                      0x00007fff937181b4 _CFXNotificationPost + 3140
    5   AppKit                              0x00007fff92209bb9 -[NSView _postFrameChangeNotification] + 422
    6   AppKit                              0x00007fff92208bc6 -[NSView setFrameOrigin:] + 862
    7   StoreUI                             0x000000010eb69fc0 -[FRWindow handleToolbarViewChangedNotification:] + 707
    8   StoreUI                             0x000000010eb69b54 -[FRWindow setToolbar:] + 183
    9   App Store                           0x000000010eb3415f App Store + 8543
    10 AppKit                              0x00007fff9241f727 -[NSWindowController _windowDidLoad] + 586
    11 AppKit                              0x00007fff924068e2 -[NSWindowController window] + 110
    12 App Store                           0x000000010eb339d8 App Store + 6616
    13 CoreFoundation                      0x00007fff93826cbc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
    14 CoreFoundation                      0x00007fff937181b4 _CFXNotificationPost + 3140
    15 Foundation                          0x00007fff8b87dea1 -[NSNotificationCenter postNotificationName:object:userInfo:] + 66
    16 AppKit                              0x00007fff921d13c7 -[NSApplication finishLaunching] + 440
    17 AppKit                              0x00007fff921d0e91 -[NSApplication run] + 128
    18 AppKit                              0x00007fff921bc524 NSApplicationMain + 1832
    19 libdyld.dylib                       0x00007fff9a0df5c9 start + 1
    20 ???                                 0x0000000000000001 0x0 + 1
10/20/14 4:20:31.784 PM App Store[1693]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6000002e7380 {NSUnderlyingError=0x608000445bb0 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/featur ed.pdf, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/featur ed.pdf, NSLocalizedDescription=The request timed out.}
10/20/14 4:20:31.785 PM App Store[1693]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6000002e0880 {NSUnderlyingError=0x608000440c30 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/top.pd f, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/top.pd f, NSLocalizedDescription=The request timed out.}
10/20/14 4:20:31.785 PM App Store[1693]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6000000ff000 {NSUnderlyingError=0x608000446510 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/catego ries.pdf, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/catego ries.pdf, NSLocalizedDescription=The request timed out.}
10/20/14 4:20:31.787 PM App Store[1693]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6000002efb80 {NSUnderlyingError=0x60800044ce10 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/purcha sed.pdf, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/purcha sed.pdf, NSLocalizedDescription=The request timed out.}
10/20/14 4:20:31.788 PM App Store[1693]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6000002efd80 {NSUnderlyingError=0x608000258d50 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update s.pdf, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update s.pdf, NSLocalizedDescription=The request timed out.}
10/20/14 4:20:31.789 PM App Store[1693]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6000002eec00 {NSUnderlyingError=0x608000258540 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update -x.pdf, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update -x.pdf, NSLocalizedDescription=The request timed out.}
10/20/14 4:20:31.792 PM App Store[1693]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6000002eeb80 {NSUnderlyingError=0x6080002584b0 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update -xx.pdf, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update -xx.pdf, NSLocalizedDescription=The request timed out.}
10/20/14 4:20:31.793 PM App Store[1693]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6000002efd00 {NSUnderlyingError=0x608000258480 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update -xxx.pdf, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update -xxx.pdf, NSLocalizedDescription=The request timed out.}
10/20/14 4:22:34.047 PM App Store[1693]: <NSXPCConnection: 0x60800011d640> connection to service named com.apple.storeassetd: Warning: Exception caught during decoding of received reply to message 'startAdoptionEligibilityCheckWithReplyBlock:', dropping incoming message and calling failure block.
Exception: Exception while decoding argument 1 (#2 of invocation):
<NSInvocation: 0x608000677cc0>
return value: {v} void
target: {@?} 0x0 (block)
argument 1: {c} 0 ''
argument 2: {@"NSDictionary"} 0x0
Exception: value for key 'NS.objects' was of unexpected class 'NSError'. Allowed classes are '{(
    NSData,
    NSString,
    NSArray,
    NSDictionary,
    NSDate,
    NSNumber,
    NSNull
10/20/14 4:29:09.606 PM App Store[1720]: Unknown class 'FRPageController', using 'NSObject' instead. Encountered in Interface Builder file at path /System/Library/PrivateFrameworks/StoreUI.framework/Resources/Base.lproj/FRStor eViewController.nib.
10/20/14 4:29:09.608 PM App Store[1720]: Failed to connect (delegate) outlet from (NSObject) to (FRNavigationController): missing setter or instance variable
10/20/14 4:29:09.608 PM App Store[1720]: Failed to connect (view) outlet from (NSObject) to (FRWindowBackgroundView): missing setter or instance variable
10/20/14 4:29:09.608 PM App Store[1720]: Failed to connect (pageController) outlet from (FRNavigationController) to (NSObject): missing setter or instance variable
10/20/14 4:29:09.706 PM App Store[1720]: NSWindow warning: adding an unknown subview: <_NSThemeCloseWidget: 0x608000192210>
10/20/14 4:29:09.709 PM App Store[1720]: Call stack:
    0   AppKit                              0x00007fff9289eb2c -[NSThemeFrame addSubview:] + 107
    1   AppKit                              0x00007fff9228dc6f -[NSView addSubview:positioned:relativeTo:] + 208
    2   StoreUI                             0x0000000105a1c13a -[FRWindow handleToolbarViewChangedNotification:] + 1085
    3   CoreFoundation                      0x00007fff93826cbc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
    4   CoreFoundation                      0x00007fff937181b4 _CFXNotificationPost + 3140
    5   AppKit                              0x00007fff92209bb9 -[NSView _postFrameChangeNotification] + 422
    6   AppKit                              0x00007fff92208bc6 -[NSView setFrameOrigin:] + 862
    7   StoreUI                             0x0000000105a1bfc0 -[FRWindow handleToolbarViewChangedNotification:] + 707
    8   StoreUI                             0x0000000105a1bb54 -[FRWindow setToolbar:] + 183
    9   App Store                           0x00000001059ed15f App Store + 8543
    10 AppKit                              0x00007fff9241f727 -[NSWindowController _windowDidLoad] + 586
    11 AppKit                              0x00007fff924068e2 -[NSWindowController window] + 110
    12 App Store                           0x00000001059ec9d8 App Store + 6616
    13 CoreFoundation                      0x00007fff93826cbc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
    14 CoreFoundation                      0x00007fff937181b4 _CFXNotificationPost + 3140
    15 Foundation                          0x00007fff8b87dea1 -[NSNotificationCenter postNotificationName:object:userInfo:] + 66
    16 AppKit                              0x00007fff921d13c7 -[NSApplication finishLaunching] + 440
    17 AppKit                              0x00007fff921d0e91 -[NSApplication run] + 128
    18 AppKit                              0x00007fff921bc524 NSApplicationMain + 1832
    19 libdyld.dylib                       0x00007fff9a0df5c9 start + 1
    20 ???                                 0x0000000000000001 0x0 + 1
10/20/14 4:30:10.975 PM App Store[1720]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6080002ed580 {NSUnderlyingError=0x600000453950 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/featur ed.pdf, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/featur ed.pdf, NSLocalizedDescription=The request timed out.}
10/20/14 4:30:10.975 PM App Store[1720]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6080002eb880 {NSUnderlyingError=0x600000450530 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/top.pd f, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/top.pd f, NSLocalizedDescription=The request timed out.}
10/20/14 4:30:10.976 PM App Store[1720]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6080002e4580 {NSUnderlyingError=0x600000452960 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/catego ries.pdf, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/catego ries.pdf, NSLocalizedDescription=The request timed out.}
10/20/14 4:30:10.978 PM App Store[1720]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6080002e3f00 {NSUnderlyingError=0x60000044ff90 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/purcha sed.pdf, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/purcha sed.pdf, NSLocalizedDescription=The request timed out.}
10/20/14 4:30:10.979 PM App Store[1720]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6080002ede80 {NSUnderlyingError=0x600000450bf0 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update s.pdf, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update s.pdf, NSLocalizedDescription=The request timed out.}
10/20/14 4:30:10.979 PM App Store[1720]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6080002edf00 {NSUnderlyingError=0x60000044e520 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update -x.pdf, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update -x.pdf, NSLocalizedDescription=The request timed out.}
10/20/14 4:30:10.982 PM App Store[1720]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6080002eca80 {NSUnderlyingError=0x60000044a2f0 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update -xx.pdf, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update -xx.pdf, NSLocalizedDescription=The request timed out.}
10/20/14 4:30:10.984 PM App Store[1720]: serverError Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo=0x6000002e7880 {NSUnderlyingError=0x6000004497b0 "The request timed out.", NSErrorFailingURLStringKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update -xxx.pdf, NSErrorFailingURLKey=https://s.mzstatic.com/images/html_resources/da-storefront/tab_bar_modern/update -xxx.pdf, NSLocalizedDescription=The request timed out.}
10/20/14 4:32:13.188 PM App Store[1720]: <NSXPCConnection: 0x600000118150> connection to service named com.apple.storeassetd: Warning: Exception caught during decoding of received reply to message 'startAdoptionEligibilityCheckWithReplyBlock:', dropping incoming message and calling failure block.
Exception: Exception while decoding argument 1 (#2 of invocation):
<NSInvocation: 0x60000067a340>
return value: {v} void
target: {@?} 0x0 (block)
argument 1: {c} 0 ''
argument 2: {@"NSDictionary"} 0x0
Exception: value for key 'NS.objects' was of unexpected class 'NSError'. Allowed classes are '{(
    NSData,
    NSString,
    NSArray,
    NSDictionary,
    NSDate,
    NSNumber,
    NSNull
=================================
There is nothing under User Diagnostic Reports, but the following is the latest entry in System diagnostic reports:
================================
Command:
App Store
Path:
/Applications/App Store.app/Contents/MacOS/App Store
Process:
App Store [2737]
Path:
/Applications/App Store.app/Contents/MacOS/App Store
0x103c96000 -
0x103c99fff com.apple.appstore 2.0 (376)
<0B8E0BE5-B1F2-3978-B923-6077F58D3FB1> /Applications/App Store.app/Contents/MacOS/App Store
0x103cae000 -
0x103d04fff com.apple.StoreUI 1.0 (1)
<90F653C7-18D3-3752-8FEE-5637D3CFB699> /System/Library/PrivateFrameworks/StoreUI.framework/Versions/A/StoreUI
0x7fff84396000 -
0x7fff843f4fff com.apple.StoreFoundation 1.0 (1)
<1F304464-8A15-347A-BE47-5FAAA50A0C8C> /System/Library/PrivateFrameworks/StoreFoundation.framework/Versions/A/StoreFou ndation
Process:
com.apple.appstore.PluginXPCService [542]
Path:
/System/Library/PrivateFrameworks/StoreXPCServices.framework/Versions/A/XPCServi ces/com.apple.appstore.PluginXPCService.xpc/Contents/MacOS/com.apple.appstore.Pl uginXPCService
0x10e694000 -
0x10e695fff com.apple.appstore.PluginXPCService 1.0 (1) <63D8971F-049B-3D0E-B548-E071A2DCB3A0> /System/Library/PrivateFrameworks/StoreXPCServices.framework/Versions/A/XPCServ ices/com.apple.appstore.PluginXPCService.xpc/Contents/MacOS/com.apple.appstore.P luginXPCService
Responsible:
App Store [2737]
<thread QoS utility, boosted, received importance donation from storeassetd [519], received importance donation from App Store [2737], timers coalesced, IO policy standard>
<thread QoS utility, boosted, received importance donation from storeassetd [519], received importance donation from App Store [2737], timers coalesced, IO policy standard>
<thread QoS utility, boosted, received importance donation from storeassetd [519], received importance donation from App Store [2737], timers coalesced, IO policy standard>
<thread QoS utility, boosted, received importance donation from storeassetd [519], received importance donation from App Store [2737], timers coalesced, IO policy standard>
<thread QoS utility, boosted, received importance donation from storeassetd [519], received importance donation from App Store [2737], timers coalesced, IO policy standard>
<thread QoS utility, boosted, received importance donation from storeassetd [519], received importance donation from App Store [2737], timers coalesced, IO policy standard>
<thread QoS utility, boosted, received importance donation from storeassetd [519], received importance donation from App Store [2737], timers coalesced, IO policy standard>
<thread QoS utility, boosted, received importance donation from storeassetd [519], received importance donation from App Store [2737], timers coalesced, IO policy standard>
<thread QoS utility, boosted, received importance donation from storeassetd [519], received importance donation from App Store [2737], timers coalesced, IO policy standard>
0x7fff84396000 -
0x7fff843f4fff com.apple.StoreFoundation 1.0 (1)
<1F304464-8A15-347A-BE47-5FAAA50A0C8C> /System/Library/PrivateFrameworks/StoreFoundation.framework/Versions/A/StoreFou ndation
<thread QoS utility, boosted, received importance donation from App Store [2737], timers coalesced, IO policy standard>
<thread QoS utility, boosted, received importance donation from App Store [2737], timers coalesced, IO policy standard>
<thread QoS utility, boosted, received importance donation from App Store [2737], timers coalesced, IO policy standard>
<thread QoS utility, boosted, received importance donation from App Store [2737], timers coalesced, IO policy standard>
<thread QoS utility, boosted, received importance donation from App Store [2737], timers coalesced, IO policy standard>
<thread QoS utility, boosted, received importance donation from App Store [2737], timers coalesced, IO policy standard>
<thread QoS utility, boosted, received importance donation from App Store [2737], timers coalesced, IO policy standard>
<thread QoS utility, boosted, received importance donation from App Store [2737], timers coalesced, IO policy standard>
0x7fff84396000 -
0x7fff843f4fff com.apple.StoreFoundation 1.0 (1)
<1F304464-8A15-347A-BE47-5FAAA50A0C8C> /System/Library/PrivateFrameworks/StoreFoundation.framework/Versions/A/StoreFou ndation
Path:
/System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/sto reuid.app/Contents/MacOS/storeuid
0x10a405000 -
0x10a408fff com.apple.storeuid 1.0 (1)
<780A251B-638D-34C4-830F-3491B659BB6D> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Resources/st oreuid.app/Contents/MacOS/storeuid
   14
1 0xffffff7f81684000 0xb000
0xb000
com.apple.driver.AppleFDEKeyStore (28.30) <8 7 6 5 4 3 1>
   20
0 0xffffff7f824db000 0x23000
0x23000
com.apple.driver.AppleKeyStore (2) <19 18 8 7 6 5 4 3 1>
=====================================
This all looks like information that would be useful to someone who had the source code for the app, or at least an intimate knowledge of the OS, but not to ordinary users. I did notice a lot of "server time-out" errors but I have no idea what I can do about them, if even they are important.
Thanks for helping out with this.
Walt

App Store problem with 2g iTouch 8Gig

I just got the 8gig 2g itouch and when I try to use the app store from it I get a message that says I can only buy from the US store. This unit came from Canada and is supposed to have a 10 month warranty. If I use itunes from my PC I can download and sync any app, music, photo and the like with no problems. Is there a way to change the way the app store sees my unit and knows I am in the US? In general settings my region format is US under the international heading. Any help will be appreciated!

So, your unit was purchased in Canada, and all syncing and play is problem free. You are from the U.S. The main problem is, then, is the identity of the iPod.
If I might ask, what's the problem if the unit works fine? Is there an issue with the warranty?

Problem with fuzzy text in Captivate 5

Hi,
I know this is a question that has been raised before, but I'm yet to find a solution for my projects and live chat can't help me. I'm using Captivate version 5, and regardless of whether I publish in high, medium or low quality, the text on my text captions and rollover captions appears fuzzy once published. I'm using just the SWF to upload to a normal webpage (no LMS involved), without the HTML file, which I gather from previous posts may be a problem. Can anyone help me around this please?
Thanks,
Laura

Hi Laura
Likely nobody will be able to help here. What is happening is that by not using the associated HTML page, the SWF is being either stretched or compressed. When that happens, pixels become rearranged. Text gets fuzzy (if you reduce the size) and often blocky or "jaggy" (if you increase the size). Just the nature of dealing with raster (bitmapped) images.
Cheers... Rick
Helpful and Handy Links
Captivate Wish Form/Bug Reporting Form
Adobe Certified Captivate Training
SorcerStone Blog
Captivate eBooks

App builder problem with Fuzzy Toolkit

Similar Messages

Maybe you are looking for