HT201210 " An internal device error has occurred"

I am trying to update my IOS on my Generation 4 Ipod Touch but I keep getting a message that says " An internal device error has occurred"

- Try placing the iPod in Recovery Mode and then restore via iTunes.
- Next try placing the iPod in DFU mode and then restore
- Disable the computer's antivus and firewall
- Make an appointment at the Genius Bar of an Apple store.
Apple Retail Store - Genius Bar

Similar Messages

'An Internal Device Error Has Occurred' what do i do?

I keep getting this whenever I try to sync my ipod.
I don't know what it means or What I should do about it..
Please help

Try:
- Reset the iOS device. Nothing will be lost
Reset iOS device: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears.
- Reboot the computer
- Try another USB port and cable
- Restore from backup. See:
iOS: How to back up
- Restore to factory settings/new iOS device.

An internal device error has occurred

I have tried everything i have a iphone 5 with the newest update on ios 7 nothing will sync i have reset it started from new. Someone please help me. i have had the phone replaced also i have unistalled itunes and re installed it. PLEASE HELPPPPPPPP

Try:
- Reset the iOS device. Nothing will be lost
Reset iOS device: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears.
- Reboot the computer
- Try another USB port and cable
- Restore from backup. See:
iOS: How to back up
- Restore to factory settings/new iOS device.

An internal software error has occurred. Error code: 1003

Dear, I am working on a FPGA programming. When I use the VI: "High Throughput Add Function". Some error occur.
Internal software error(s):
Error code: 1003 (refer to details)
Details:
An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
Error 1003 occurred at E:\Program Files (x86)\National Instruments\LabVIEW 2012\vi.lib\rvi\FXPMathLib\FxpAdd\modGen\nifxpmath_Add_EmitCode.vi: There's a broken VI

Hello Yjin,
Can you show me a VI in which this error occurs?
Which software versions are you using?
An easy way to find this information is as follows:
http://digital.ni.com/public.nsf/allkb/271F252B4EF0A2E0862570E70056A1E4?OpenDocument
Kind Regards,
Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
CLD, CTA
If someone helped you, let them know. Mark as solved and/or give a kudo.

HELP!!!! An Internal Server Error Has Occurred when I try to redeem a gift.

When I try to redeem a 'gifted' album, I end up with a blank page with this message at the top:
An Internal Server Error Has Occurred.
When I try to "report a problem" the same page appears, even on a different computer.
When I try to "Report a Problem" in my account on iTunes, there is no field to type in my details.
I have tried to ring Apple, and they say they cannot support iTunes, and that all complaints have to go through the web site. HELP!!!!

Shirley,
Unfortunately, this is the wrong forum for you. This forum is for those of us involved with Apple's iTunes U ("University"). iTunes U is a way for colleges and universities to post content within the iTunes Store. None of us here can help you resolve a money issue with the iTunes Store, must as we'd like to. Only Duncan works for Apple ... the rest of us work for colleges and universities all over the world and we have little control over your Apple account(s).
But, to be honest, I'd be pretty shocked that a call to Apple could not help you resolve this kind of problem. Compared to other tech companies, Apple is exceptional in its phone support. If it's helpful, this page:
http://www.apple.com/support/itunes/store/gift/
has a link at the bottom you can use to contact Apple directly about gift music problems.

Another Compiler Bug (message: An internal build error has occurred... Unknown Flex Problem)

I was fighting with this problem for a few days. Finally I've got it resolved. I want to describe it and fill in BUG in the bug report, but I am not sure about Adobe support options. So, I am putting bug report here.
1. ASSUMPTION: All problems which compiler reports as unknown problem are the real compiler BUGs/Problems. Eventually MXML compiler/ActionScript compiler should be able to take C++ or FORTRAN code or an aribitrary text and nicely tell "Error: It is not ActionScript (Flex) code" or "the code is corrupted from Line so and so...". When compiler crashed, it is most probably due to one of the states not handled (or not handled correct). Keeping this in mind I assume, that my code has nothing to do with the compiler crash.
2. PROBLEM Description.
     - I tried to port our internal project from Flex3.5/Flex Builder 3 to Flex4.1/Flash Builder 4.
     - After checking out and trying to build code I start getting weird problems like Error 1037: Packages cannot be nested.
     - After cleaning and compiling project by project, walking up dependency tree, I was able to get rid of this problem.
     - On last Project I've got another problem (An internal build error has occurred... Unknown Flex Problem). Which I stuck with for a while.
     - When I checked log file I found following messages:
