Kontakt runtime error in setup script

1. Hi,

   Kontakt (version 5 and 6) won’t install and a window with the following message pops up:

   »Runtime error in setup script.

   Line 0: Invalid data type for: ‘RegisteredOwner’

   My pc is new and I have already formatted it twice, but the error still occurs…

   What might be the cause?

   Attached Files:

   • 

2. That appears to be an installer for Native Access not Kontakt… and did you extract (Unpack) the zip file or are you trying to run the program from within the Zip file…Try unpacking to the desktop then running the installer.

4. Hi!
   Thank you for your help!

   But,
   I extracted all the content to the Desktop, and the error persists.
   In any product: Kontakt and Native Access…

   Attached Files:

5. Help me friends!

6. Do not unpack all of the content to the desktop.

   On Windows 10, you should run the following program to install Native Access — «Native Access 1.12.2 Setup PC.exe».

   You should be able to have the Native Access program install Kontakt. Alternatively, you should run «Kontakt Setup PC 6.4.2,exe».

   In all of the pictures you have posted you are unpacking files unncessarily.

   • Like x 1

7. Please install Native Access, then install Kontakt from Native Access. If you still have issues please contact my colleagues here :
   https://support.native-instruments.com/hc/en-us/articles/360002705378

**SOLVED** HELP Kontakt 4 C++ Runtime Error

guydoingmusic

Senior Member

Turned computer on this morning. Booted fine then had the «blue screen». Re-booted. Opened up VEPro, Cubase and loaded project. At this point got the «Runtime Error» for Kontakt 4. I have uninstalled, re-installed. Tried to run standalone. Tried to run standalone as Admin. Plugin crashes in VEPro, Cubase, and Standalone. I did a System Restore to a couple of days ago when it was working fine. No luck there either.

RiffWraith

Senior Member

Re: HELP Kontakt 4 C++ Runtime Error

Would help if you stated what your OS is, instead of having people look at that joke that is your sig.

Sounds like Windows? If so, the first thing I would do is this:

Open a command prompt, and type sfc /verifyonly and press Enter

That will tell you if any files have issues, including dll files. You can also do a sfc /scannow

That will fix any issues you have (verifyonly will only tell you if there are problems).

But be aware that if you have modified your system files as in theming explorer/system files, running sfc /scannow will revert the system files such as explorer.exe back to it’s default state. Make the appropriate backups of your system files that you have modified for theming if you wish to save them before running sfc /scannow.

If that doesn’t find anything, the next thing I would do is uninstall Kontakt, using the control panel, and then reinstall after rebooting.

Источник

