/build/static/layout/Breadcrumb_cap_w.png

Sequencing Articulate Storyline

Hi Ladys and Gents,

I have made a virtualized app of Storyline (App- v Format) to test  it out on the clients. But when i started the application the application stopped working. So i looked in the eventviewer and found the following:

 

Fault bucket 3642135083, type 5

Name of event: clr20r3

Answer: Not available

Id CAB file: 0

 

Signature of problem:

P1: storyline.exe

P2: 1.3.1305.2012

P3: 519a5884

P4: Articulate

P5: 3.0.1305.2012

P6: 519a5854

P7: 1877

P8: a

P9: System.DllNotFoundException

P10:

 

Attached files:

C: \ Users \ ziggoitadmin \ AppData \ Local \ Temp \ WER470E.tmp.WERInternalMetadata.xml

 

These files may be available here:

 

 

Analysis Symbol:

Again seek solution: 0nRapport ID: 8613bbe6-3b05-11e3-8155-0050562dfc83

Report Status: 0

 

I tried to google the error but i cant really find what the problem is, i tried some solutions that i found like repairing .net, removing all the reg keys/cache etc for an clean start up but nothing worked so far. I posted de same question on the vendor forum, but i thought lets ask it here aswell because you never know.

If this doesn't work then we have to go over to a MSI and just normaly install the product. But i want test this way first.

 

 

Regards,

 

Arelan Junior Package Engineer


3 Comments   [ + ] Show comments
  • Install it manually on a machine you have the sequence installed on - does the seqeunce work then?

    If it does then it'll be something that has been missed during the monitoring phase and installing it manually has put those files on the system making them available for use by the sequence.

    Make sure you're shortcuts are called something slightly different, otherwise the MSI will overwrite them - unless you install it manually first and then install the sequence, in which case your sequenced shortcuts will be present.

    Open up the MSI and check what's in the file table and registry table - does it match what you've captured?

    Hope that helps,

    Dunnpy - dunnpy 11 years ago
  • I made an App-v from the vendor Exe not best practice but had to try.

    I installed it manually and then the sequence over it, and indeed it worked. Afterwards i removed the manual installed application and tested my App-v again. And my Sequence still worked. So indeed the manual install added some files somewhere so i removed the App-v aswell, and then started looking for files that were left behind.

    And i saw some .DAT files and some other files that i haven't seen before in the Appdata folder.

    And my sequence exclude's the Local Appdata by default. So just made another sequence and removed [{Local AppData}] from the exclusion list in the sequencer. And it worked !!!

    (This was in App-v 5) just a extra note.

    Thanks for the advice !!

    Best regards,

    Arelan Junior Package Engineer - Arelan 11 years ago
  • Sorry to dredge this from the depths but I could use some help.
    This did not work for me unfortunately. However please note I am using App V 4.6 SP2.

    Upon Startup on a client I get the following error:
    UI_AdminRequiredNotice
    UI_AdminVistaNotice11
    I choose UI_Close and then close out the registration box and the application closes. If I try to activate with a good key I get the same error as above then it says the key is invalid.

    I have verified I am installing with the latest version from Articulate (due to this flash error here https://community.articulate.com/discussions/articulate-presenter/ui-admin-required-notice-constantly-activating-registering)

    I have tried sequencing with the %CSIDL_LOCAL_APPDATA% and %TMP& folders taken out of the exceptions due to this article recommendation http://www.itninja.com/question/sequencing-articulate-storyline as well as from taking a look at what files are left over if you uninstall the local copy. If I have a local copy of articulate installed along with the virtual, the virtual works fine without error. If I uninstall the local copy and try the virtual then it still works.

    Procmon running in the bubble and filtered to the storyline.exe process with results other than successful isn't a whole lot of help either.
    there are a lot of NAME NOT FOUND, END OF FILE, and a few Access Denieds.

    The Access Denieds are in reference to locations on Y:\ (which is what we use instead of Q) even though I have the OSD set to allow local interaction and also have enforce security descriptors unchecked when sequencing.

    Any help would be greatly appreciated! - KireiX 9 years ago
    • I have also tried changing the location of the install to the Y drive as in this article: Install local: http://www.articulate.com/support/storyline-2/how-to-change-the-installation-location-for-articulate-storyline-2 and no luck.
      I installed a local copy and then uninstalled and looked at what files and registry entries were left over. I made sure those were included when sequencing and I got a different error. XML is below:

      <?xml version="1.0" encoding="utf-16"?>
      <ErrorReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <ReportType>Error</ReportType>
      <ApplicationName>Storyline</ApplicationName>
      <Version>2.4.1501.717</Version>
      <SerialNumber />
      <Enterprise>false</Enterprise>
      <Email />
      <Date>2015-03-05T12:39:07.1790898-08:00</Date>
      <Message>Could not load file or assembly 'Articulate.Text.Platform.dll' or one of its dependencies. The specified module could not be found.</Message>
      <Source>Articulate.Text.Forms</Source>
      <StackTrace>System.IO.FileNotFoundException: Could not load file or assembly 'Articulate.Text.Platform.dll' or one of its dependencies. The specified module could not be found.
      File name: 'Articulate.Text.Platform.dll'
      at Articulate.Text.Forms.TextPane..ctor()
      at Articulate.Design.NotesTextPane..ctor()
      at Articulate.Design.SlideView.ay()
      at Articulate.Design.SlideView..ctor()
      at Articulate.Storyline.Controls.exSlideView..ctor()
      at Articulate.Storyline.Forms.exMainForm.CreateSlideViewInstance()
      at Articulate.Design.UI.MainForm.PopulateViews()
      at Articulate.Storyline.Forms.exMainForm.PopulateViews()
      at Articulate.Design.UI.Forms.MainFormBase.OnCreateControl()
      at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
      at System.Windows.Forms.Control.CreateControl()
      at System.Windows.Forms.Control.WmShowWindow(Message&amp; m)
      at System.Windows.Forms.Control.WndProc(Message&amp; m)
      at System.Windows.Forms.ScrollableControl.WndProc(Message&amp; m)
      at System.Windows.Forms.Form.WmShowWindow(Message&amp; m)
      at System.Windows.Forms.Form.WndProc(Message&amp; m)
      at Articulate.Design.UI.Ribbon.RibbonForm.WndProc(Message&amp; m)
      at Articulate.Design.UI.Forms.MainFormBase.WndProc(Message&amp; m)
      at Articulate.Design.UI.MainForm.WndProc(Message&amp; m)
      at Articulate.Storyline.Forms.exMainForm.WndProc(Message&amp; m)
      at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message&amp; m)
      at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message&amp; m)
      at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

      </StackTrace>
      <FlashVersion>WIN 16,0,0,235</FlashVersion>
      <PrivateMemory>124,460 K</PrivateMemory>
      <VirtualMemory>478,380 K</VirtualMemory>
      <OSVersion>Windows 7 6.1.7601 Service Pack 1</OSVersion>
      <CLRVersion>4.0.30319.1026</CLRVersion>
      <ProcessorCount>1</ProcessorCount>
      </ErrorReport> - KireiX 9 years ago

Answers (1)

Answer Summary:
Posted by: Arelan 11 years ago
White Belt
1

Remove [{Local AppData}] from the exclusion list in the sequencer.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