============================================================
!ENTRY com.adobe.flexbuilder.project 4 43 2010-12-21 15:45:24.353
!MESSAGE Uncaught exception in compiler
!STACK 0
java.lang.ClassCastException: macromedia.asc.parser.InputBuffer cannot be cast to flex2.compiler.as3.CodeFragmentsInputBuffer
at flex2.compiler.as3.AbstractSyntaxTreeUtil.lineNumberToPosition(AbstractSyntaxTreeUtil.jav a:1266)
at flex2.compiler.mxml.ImplementationGenerator.generateBinding(ImplementationGenerator.java: 569)
at flex2.compiler.mxml.ImplementationGenerator.generateBindingsSetupFunction(ImplementationG enerator.java:863)
at flex2.compiler.mxml.ImplementationGenerator.generateBindingsSetup(ImplementationGenerator .java:812)
at flex2.compiler.mxml.ImplementationGenerator.generateInitializerSupportDefs(Implementation Generator.java:1878)
at flex2.compiler.mxml.ImplementationGenerator.generateClassDefinition(ImplementationGenerat or.java:1044)
at flex2.compiler.mxml.ImplementationGenerator.<init>(ImplementationGenerator.java:206)
at flex2.compiler.mxml.ImplementationCompiler.generateImplementationAST(ImplementationCompil er.java:499)
at flex2.compiler.mxml.ImplementationCompiler.parse1(ImplementationCompiler.java:197)
at flex2.compiler.mxml.MxmlCompiler.parse1(MxmlCompiler.java:168)
at flex2.compiler.CompilerAPI.parse1(CompilerAPI.java:2871)
at flex2.compiler.CompilerAPI.parse1(CompilerAPI.java:2824)
at flex2.compiler.CompilerAPI.batch2(CompilerAPI.java:446)
at flex2.compiler.CompilerAPI.batch(CompilerAPI.java:1274)
at flex2.compiler.CompilerAPI.compile(CompilerAPI.java:1496)
at flex2.tools.oem.Application.compile(Application.java:1188)
at flex2.tools.oem.Application.recompile(Application.java:1133)
at flex2.tools.oem.Application.compile(Application.java:819)
at flex2.tools.flexbuilder.BuilderApplication.compile(BuilderApplication.java:344)
at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder$MyBuilder.mybuild(A SApplicationBuilder.java:276)
at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.build(ASApplication Builder.java:127)
at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.build(ASBuilder.java:190)
at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.build(ASItemBuilder.java:7 4)
at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.buildItem(FlexProjectB uilder.java:480)
at com.adobe.flexbuilder.project.compiler.internal.FlexProjectBuilder.build(FlexProjectBuild er.java:306)
at com.adobe.flexbuilder.project.compiler.internal.FlexIncrementalBuilder.build(FlexIncremen talBuilder.java:157)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:633)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:218)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:360)
at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:516)
at org.eclipse.core.internal.resources.Project.build(Project.java:94)
at org.eclipse.ui.actions.BuildAction.invokeOperation(BuildAction.java:221)
at org.eclipse.ui.actions.WorkspaceAction.execute(WorkspaceAction.java:162)
at org.eclipse.ui.actions.WorkspaceAction$2.runInWorkspace(WorkspaceAction.java:483)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38 )
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!SESSION 2010-12-22 09:48:27.766 -----------------------------------------------
eclipse.buildId=M20100909-0800
java.version=1.6.0_16
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -data C:\Client_Flex4 -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
================================================
3. RESOLUTION/WORK AROUND
     - I was able to get this problem cleared by putting compiler option for Flex Application projects: -keep-generated-actionscript
4. SIDE NOTE
I do not really see putting this compiler option as the solution and living with the mistery is making me fill a bit bad.

