What causes inconsiste​nt error: Error loading "mydll.dll​" Invalid access to memory location.

I have a set of sample code vis which are wrappers around an external dll using the call library function nodes.  These work in all versions of LabVIEW from 6.1 to 8.2.  In version 8 and 8.2, there is an inconsistent error which appears after a vi is opened, run successfully, closed and then re-opened some time later - all without closing LabVIEW.  The error is reported without an error number as 'Error loading "myDll.dll". Invalid access to memory location.'  If LabVIEW is closed, reopened and the vi loaded again and run, it works fine.  The same error occurs if a second vi calling the same .dll is loaded and run after the first is successful.
Since the vi works just fine the first time it is opened, why does this error occur the second time?  What do I have to change so that I don't  have to close LabVIEW every time I want to run a different VI?
Thanks in advance.
Mike.

Mea culpa. We have found a fix for this.  It relates to our dll structure.  We create a message pump in the dll associated with a hidden window.  When the dll is initialized, the window is registered with the operating system.  When the dll is unloaded, the window is closed but we weren't de-registering it.  This caused the problem the second time the dll was loaded.  By de-registering when the dll is unloaded, the problem has been solved.
Mike.

Similar Messages

  • RUNDLL Error loading CTMBHA.DLL invalid access to memory locat

    Error message at start up:? "Error loading CTMBHA.DLL? Invalid access to memory location"
    Does anyone know if this file has to do with Sound Blaster Audigy ADVANCED MB Ready, DR release 5.0.3708 ??If so, I will follow the reinstall instructions per the FAQ.?Thanks.

    Here's the solution from the_Riddler that works:?So I broke out REGMON from sysinternals, and tried the install when the Status 200 error came up I saw that they were accessing the "C:\Documents and Settings\All Users\Application Data\Creative Labs\Licenses" directory.. So I went to the Directory and renamed the B3420000.dat file there to B3420000.dat.old?Then did another reinstall and sure enough the application continued and allowed me activate the product and continue the install..

  • TH3800.dll loading causes "Invalid access to memory location".

    Hello, back again.
    I'm writing a thermotron temperature control program for a school project and I'm having an issue with the drivers supplied by Thermotron. I unpacked their drivers and put them in the instr.lib folder, then I put the included TH3800.dll into C:\VXIpnp\WinNT\bin in accordance with directions. I'm using the Student Edition of LabVIEW 2010 with SP1, and every time I load a VI from the library I get an error message that says:
    Error loading "TH3800.dll".
    Invalid access to memory location.
    I have no idea what the problem is exactly, and am not sure what to do to fix it. Any suggestions would be appreciated.
    Thanks,
    Simon
    Solved!
    Go to Solution.

    I'm not positive, but it seems like either the drivers you have are corrupt, don't exist, or are locked in memory somehow. This would definitely be an issue you'd want to bring up with Thermotron as they'll have more details about their DLLs. I tried googling about it and the dll name it's self brings up shockingly little information. Definitely something worth talking to them about!

  • Javascript error: invalid access to memory location

    I have a Popup Key LOV (Displays description, returns key value) in a screen that works great.
    Then we were giving a training to use the app.
    This one room has 8 computers in it and all get the Javascript error:
    Error: invalid access to memory location
    after the Popup comes up and then when selecting one of the choices.
    The version was 6.0xxxx and other machines are IE 7.0 but we found another machine not in that room that had 6.0xxx and it works fine.
    That room may not have had upgrades to OS or ???, ???
    Any ideas in what to check?
    Thanks Bill

    Hello,
    And this is a javascript error your getting? I've never seen that one, have you checked in FF it's debug message is better and will help you narrow it down.
    Since there your getting inconsistent results between the machines in that room compared to others is some sort of plugins on the machines your using for training? Popup blockers or tracking plugins (seen that in some UI labs).
    My other guess is that there might be some js trying to run on the popup before it's opened, but that wouldn't account for the inconsistent results.
    Carl

  • What causes the itunes.msi error and what is the best way to fix it?

    i have windows xp. when trying to update to itunes 8.2-the installer can not locate the Itunes.msi file. i found the file but the installer can't use it. this is also the case when i try to delete itunes and/or reinstall.
    what causes this error and could someone point me in the right direction as how to fix this.
    also i can't open itunes without having my ipod connected..so annoying. is that normal?
    thanks. =)

    Apple will exchange your iPod for a refurbished one for $199 for 64 GB 4G and $99 for the other 4Gs. They do not fix yours.
    Apple - iPod Repair price                       
    A third-party place like the following maybe less. Google for more.
    iPhone Repair, Service & Parts: iPod Touch, iPad, MacBook Pro Screens
    Replace the screen yourself if you are up to it
    iPod Touch Repair – iFixit

  • Download error cannot load the DLL (pdh dll)

     I've tried and tried several times to download Skype but half way through the down load I get the following error message: cannot load the DLL (pdh.dll)

    Try to run System File Checker tool (sfc /scannow): http://support.microsoft.com/kb/929833

  • Toad Error - Cannot load OCI DLL: C:\Oracle\instantclient_11_1\oci.dll

    Hello All,
    Help needed to fix this error.
    We are getting the below error from Toad after fresh install on Windows 7 64 Bit.
    Toad for Oracle Base
    Version: 10.6.1.3
    Cannot load OCI DLL: C:\Oracle\instantclient_11_1\oci.dll
    We are using the Oracle Instant Client (instantclient-basic-nt-11.2.0.2.0).
    We are able to connect to the database from the command line successfully, but when we tried to launch the Toad and connect it we are getting the above error.
    How do we fix this issue?
    Thanks in advance.
    Sandeep S

    mseberg wrote:
    So is this a Toad issue or an Oracle client issue?More like a general software or programming "issue". If Toad (or other program) is 32-bit, then loaded libraries (e.g. Oracle Client dll's) needs to be 32-bit.
    I'm sure this is documented in requirements for Toad. See e.g. [url http://toadfororacle.com/servlet/KbServlet/download/4264-102-12585/10.6_ReleaseNotes.htm#SystemRequirements]Toad 10.6 Release notes.
    Edited by: orafad on Aug 10, 2011 2:35 AM

  • Error 1097 after calling dll function which allocates memory inside

    Hello!
    When a call one my functions in my dll from LabView, i get an error 1097. My function takes a few arguments and then allocates some memory for measurement.
    It's not returning any pointers to that memory area, it is just allocates that memory for itself. I don't know what could be the problem, probably i am missing something.
    Could you help please?
    Best regards,
    Tamas
    Solved!
    Go to Solution.

    Are you sure that the allocate function is the problem?
    Error 1097 simply means something inside the external code wrote into memory locations that it was not meant to write. That is usually because of output buffer parameters that are not allocated (large enough) in LabVIEW when passed to the external code fucntion, so the function assuming it received a buffer of a certain size happily writes into that buffer but overwriting other information it should not have.
    But that is by far not the only possibility to cause this error. A simple bug in the external code can cause the same problem when a pointer goes astray or such. The fact that you used that library elsewhere already without seeing any problem is unfortunately no guarantee that the function is not buggy. The LabVIEW exeception handling around the Call Library Node has gotten rather picky and can detect violations that do not have to cause visible problems at all. But the violations it detects are real violations so just silencing them is not a good idea, as they could cause all kinds of problems including overwriting vital data structures in your program that either cause a crash later on or simply wrong results in other parts of your program. Especially the last one is a total bummer to debug.
    Without seeing much more of your code it is basically impossible to point out where the problem could lie. The particular Allocate function doesn't look like there is much that could be done wrong, but I would assume that you call several other functions too somewhere, which could cause the problem. If you can absolutely positively say that you never ever call any library function with a to short (or unallocated) buffer parameter, then you will have to take it up with the manufacturer of your lib, as it would seem very likely that there is some problem in there.
    Also you pass a handle to the library function but your Allocate function does not have this as a parameter! Where does this handle come from? Are you sure you have allocated and prepared it properly before calling this function? A handle is quite often a pointer, although usually a so called opaque pointer meaning the user of the library does not and should not know anything about the structure this pointer points to. It is only known internal to the library.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • What causes the digital fax error to keep popping up on the touch scree

    HP officejet pro 8500 wireless, the error message is digital fax error , what would cause that, Thanks Ted

    http://www.verizonwireless.com/support/knowledge-base-87344/
    Back up first though.  Textra app works for pic messages. You cannot go back to previous software version

  • What causes Media not present error, even with disc inserted

    I have a 2 hr  video project that I would like to place on a DVD in NTSC format.  I get an error msg "Media not present" even with DVD inserted in burner.  I have checked "Fit content to available space".  Is the 2 hr project too long to compress onto the DVD, or are there other possible causes?  I did a 1 1/2 hr project with no problems.  I have plenty of hard drive space. 

    download orders
    What version of Premiere Elements and on what computer operating system is it running?
    The problem is the disc in the burner tray not being recognized by Premiere Elements. Another frequent related issue is Burner Location: in burn dialog being empty when the Premiere Elements does not recognize the burner.
    In the problem that you have,
    a. Have you tried other brands/types of DVD discs?
    b. If you start a new project and take the new Timeline content to DVD-VIDEO on DVD disc, does the problem remain the same?
    B. Have you tried program uninstall/free ccleaner run through/reinstall with antivirus and firewall(s) disabled?
    If you are in a time crunch, you should consider burning the Timeline content to folder and then taking the VIDEO_TS Folder from that
    saved folder into a program like ImgBurn for the DVD-VIDEO on DVD production.
    Please review and consider and then we will supply you with how to details. Looking forward to your results.
    Thank you.
    ATR

  • What causes the VISA timeout error 1073807339?

    I'm getting this error while using a HP audio analyzer. The error also says "Timeout expired before operation completed." Can anyone give me any info on this?

    Hi
    Try increasing your timeout value. Check this link too: http://www.ni.com/support/labview/visa/verr2.htm
    Hope this helps
    Regards,
    Luca

  • Error  while loading a DLL

    Hi All
    We are trying to load some Tibhco related files when the application starts up using a servlet . But it fails with the following error below :
    ava.lang.UnsatisfiedLinkError: Native Library C:
    TIBCO
    TIBRV
    bin
    tibrvj.dll already loaded in another classloader#
    #1.5#000FFE28D1B40042000000EC0000155400040E0341EF3B6F#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1551)#
    #1.5#000FFE28D1B40042000000ED0000155400040E0341EF3C36#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1511)#
    #1.5#000FFE28D1B40042000000EE0000155400040E0341EF3CFC#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at java.lang.Runtime.loadLibrary0(Runtime.java:788)#
    #1.5#000FFE28D1B40042000000EF0000155400040E0341EF3DC8#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at java.lang.System.loadLibrary(System.java:834)#
    #1.5#000FFE28D1B40042000000F00000155400040E0341EF3E8C#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.tibco.tibrv.Tibrv.loadLib(Tibrv.java:435)#
    #1.5#000FFE28D1B40042000000F10000155400040E0341EF3F4F#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.tibco.tibrv.Tibrv.open(Tibrv.java:252)#
    #1.5#000FFE28D1B40042000000F20000155400040E0341EF4010#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.tpt.thresher.server.jms.TibrvMessagePublisher.getInstance(TibrvMessagePublisher.java:57)#
    #1.5#000FFE28D1B40042000000F30000155400040E0341EF40DB#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.tpt.thresher.server.jms.MessagePublisherFactory.makeMessagePublisher(MessagePublisherFactory.java:23)#
    #1.5#000FFE28D1B40042000000F40000155400040E0341EF42A6#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.tpt.thresher.server.startup.AppStartup.doStartUp(AppStartup.java:179)#
    #1.5#000FFE28D1B40042000000F50000155400040E0341EF436D#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.tpt.comxl.BootServlet.doPost(BootServlet.java:41)#
    #1.5#000FFE28D1B40042000000F60000155400040E0341EF4433#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.tpt.comxl.BootServlet.doGet(BootServlet.java:31)#
    #1.5#000FFE28D1B40042000000F70000155400040E0341EF44FE#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)#
    #1.5#000FFE28D1B40042000000F80000155400040E0341EF45C4#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5#000FFE28D1B40042000000F90000155400040E0341EF468B#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)#
    #1.5#000FFE28D1B40042000000FA0000155400040E0341EF4756#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
    #1.5#000FFE28D1B40042000000FB0000155400040E0341EF4821#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:391)#
    #1.5#000FFE28D1B40042000000FC0000155400040E0341EF48F0#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265)#
    #1.5#000FFE28D1B40042000000FD0000155400040E0341EF49BB#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345)#
    #1.5#000FFE28D1B40042000000FE0000155400040E0341EF4A85#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323)#
    #1.5#000FFE28D1B40042000000FF0000155400040E0341EF4B50#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865)#
    #1.5#000FFE28D1B40042000001000000155400040E0341EF4C1A#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240)#
    #1.5#000FFE28D1B40042000001010000155400040E0341EF4CF0#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#
    #1.5#000FFE28D1B40042000001020000155400040E0341EF4DB7#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#
    #1.5#000FFE28D1B40042000001030000155400040E0341EF4E81#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)#
    #1.5#000FFE28D1B40042000001040000155400040E0341EF4F51#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)#
    #1.5#000FFE28D1B40042000001050000155400040E0341EF501C#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
    #1.5#000FFE28D1B40042000001060000155400040E0341EF50E6#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
    #1.5#000FFE28D1B40042000001070000155400040E0341EF51AA#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)#
    #1.5#000FFE28D1B40042000001080000155400040E0341EF5279#1141307060810#System.err#sap.com/CXL_EAR#System.err#Guest#2####8b1fd570a9f211dab67a000ffe28d1b4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)#
    Wanted to know how can i avoid this.
    regards
    rajesh kr

    Hi Rajesh,
    It sounds like you have multiple instances of your web app getting loaded at the same time by different classloaders.
    So you need to ensure that your native library is loaded by WAS's common class loader: the referring class (that does the loadlibrary) must be in common/lib (not your webapp's WEB-INF/lib), and (of course) your native lib needs to in PATH or LD_LIBRARY_PATH as appropriate for the platform.
    just refer these two forums also..
    http://java.sun.com/docs/books/jni/html/design.html#8628
    Re: How find out which user is using which company code?
                           Regards
                           Kishor Gopinathan

  • Error 998 when calling dll

    Hello,
    I'm using LabView9 32-bit on 64-bit machine (Windows7) and I'm trying to call some functions from an external dll (32-bit).
    When configuring the call-library-function-node to use this dll I get an error message saying:
     "error loading (filename of dll)". Invalid access to memory location.
    The message is in German as is my operating system.
    Now I wrote a little test app in VC++ which directly called the dll. Everything worked fine.
    Next I wrote a wrapper-dll to call the original dll's functions and used that with my test app in VC++. Also no problems.
    Finally I configured LabView to call the wrapper-dll and got no error message at least right after configuration.
    But when I run the VI and debug the wrapper-dll I get an error 998 when the wrapper-dll tries to load the original dll.
    According to Microsoft's description of system error codes this is ERROR_NOACCESS and means exactly "Invalid access to memory location".
    So for some strange reason LabView isn't able to load that dll, which is obviously no problem for a C++ app.
    Any help on this would be very much appreciated since my project is strongly dependent on getting this to work.
    Best regards,
    \Ulli.

    Hi Ronnie,
    unfortunately there is no direct solution for this issue so far. Both sides, the dll-vendor (texas instruments) and ni are aware of it, with ni (in my opinion) at least trying to solve it.
    The cause seems to be some encryption stuff on the vendor side (they use an usb dongle). Is something similar involved with your problem?
    My current workaround is to have an external wrapper app written in c++ accessing the said dll. To this wrapper I communicate via socket to realise the function calls.
    This is quite annoying since it's a bit of work to do and you definitely loose performance. But so far no one was able (and in case of Texas Instruments even not willing) to help on that problem.
    And again: for me this issue applies only for the said configuration:
    Windows7, 64-bit,
    LV2009, 32-bit (I cannot use 64 bit because of some 32-bit-only toolboxes)
    the dll is available both in 32 and 64 bit...
    I'm still exited, if there will be an official solution,
    good luck,
    \Ulli.

  • Error Opening After Effects CS3 - cannot load AERes1.dll

    Hello,
    When I try to open After effects I get this Error "cannot load AERes1.DLL"
    I tried to reinstall after effects and it didnt dfix the problem.
    I uninstalled the entire Master collection CS3 and reinstalled and the problem didnt solve.
    I could open After Effects in the past.
    Any suggestions?

    OK so this is how I solved the problem if anyone encounter it ever again...
    Uninstalling and reinstalling the CS3 won't help.
    The problem happens probably because of quicktime installed prior to the CS3 updates. I didnt try to remove quicktime. I formatted my PC and luckly I had an image of my c: drive from the time I installed the cs3 and prior to the time I installed Quicktime. So I made all Adobe Cs3 updates first and only than installed Quicktime.
    Now After Effects works.
    If anyone finds a way to solve this without formatting c: drive, let me know.
    Ariel E.

  • Package load Failed! Invalid package Title, manifest file cannot be found

    Greetings. I am new to UPK and am seeking guidance on an upgrade to 11.1.
    A little background on what we are trying to do:
    We have two machines:
    Windows 2003 machine in domain 'X' | UPK 11.0.0.1.
    Windows 2008 R2 virtual machine in domain 'Y' | UPK 11.0 on the new machine first, install the 11.0.0.1 patch, and then upgrade to 11.1.
    We are using the same database as the old machine. Developer Server is Standard Authentication, Knowledge Center is Windows authentication.
    ==========================================================================================
    So far we have installed 11.1 with the respective database upgrades, but are lost as to how to migrate the old Content Root data. We have copied all the content to the new Content Root, added it to IIS like the old machine, and verified that the UPK database Content Root path is correct and working.
    For the rest of the post, I am remoted into the server from my local workstation, and then using IE to access KCenter on the server's FQDN, not via localhost.
    Since I am green, so I presumed that I would need to import the titles under Manager in KCenter. I zipped each content folder individually (they are named "1", "9", etc), and then attempted to import each zip file.
    NOTE: At this stage sometimes we are prompted to authenticate again. When it does, sometimes the credentials that we know work, get rejected and we are prompted again. This will repeat until we get a 401 and we have to start over. We have verified that the Windows account currently in session with the site is valid and has administrator authority within KC.
    NOTE2: On the first few tries, .NET complained that maxRequestLength was not large enough. I had our servers team increase it on the actual server in order for us to proceed.
    Provided we don't have to authenticate again, or that it actually accepts our credentials, we get to the 30% mark and then receive the error: *"Package load Failed! Invalid package Title, manifest file cannot be found"*
    Does anyone have any wisdom for this process? The title importation section in the deployment manual is not helping, and the administrator from whom I am taking over this software has not had to deal with this before.
    Thank you,
    Ian
    Edited by: 986290 on Feb 5, 2013 10:21 AM

    Hi Marc, thanks for the post,
    I have gone through an extensive troubleshooting process with Oracle, including their development team, in order to fully complete our project setup. As a supplemental bit of information, we also were having connection errors when attempting to publish directly to the knowledge center.
    As far as the context of this post, here is the solution in brief:
    1) Verify that the package being imported was published from the same version of the Developer Client as the Knowledge Center installation's.
    2) Check for database consistency issues. In our case we were using a database that was built in another domain. After numerous attempts with Oracle support on the line to determine the inconsistency, it was decided to completely reinstall and build a new database from scratch in the new domain.
    3) Check application pool identities and access (while we had some inconsistencies here, correcting them did not change the behavior of the import/publish errors)
    In review, a lot of what we had setup was correct. Our primary point of failure, we feel, was using the old database. Technically this should not have been a problem, but Murphy likes to get his way sometimes.
    Cheers,
    Ian

Maybe you are looking for