проблема с установкой Update на Kontakt 5.1.0 (1 онлайн

subcrimes

New Member

1.Kontakt 5.1.0 установился без проблем, на первом скрине видно как выглядит папка из установленным Контактом.
2. При Установке Kontakt 5.2.1 Update выбивает следующее окно (Скрин №2). Нажимаю «ДА» так как без этого действия нельзя продолжить установку.
3.Для установки Апдейта выбираю по умолчанию ту же директорию, что и в предыдущей установке и нажимаю «Next», плагины тоже по умолчанию стоят пути установки и жму «Next».

4.После того как была нажата клавиша «Next» по идеи должна была пойти без проблемная установка Апдейта и на этом установка закончилась бы.

5.Однако у меня выбивает следующее окно Скрин №3 «Обзор папок» в котором установочная программа просит указать следующее: «please locate your original setup sources to continue operation».
При этом перед тем как выскакивает данное окно, на скрине №3 мы можем видеть, что из папки «Native Instruments» сама по себе удаляется папка «Kontakt 5».

6. Я пытался указать директорию «Native Instruments», установочный файл, пробовал копировать удалённую папку «Kontakt 5» в директорию «Native Instruments» и указать на неё, но безрезультатно.

Помогите кто чем сможет! если у кого то есть установленный Kontakt 5.5.0 и можно просто взять скопировать его для использования на другой ПК то я с радостью рассмотрю этот вариант.
Или если кто знает как исправить баг из установкой апдейта.
П,С. работаю на Операционной системе Windows 8.1. 64 бита

Источник

Kontakt runtime error in setup script

Post by vartom » Thu Nov 20, 2014 6:13 am

I’ve got the following:

***********
Runtime Error in setup script
Source file: «. «
Line Number: 68684
Library Not found: msi.dll
***********

I’ve researched this issue for days now but I couldn’t find an answer even though I was looking at your Technical Support forum as well.

You can see, that our project has a lot of line of code.
From one of your previous post I figured it out, that the ‘Line Number’ is the number of the line in the main script, after the include scripts have been merged.
The problem is that our main script contains no more than 2500 lines, so the rest of the lines are the other included scripts.

My question is how can I determine exactly where the exception was thrown (in which include script, which line)? Is there a tool which can merge all my included scripts to the main one?
And also do you have a ruff idea how the ‘msi.dll’ can’t be found?

All this is happening during UN-INSTALLATION (from Control Panel, Add/Remove programs) process.
The un-installation itself is starting in a strange fashion, the MAINTENANCE variable does not recognized that the product is installed, and it’s value is FALSE instead of TRUE (we know this from the logs).

I must mention that this happens on some of our client’s machine, so it’s pretty difficult for us (developers) to identify the actual cause of the error.

Thanks in advance for your assistance.

PS: Just this morning I got this error from another client:

***********
Runtime Error in setup script
Source file: «. «
Line Number: 35330
Unable to obtain command headers. Please rebuild you project.
***********

Is this mean that during building or bagging the project something went wrong? Do an actual «rebuild» as the message suggests solve the problem, or should we investigate this more deeply?
This is happening during INSTALLATION .

(We are using InstallAware 11, and I’m afraid at the moment to update it is not an option . )

Re: Runtime Error in setup script (msi.dll — not found)

Post by FrancescoT » Thu Nov 20, 2014 12:47 pm

could you please post the link where I can download your installer?
If you prefer, you can send me an email with the download link.

I’ll try to check it.

Francesco Toscano
InstallAware Software

Re: Runtime Error in setup script (msi.dll — not found)

Post by vartom » Mon Nov 24, 2014 7:40 am

Sorry for the late response, but I was waiting for a response (logs and environment information) form the client where the error occurred.
We add a lot of log messages to the code, and find out which line of code throws the exception: Get Installed State . is the culprit.
This is happening under WIN8 Pro (without any patches).

Do you have an idea what can I do to fix the problem?

Previously we had a similar issue with another function, which crashed on certain computers: Get System Setting Language .
This call was replaced with this one: Call DLL Function Kernel32.dll->GetSystemDefaultUILanguage , and after that the crashes disappeared from those computers as well.

I was thinking, if there is maybe a similar call, that I should use to replace the «Get Installed State» command, if no other option is available?

Thanks for your assistance.

Re: Runtime Error in setup script (msi.dll — not found)

Post by FrancescoT » Mon Nov 24, 2014 1:24 pm

Do you use any localization with the project?

Francesco Toscano
InstallAware Software

Re: Runtime Error in setup script (msi.dll — not found)

Post by vartom » Tue Nov 25, 2014 3:22 am

Also we have several embedded installers, which got installed/uninstalled by selecting/un-selecting a component.
And we are getting the install state for those components when the function fails.

Re: Runtime Error in setup script (msi.dll — not found)

Post by FrancescoT » Tue Nov 25, 2014 11:58 am

Are you sure that the localized resource strings currently used by your project have been updated accordingly (they include the most recent changes you may have applied to your script(s)?

I may suggest to try to export and then to import back in your project the localized resource strings used.

Francesco Toscano
InstallAware Software

Re: Runtime Error in setup script (msi.dll — not found)

Post by vartom » Wed Nov 26, 2014 5:14 am

I think there is a misunderstanding here.
We do use localized resources, and they do cause some other kind of error if they are not updated correctly, but I don’t think that’s the case here.

When the exception occurs the client didn’t change the culture setting, the default language was used (with the original scripts). We don’t have a problem with the languages at all.

At the moment, not the Get System Setting Language function crashes, but the Get Installed State .
More precisely, what fails ( just on a few machines , on other ones is working), is this line of code : Get Installed State for <3eb4e0fd-cfe6-469d-aecc-8b0b7b39ca68>into Variable SETUPTYPE_LMM .

I don’t understand why that is happening, so basically I’m looking for a possible explanation here.
And if there is non what you can think of, I’m also opened to change that line of code to something else, which does the same, but differently. For example I found this post: viewtopic.php?f=2&t=2766 .

Based on what I read there, would it be correct to change the above mentioned line of code with the below ones, and get the same result ? (If the answer is NO, can you please correct this code part, or provide some other way to achieve our goal?)

Read Registry Key HKLM\ <3eb4e0fd-cfe6-469d-aecc-8b0b7b39ca68>into SETUPTYPE_LMM
After that check weather $SETUPTYPE_LMM$ contains something or not.
If YES than the program was installed, otherwise was not.

Thanks for your assistance.

Re: Runtime Error in setup script (msi.dll — not found)

Post by FrancescoT » Wed Nov 26, 2014 1:04 pm

you can also use the approach described by the link, in place of that command(If I am not wrong, that command should do something similar internally).

Anyway it may be interesting, if you could provide some more details about the machine where you found such error.
I would to see if I am able to replicate the same.

Francesco Toscano
InstallAware Software

Re: Runtime Error in setup script (msi.dll — not found)

Post by vartom » Mon Dec 01, 2014 10:22 am

I couldn’t find out any more specifics (just what you can find above) about the machine, where the problem first occurred.
But since I don’t have any better ideas, I’ll try to change the code based on the other post.

I don’t know when that will happen (because we are in a middle of a release, and I have other important issues), but I’ll let you know if it worked out or not.

Re: Runtime Error in setup script (msi.dll — not found)

Post by vartom » Tue Mar 24, 2015 6:11 am

I’m back to this issue again. I’m still trying to fix it, but a new issues kept me from finishing it.
I managed to reproduce the issue on one of my Oracle VM Virtual PC (WIN7 64-bit — after a new installation).

I successfully switched the Get Installed State with Check Registry + verifying the returned value, so that not an issue anymore. This won’t cause the runtime error anymore.
But now my installer is crashing with the same message (Runtime error / msi.dll not found) on a totally unexpected place.

Here is how I can reproduce the issue:

1. Install the product, everything work out as expected, NO ERROR.
Here the part of the log (IA related):

1.EXE» /k=»»
LANGUAGE: English
ADVERTISE: FALSE
LOGGED :
MAINTENANCE : FALSE
MODIFY : TRUE
NEEDSUPGRADE : FALSE
NEWINSTANCE : FALSE
REBOOTCOMPUTER : FALSE
REBOOTNOW : OK
REMOVE : FALSE
REPAIR : FALSE
AFTER_REBOOT : FALSE
EXEDIR: C:UsersuserAppDataLocalTempmia8562.tmp MSIFILE : C:UsersuserAppDataLocalTempmia1SetupOffice.msi
ROOTDIR : C:UsersuserAppDataLocalTempmia8562.tmp—————————————————-

2. I’m going to Control Panel/Programs and Features, trying to uninstall the product.

Here’s the same log part:

Verbose logging started
—————————————————-
Installer : Start
CMDLINE : REMOVE=TRUE MODIFY=FALSE
LANGUAGE: English
ADVERTISE: FALSE
LOGGED :
MAINTENANCE : FALSE
MODIFY : FALSE
NEEDSUPGRADE : FALSE
NEWINSTANCE : FALSE
REBOOTCOMPUTER : FALSE
REBOOTNOW : OK
REMOVE : TRUE
REPAIR : FALSE
AFTER_REBOOT : FALSE
EXEDIR: C:ProgramData MSIFILE : C:UsersuserAppDataLocalTempmia1SetupOffice.msi
ROOTDIR : C:ProgramData—————————————————-

The setup is running successfully until reaches the Apply Uninstall command, than crashes with the «Runtime error / msi.dll not found» message.

The main difference that I noticed between the two logs, are with the CMDLINE, EXEDIR, ROOTDIR and the MAINTENANCE/MODIFY values.
As I previously mentioned the uninstallation is starting in a strange fashion, the MAINTENANCE variable does not recognized that the same product is installed, and it’s value is FALSE instead of TRUE (on this virtual machine ONLY). If I run the same installer on my dev. PC everything is working as expected, the MAINTENANCE will be TRUE during uninstallation, and also the Apply Uninstall command does NOT crash.

3. If I start the setup from Control Panel/Programs and Features but this time to REPAIR/REAPPLY/ADD FEATURE installation, the setup will also crash, but this time at the Apply Install command, error message is the same.

Do you have any idea what is this about?
What can I do, is there a way that I can fix this?
Can I replace these command with something else? (I don’t think that is plausible this time, right?)

4. If I run the executable to REMOVE/REPAIR/ADD FEATURE, and not start it from Control Panel/Programs and Features the setup will NOT crash. (That is not a user-friendly way to uninstall/repair the product. The users will not think of this scenario, they will always try to uninstall the product from Control Panel/Programs and Features !)
This is again can be a useful information. What is the main difference that you can think of between those two scenarios??

ALSO : I set the LOGGED variable from code, so that I trace everything. Durring installation the log is successfully saved with every information in it.
But durring REMOVE/REPAIR the log file only contains a few line, and nothing will be placed inside the node, basically will be empty. So I know nothing what could have caused the crash.
This is its whole content:

msi.dll exists in C:WindowsSysWOW64 folder.

I’m just pinpointing here:
— A windows update that is missing here?
— Somehow during uninstall/repair the Apply command faces a user authorization error (cannot create a folder or overwrite something)? [my user is admin on the virtual machine]
— Is is possible to use different CMDLINE params and still run the setup from Control Panel/Programs and Features?

Источник

Hi Francesco,

I’m back to this issue again. I’m still trying to fix it, but a new issues kept me from finishing it.
I managed to reproduce the issue on one of my Oracle VM Virtual PC (WIN7 64-bit — after a new installation).

I successfully switched the Get Installed State with Check Registry + verifying the returned value, so that not an issue anymore. This won’t cause the runtime error anymore…
But now my installer is crashing with the same message (Runtime error / msi.dll not found) on a totally unexpected place.

Here is how I can reproduce the issue:

1. Install the product, everything work out as expected, NO ERROR.
Here the part of the log (IA related):

Verbose logging started
—————————————————-
Installer : Start
CMDLINE : /m=»C:TempSetupO~1.EXE» /k=»»
LANGUAGE: English
ADVERTISE: FALSE
LOGGED :
MAINTENANCE : FALSE
MODIFY : TRUE
NEEDSUPGRADE : FALSE
NEWINSTANCE : FALSE
REBOOTCOMPUTER : FALSE
REBOOTNOW : OK
REMOVE : FALSE
REPAIR : FALSE
AFTER_REBOOT : FALSE
EXEDIR: C:UsersuserAppDataLocalTempmia8562.tmp MSIFILE : C:UsersuserAppDataLocalTempmia1SetupOffice.msi
ROOTDIR : C:UsersuserAppDataLocalTempmia8562.tmp—————————————————-

2. I’m going to Control Panel/Programs and Features, trying to uninstall the product.

Here’s the same log part:

Verbose logging started
—————————————————-
Installer : Start
CMDLINE : REMOVE=TRUE MODIFY=FALSE
LANGUAGE: English
ADVERTISE: FALSE
LOGGED :
MAINTENANCE : FALSE
MODIFY : FALSE
NEEDSUPGRADE : FALSE
NEWINSTANCE : FALSE
REBOOTCOMPUTER : FALSE
REBOOTNOW : OK
REMOVE : TRUE
REPAIR : FALSE
AFTER_REBOOT : FALSE
EXEDIR: C:ProgramData{FBA686E9-64F4-40CB-8E95-66BB923BBA52} MSIFILE : C:UsersuserAppDataLocalTempmia1SetupOffice.msi
ROOTDIR : C:ProgramData{FBA686E9-64F4-40CB-8E95-66BB923BBA52}—————————————————-

The setup is running successfully until reaches the Apply Uninstall command, than crashes with the «Runtime error / msi.dll not found» message.

The main difference that I noticed between the two logs, are with the CMDLINE, EXEDIR, ROOTDIR and the MAINTENANCE/MODIFY values.
As I previously mentioned the uninstallation is starting in a strange fashion, the MAINTENANCE variable does not recognized that the same product is installed, and it’s value is FALSE instead of TRUE (on this virtual machine ONLY). If I run the same installer on my dev. PC everything is working as expected, the MAINTENANCE will be TRUE during uninstallation, and also the Apply Uninstall command does NOT crash.

3. If I start the setup from Control Panel/Programs and Features but this time to REPAIR/REAPPLY/ADD FEATURE installation, the setup will also crash, but this time at the Apply Install command, error message is the same.

Do you have any idea what is this about?
What can I do, is there a way that I can fix this?
Can I replace these command with something else? (I don’t think that is plausible this time, right?)

4. If I run the executable to REMOVE/REPAIR/ADD FEATURE, and not start it from Control Panel/Programs and Features the setup will NOT crash. (That is not a user-friendly way to uninstall/repair the product. The users will not think of this scenario, they will always try to uninstall the product from Control Panel/Programs and Features !)
This is again can be a useful information. What is the main difference that you can think of between those two scenarios??

ALSO: I set the LOGGED variable from code, so that I trace everything. Durring installation the log is successfully saved with every information in it.
But durring REMOVE/REPAIR the log file only contains a few line, and nothing will be placed inside the < m y a h > node, basically will be empty. So I know nothing what could have caused the crash…
This is its whole content:
< / R u n S c r i p t >
< F r e e >
< / F r e e >
< C a c h e d S u p p o r t D i r >
< / C a c h e d S u p p o r t D i r >
< / I n s t a l l A w a r e >

msi.dll exists in C:WindowsSysWOW64 folder.

I’m just pinpointing here:
— A windows update that is missing here?
— Somehow during uninstall/repair the Apply command faces a user authorization error (cannot create a folder or overwrite something)? [my user is admin on the virtual machine]
— Is is possible to use different CMDLINE params and still run the setup from Control Panel/Programs and Features?

I would really appreciate any ideas.

Thanks.