Hi Faser,
I just tried it on Vista with our latest FB Plugin build but
I was unable to reproduce your issue with the following setup:
- FB Plugin build installed by Administrator account user
under her Documents folder
- Administrator account user can launch, create Flex projects
under her own workspace without any problems
- Standard account user can launch the FB Plugin build (need
Admin's password) and create Flex project (default location) under
his own workspace
If your setup is different, can you please log a bug at
http://bugs.adobe.com/flex.
Be sure to include what build you are using, whether it's
reproducible, the detail of the setup, etc...
thanks,
Sharon

When launching FaceTime - "internal facetime error has occurred"?

Trying to launch facetime and keep getting message "internal facetime error has occured". Anyone have any idea what that means?

If your webcam is powered by USB, make sure it is attached directly to your Mac and not a USB hub. In my case, I had my Rocketfish webcam attached to a peripheral USB hub and it wasn't drawing enough power to operate at capacity. Therefore, Facetime was quitting on me and giving me an error message. Once I attached the webcam directly to my Mac USB port, problem solved. Hope that helps.

Mathscript node: an internal mathscript error has occurred: 64-bit LabVIEW 2009

Hi Folks -
I have an installation now of
LabVIEW 2009 9.03f, Vision, and Advanced Signal Processing Toolkit, all
64-bit versions on a new computer so that I can convert some code from
32- to 64-bit.
I figure I will address errors
one-by-one and here's the first one. I have a VI with a mathscript
node and the VI, which loaded and ran fine in the 32-bit environment,
is now broken and giving the error "mathscript node: an internal
mathscript error has occurred." My main concern - is mathscript not
supported in 64-bit LabVIEW right now?
I am attaching the VI. Any ideas are appreciated. I need to get this working.
Also, NI, is there a special 64-bit forum that we should post to in the future, or create to post to?
Sincerely,
Don
Solved!
Go to Solution.
Attachments:
sort.vi ‏753 KB

From 2009 help
LabVIEW MathScript is a text-based language you can use to write functions and scripts. You can process scripts using LabVIEW MathScript in the LabVIEW MathScript Window or a MathScript Node. When you create a LabVIEW MathScript, you must use supported data types.
The MathScript syntax is an intuitive and logical
syntax predominantly based on standard mathematical and computer
programming terms, terms in widespread and common use, and/or
descriptive abbreviations, truncations and concatenations of standard
terms. The LabVIEW MathScript Window and MathScript
Nodes are able to process files you create using the current MathScript
syntax and, for backwards compatibility, files you created using legacy
MathScript syntaxes. The LabVIEW MathScript Window
and MathScript Nodes also can process certain of your files that use
other text-based syntaxes, such as files you created using the MATLAB® software. Because the MathScript RT Module engine is used to process scripts in the LabVIEW MathScript Window
and MathScript Nodes, and because the MathScript RT Module engine does
not support all syntaxes, not all existing text-based scripts are
supported.
(LabVIEW 64-bit) LabVIEW MathScript is not supported in LabVIEW (64-bit).

FPGA An internal software error has occurred. memory write

Hi everybody
We are encountering an error during compilation of an FPGA VI. It is probably related to our use of FPGA block memory. We have a non-timed while loop that is reading from an FPGA host-to-target FIFO and writing into block memory (inside a sub-VI called z_scan_write.vi). In another loop (this one is timed-loop), there is a subVI called we z_scan_read.vi, inside which we read from the block memory.
Does anybody have an idea what is going wrong and how we could avoid this problem? Thank you very much in advance for any hint!
The full error message is as follows. Note that it refers to the above-mentioned two subVIs z_scan_write.vi and z_scan_read.vi...
An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
nirviUIDToObject.vi<ERR>
Error getting object reference for UID.
All text parsed:
<CodeGenErr>
<ErrorCode>-61060</ErrorCode>
<DynamicText><TreeLineInfo><LineInfo><ErrorInfoCallback><VIPath>C:\Program Files (x86)\National Instruments\LabVIEW 2010\vi.lib\rvi\ClientSDK\Core\ErrorReporting\Private\nirviPersistentNameToProjectItemLineInfoCallback.vi</VIPath>
<Data>zIntensityTuples/{29C03A58-DC8D-4BC7-BAFA-66AFAE4E42D1}/%s</Data>
</ErrorInfoCallback>
</LineInfo>
<TreeInfo><TreeID>ProjItem</TreeID>
</TreeInfo>
</TreeLineInfo>
<TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_write.vi_FPGACompileCopy00000021.vi</VIPath>
<UID>2747</UID>
<ObjectName>Memory Write 'Memory Method Node'</ObjectName>
</DiagramObject>
</LineInfo>
<TreeInfo><ParentID>ProjItem</ParentID>
</TreeInfo>
</TreeLineInfo>
<TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_read.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>194</UID>
<ObjectName>Memory Read 'Memory Method Node'</ObjectName>
</DiagramObject>
</LineInfo>
<TreeInfo><ParentID>ProjItem</ParentID>
</TreeInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61060</ErrorCode>
<DynamicText><TreeLineInfo><LineInfo><ErrorInfoCallback><VIPath>C:\Program Files (x86)\National Instruments\LabVIEW 2010\vi.lib\rvi\ClientSDK\Core\ErrorReporting\Private\nirviPersistentNameToProjectItemLineInfoCallback.vi</VIPath>
<Data>zIntensityTuples/{29C03A58-DC8D-4BC7-BAFA-66AFAE4E42D1}/%s</Data>
</ErrorInfoCallback>
</LineInfo>
<TreeInfo><TreeID>ProjItem</TreeID>
</TreeInfo>
</TreeLineInfo>
<TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_write.vi_FPGACompileCopy00000021.vi</VIPath>
<UID>2747</UID>
<ObjectName>Memory Write 'Memory Method Node'</ObjectName>
</DiagramObject>
</LineInfo>
<TreeInfo><ParentID>ProjItem</ParentID>
</TreeInfo>
</TreeLineInfo>
<TreeLineInfo><LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.z_scan_read.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>194</UID>
<ObjectName>Memory Read 'Memory Method Node'</ObjectName>
</DiagramObject>
</LineInfo>
<TreeInfo><ParentID>ProjItem</ParentID>
</TreeInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2803</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2816</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2803</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2816</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2803</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2816</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2803</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2816</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
Solved!
Go to Solution.

Removing the two subVIs that read from/write to the block memory doesn't avoid the error showing up during compilation. The error details are obviously different now; they don't refer to the two subVIs (mentioned in the previous post) anymore...
An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
nirviUIDToObject.vi<ERR>
Error getting object reference for UID.
All text parsed:
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2735</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2748</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2735</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2748</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2735</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2748</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>
<CodeGenErr>
<ErrorCode>-61106</ErrorCode>
<DynamicText><TreeLineInfo><TreeInfo><TreeID>1</TreeID>
</TreeInfo>
<LineInfo><VI><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</VIPath>
<Name>NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi</Name>
</VI>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>2</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2735</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
<TreeLineInfo><TreeInfo><TreeID>3</TreeID>
<ParentID>1</ParentID>
</TreeInfo>
<LineInfo><DiagramObject><VIPath>C:\NIFPGA\compilation\FPGAWrapperAK101_PXI-7813R_main_C0C9511F\MungedForFPGA\NI.Munge.main.vi_FPGACompileCopy00000001.vi</VIPath>
<UID>2748</UID>
<ObjectName>SubVI: 'NI.Munge.generate_DAC_voltages.vi_FPGACompileCopy00000001.vi'</ObjectName>
</DiagramObject>
</LineInfo>
</TreeLineInfo>
</DynamicText>
</CodeGenErr>

I cannot log in to volume purchasing--an internal server error has occurred

I cannot log in to volume purchasing--an internal server error has occurred

just tried again and got XML code.

An internal build error has occurred. Right-click for more information

Greetings!
We are using Eclipse 3.4 or 3,5 with Flash 4 plugin and Flex SDK 3.3.0.
Project set comprises several, more than a couple dozen, dependent Flex and Java projects.
Time-to-time we run across an internal build error on all Flex projects.
The stack trace where topmost entries are:
So far we did not find how to get around the problem except delete project set and start from
scratch.
Pleas help!
!ENTRY com.adobe.flexbuilder.project 4 43 2010-07-23 14:40:38.353
!MESSAGE Uncaught exception in compiler
!STACK 0
java.lang.NullPointerException
at com.adobe.flexbuilder.multisdk.compiler.internal.ASBuilder.applySettings(ASBuilder.java:3 25)
at com.adobe.flexbuilder.multisdk.compiler.internal.ASApplicationBuilder.setup(ASApplication Builder.java:67)
at com.adobe.flexbuilder.multisdk.compiler.internal.ASItemBuilder.setup(ASItemBuilder.java:5 4)
at com.adobe.flexbuilder.project.compiler.BuilderFactory.createBuilder(BuilderFactory.java:8 0)
at com.adobe.flexbuilder.project.compiler.BuilderFactory.createBuilder(BuilderFactory.java:5 9)
at com.adobe.flexbuilder.project.compiler.BuilderManager.getBuilder(BuilderManager.java:192)
When it happens you can not open project "Properties | Flex Compiler" dialog because error
message pops up saying "The currently displayed page contains invalid values."
I am not sure how "an internal build error..." relates to "...displayed page contains invalid values"
but it worth to mention anyway.
Thanks for your help.

Getting the same error and deleting bin-debug files doesn't help. All switch statements have a case so that isn't an issue either.
Says to right click on the error for more info but that brings ups broken webpage.
Adobe I think you really rushed Flash Builder out to fast. These weird errors and the namespace debacle is just totally unprofessional.

CE: An internal authentication error has occurred

Could anyone help me please? i have been play 'try and search game':( for serveral days for this problem.
i search this forum and find other people have been in same problem, but no progress for me
i look around at uwc.log, but doesn't give me clue, i already recheck LDAP, COOKIE setting n make sure everything are right.
FYI: SSO for CAL and ME are works fine.
my step for uwc:
1. run "config-uwc"
2. post configuration
a. Enabling SSO with identity server (CE and ME)
b. edit "ics.conf"
3. restart all jes component
so did i miss something?
=======================================
uwc.log
Jul 21, 2005 10:49:20 AM com.sun.uwc.common.util.UWCDomainManager loadDomainFromIS
SEVERE: Exception..LDAP authentication failed.
Jul 21, 2005 10:49:20 AM com.sun.uwc.common.util.UWCDomainManager loadDomainFromIS
SEVERE: Exception..LDAP authentication failed.
Jul 21, 2005 10:49:20 AM com.sun.uwc.common.auth.IdentitySSOAuthFilter doFilter
FINE: 1. session is not present.. get token manager..
Jul 21, 2005 10:49:20 AM com.sun.uwc.common.auth.IdentitySSOAuthFilter doFilter
WARNING: SSOException..LDAP authentication failed.
Jul 21, 2005 10:49:20 AM com.sun.uwc.common.auth.MessagingSSOAuthFilter doFilter
FINE: Validate Cookies
Jul 21, 2005 10:49:20 AM com.sun.uwc.common.auth.MessagingSSOAuthFilter doFilter
FINE: inValid Cookies
Jul 21, 2005 10:49:20 AM com.sun.uwc.common.auth.LDAPAuthFilter doFilter
FINE: Check If Identity is enabled
Jul 21, 2005 10:49:20 AM com.sun.uwc.common.auth.LDAPAuthFilter doFilter
FINE: Identity is enabled....return
Jul 21, 2005 10:49:20 AM com.sun.uwc.common.util.UWCPreferences node
SEVERE: Could not load the file: /var/opt/sun/uwc/WEB-INF/domain/en-us,en;q=0.5/i18n.properties (No such file or directory)
Jul 21, 2005 10:49:20 AM com.sun.uwc.common.util.UWCDomainCache loadUWCResourceBundle
WARNING: Unable to load default resource bundle for domain nohat.comand localeen-us,en;q=0.5
Jul 21, 2005 10:49:20 AM com.sun.uwc.common.util.UWCPreferences node
SEVERE: Could not load the file: /var/opt/sun/uwc/WEB-INF/domain/en-us/i18n.properties (No such file or directory)
Jul 21, 2005 10:49:20 AM com.sun.uwc.common.util.UWCDomainCache loadUWCResourceBundle
WARNING: Unable to load default resource bundle for domain nohat.comand localeen-us
Jul 21, 2005 10:49:20 AM com.sun.uwc.common.util.UWCDomainCache resolveLocale
FINE: sublangs ..en
Jul 21, 2005 10:49:20 AM com.sun.uwc.common.util.UWCDomainCache loadUWCTheme
WARNING: Theme for localeenandnohat.com is not configured
=======================================
any hint,suggestion,idea are always open
many big thanks for you all

Follow the following path :
Sun Java Enterprise System 2005Q1 Installation Guide
-> Chapter 10 Configuring Components After Installation
--> Configuring Messaging Server After a Configure Later Installation
---> If you intend to use Delegated Administrator Utility ...
----> Sun Java System Communications Services 6 2005Q1 Delegated Administrator Guide
-----> Chapter 3 Configuring Delegated Administrator
And yes, fully admitted, setting it all up is not easy. Or as Jay put it : "and getting SSO to work with UWC is somewhat of an art..." :)
Cheers, Ben

HT1923 Ipad/Iphone - unknown error/internal device error

Hey all
I am having troubles with my new Ipad and Iphone. Both are new items purchased recently and i have been able to download podcasts, apps and music but now everytime i sync my items, it says 'iphone/ipad cannot be synced - an internal device error has occured', sometimes it doesnt read the devices and other times it says 'cannot connect. An unknown error occured'. Could this be a virus - i have suggested everything on the support page.

iPhone and iPod touch: Unknown error containing '0xE' when connecting
http://support.apple.com/kb/TS3221
"....Sometimes outdated drivers on a Windows computer can cause this issue. Check with the manufacturer of your computer, or your computer's motherboard, for any available USB chipset driver updates. Learn more about updating drivers for Windows."

Error:COMMON-1: Some unexpected internal error has occured.

Error:COMMON-1: Some unexpected internal error has occured. If the problem persists please report to the Tech Support.
Error: No response from the device "a.b.c.d/161". Check SNMP communities, version or network for issues.
Above errors are seen on accessing WLC for config purpose from WCS. Seen after migrating WCS 4.2.62 to a new hardware and restoring the backed config.
OS and software versions remain the same, only new hardware is an upgraded one.
The original server is now put back in place and works .. just fine.

In this migration, everything is absolutely same except the hardware.
Same WLCs, same WCS version. IP/hostname/configs all same.

Prime Infrastructure 2.1 - User add failed : Some unexpected internal error has occurred.

Setting up Prime Infrastructure to manage 2504 WLC, trying to add Lobby Ambassador and I get this error message:
User add failed : Some unexpected internal error has occurred. If the problem persists please report to the Tech Support.
Technically, this is my second attempt at setting up PI. I set it up initially with the wrong version of PI and created a lobby ambassador. I followed the instructions from the forum with a similar problem that said to remove the trap receiver on the WLC from my first attempt at installing PI.
https://supportforums.cisco.com/discussion/11110686/failed-add-device-wcs-reason-common-1-some-unexpected-internal-error-has-occured
I'm now able to add a Lobby Ambassador as long as its not the same username that I created on the previous PI setup. So I suspect this Lobby Ambassador username is somewhere on the 2504 WLC, but I can't find it anywhere to remove it.

I have just been struggling with a similar issue on a fresh install of Prime 2.1 Upgraded to 2.1.1.
If I try to create the user with lobby ambassador role it just fails with "unexpected internal error".
I eventually found that by creating the user as a normal admin user first - the user is added. You can then go in a remove the admin role and change the role to lobby ambassador. This works with no internal error and the lobby admin user is working fine.
I would say it is just a bug.

HT201210 " An internal device error has occurred"

Similar Messages

Maybe you are looking for