cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Business One AddOn Installer

Former Member
0 Kudos

hi everyone. i have created my .ard file and also my installer, the installer I created had an extension name .msi. I was on the process on registrating my add-on. I encountered an error:

1.Wrong executable digital signature for Add-on.

2.Wrong digital signature for Add-on installer.

Is it necessary to fill up the installation package for the add on to complete? Thanks.

omann

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

I have created two ard files for my add-ons but I created it using the executable file only. I register the two add-ons: ard file for Registration Data File and the executable file for the Installation Package. The status of these two add-ons in the Add-On Manager was connecting. Does it mean that my add-on is already active in my SAP B1 application? Thanks!

Nussi
Active Contributor
0 Kudos

Hi,

ok, sorry for the late answer - had stress the last days and will out tomorrow

1. the question if installed comes when your installer doesn't tell business one that the setup was ok

-> i recommend you to look at the setup sample from SDK ! i used that and created from it my own installer.

if you need help here you can ask me, but iam away the next day.

2. when you see in AddOn Manager the Status "Connected" your addon is running and you can be happy

lg David

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Ma. Luisa,

     This error occur, because some of your DLL's are not included in your .ard file.

You can watch this simple tutorial on how you compile your add-on.

http://scn.sap.com/community/business-one-sdk/blog/2012/05/18/creating-and-registering-add-on-on-sap...

Regards,

Former Member
0 Kudos

Hi Ana

The problem might be that the addon installation package was created

with a different version than Business One.

Please recreate the addon package (ARD file) using the same package

generator version as the client where you want to install the addon in.

Recompile the add-on and create the installer and the .ard file again.

Afterwards, please go through the note 819501 and correctly remove the

addon and re-install the addon with the new created addon package.

Regards,

Syn Qin

SAP Business One Forums Team

Nussi
Active Contributor
0 Kudos

Hi,

didn't try it with a .msi installer so far -> only with (own developed) .exe Setup

but the error message usually comes when you made a mistake creating the .ard file.

you have to choose the correct addon exe and installer in the .Ard Creating Window.

select the .Exe from the addon you have in the Installer Package and

than select two times the Installer Package. when you did this click "Create .Ard"

lg David

Former Member
0 Kudos

So if I would create the (.ard file), I will define the path for both executable file and installer. The executable file (.exe file) in the AddOn Exe Full Path and the installer (.msi file) in the Installer Exe Full Path. Then when I am on the process of registering the addon, I will only define (browse) the registration data file, the installer package is automatically defined after it. Do I get it right?

Thanks

Nussi
Active Contributor
0 Kudos

Hi,

looks like you got it

lg David

Former Member
0 Kudos

I will try it right now. Thanks!

Former Member
0 Kudos

Hi. I was installing the add on but it takes minutes just to finish the whole installation (depending in the estimated install time I define in the Add-On Registration Data Generator). I think it is still running and active because of the timer located at the bottom of the screen. I am waiting for the timer to stop, giving me the result of the installation. When the timer stopped, a system message appeared "Please wait for add-on installation to finish. Select Yes if installation finished successfully, otherwise select No.". What does this mean? when I choose Yes, the system prompted that the installation was failed; when I choose No, the system prompted that the installation was also failed. What do you think is the problem here?

Thanks,

Omann