AddOn Installation Failed On Terminal Server

Hello All,
I have created a addon in SAP B1 2007 B and when i am trying to installed the addon on the Windows 2008 Terminal Server
so that the client can log on to the AddOn through terminal server .But the addon is not getting installed and throwing an
error " AddOn Installation Failed  " and "Failed to Initialised the AddOn".
Thanks & Regards
Amit

Amit,
Are you logged on as Administrator on the Terminal Server and are you installing the add-on?  Windows Server 2008 is supported as of 2007B  PL09.  Are you at least at this PL level?
Eddy

Similar Messages

  • SQL Server 2008 R2 & 2008 R2 SP1 installation fails in Windows server 2012

    Hi All,
    I have a strange issue here. I have a Windows server 2012 VM where i want to deploy SQL 2008 R2 Enterprise edition.
    When i Run the setup every thing goes fine and during the installation wizard i get this error " The Folder path Program files contains  invalid characteristics. I get this error 3 - 4 times during the installation wizard and the installation fails.
    Below is the screenshot for the same.
    So i checked few articles regarding the compatibility issue and found the below article and upgraded my setup to SQL 2008 R2 SP1 using the below article.
    http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
    Again i still see the same above errors and with that a new error related to a MOF File.
    Below are the contents of the error logs. Can some one assist on this issue.
    ======================================================
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Exit code (Decimal):           -2068052692
      Exit facility code:            1212
      Exit error code:               1324
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Start time:                    2015-01-15 13:53:03
      End time:                      2015-01-15 14:04:29
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0xA60E3551%400xD3BEBD98%401211%401
    Machine Properties:
      Machine name:                  ALPCLDSCOM01
      Machine processor count:       4
      OS version:                    Future Windows Version
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      Installation location:         D:\SQLServer2008R2_SP1\x64\setup\
      Installation edition:          ENTERPRISE
      Slipstream:                    True
      SP Level                       1
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 E2KLAB\SCOMAC
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     D:\SQLServer2008R2_SP1\SP
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  E2KLAB\SCOMAC
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 E2KLAB\SCOMAC
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           E2KLAB\Gautamr,E2KLAB\SCOMAC,E2KLAB\SCOM Admins
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    1
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      Configuration status:          Passed
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Reporting Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\sql_common_core_loc_Cpu64_1033_1.log
      MSI error description:         The folder path 'Program Files' contains an invalid character.
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\SystemConfigurationCheck_Report.htm
    Gautam.75801

    Hi Alberto,
    Still the same issue.
    I installed the SQL 2008 R2 without SP1 and changed the service accounts to system account and  repaired the .NET using the .NET Repair tool
    Also changed the installation directory to D:\ Drive this time. Still same issue.
    log file:
    ===============
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Exit code (Decimal):           -2068052692
      Exit facility code:            1212
      Exit error code:               1324
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Start time:                    2015-01-15 22:55:37
      End time:                      2015-01-15 23:07:32
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SQLSysClrTypes_Cpu64_1.log
      Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.2500.0
    Machine Properties:
      Machine name:                  ALPCLDSCOM01
      Machine processor count:       4
      OS version:                    Future Windows Version
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      SPLevel:                       1
      Installation location:         D:\SQL Server 2008 R2 Datacenter edition for only Windows server 2008 R2\x64\setup\
      Installation edition:          ENTERPRISE
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              D:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           D:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   D:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           E2KLAB\Gautamr
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    1
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      Configuration status:          Passed
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Reporting Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SystemConfigurationCheck_Report.htm
    Any other suggestion i can try ?
    Gautam.75801

  • CUCM installation fails in ESX server

    Hi,
    I'm currently trying to install CUCM 9.1 in ESX server 5.1
    Attached snap is the error message and my server specs.
    Kindly help me on this.
    Thanks & Regards,
    Sakthivel M

    Hi All,
    Thanks for the support. I have changed the VM network Adapter settings to E1000
    as mentioned in the below discussion and working fine now.
    https://supportforums.cisco.com/discussion/11945106/critical-error-cucm-912-installation-failed-return-code-256

  • B1DE (AddOn Installer) for 64 bit server

    Hi All,
    I have a problem. One of my client has a 64 bit server. AddOn installation created with B1DE for SAP 2007 doesn't work on that server. After running SAP AddOn is trying to install, and then there is an error. Is there any way to create AddOn installation files that work on 64 bit server?
    Regards
    Hmg

    Both Robin and Owen are right... You need to run your code as forced 32 bit.
    The reason is the following:
    - A default project in Visual Studio is compiled as "Any CPU"
       - Any CPU means that you code will be executed as 32bit on a 32bit machine, and 64bit on a 64bit machine.
       - The Any CPU option is great for pure .NET (since all parts of it can run 32bit and 64bit)
       - In case of the SAP SDK and the AddonInstaller.dll, these are COM-based unmanaged code
          - If such unmanage code is not written to work with 64 bit, problems like yours can occur (this happens not only for SAP SDK... Tons of API out there have the same problems)
    - If you change the Any CPU option to the x86 option, you will force 64 bit mashines to run your code in "simulated" 32bit (Don't worry.. it is quite fast and gives no problems)
    We are you this with our 64 bit customers and without any problems...
    Lastly, if you wish to know more about this please hear the following podcast that describes the issue in detail (A good listen): http://www.dotnetrocks.com/default.aspx?showNum=341
    /Rasmus

  • Weblogic 10.3.0.0 installer - Failed to contact Server

    When clicking 'Next' on the 'Specify Download Options' portion of the wizard I get an error message "Failed to contact Server"
    Anyone know why I recieved this message or how I can get around it?

    OK , I have checked the log files for the server - it says it is using NON-BLOCKING source file:/dev/urandom
    Looks like this must have been sorted out in 10.3.5 as it recognizes the Linux System.
    I have the same issue on all 6 of the servers I have installed - so this may be a different issue.
    These are BL460c g6 HP blades in a c7000 chassis.
    So now I am at a dead end.
    The initial wait is still considerable, but we may have to live with this (Ubuntu Server 11.04 is still new and probably not supported well at this time)
    The admin console works fine once it initially opens and is fast.
    I tried the java command as well and got an error finding the main class in weblogic.wlst, (not the end of the world).
    all in all though it looks impressive right now, aside from the minor admin stuff, my application runs fine (which is what counts in the end).
    I will leave this open so that anyone else can view it and make suggestions.

  • Custom AddOn installation error on Windows Server 2008 64 bits

    Hi All,
    We have developed an AddOn that our client is currently testing on several Windows XP machines.
    My client requested to install it also on a Windows Serer 2008 64bits machine, so we have compiled it (both the AddOn and the Setup Installer) to x64 bits with Visual Studio 2005.
    However when we try to install it on the server and inside the SBO, we get the following error:
       An attempt was made to load a program with an incorrect format (Exception HRESULT 0x8007000B)
    The problem is that both EXE files (addon and installer) are in fact in x64 bit format because we get the standard error when we run with an 32bit machine (xxxx is not a valid Win32 application).
    Does anybody know how to solve this problem?
    Regards
    Manuel Dias

    Hi Manuel,
    This topic did come up in the forum, many a times by now, find the below links to the same.
    [Re: 64 bit windows (Exception from HRESULT: 0x8007000B)|Re: 64 bit windows (Exception from HRESULT: 0x8007000B)]
    [ Re: 64 Bit Programming SAP Add-ons|Re: 64 Bit Programming SAP Add-ons]
    HTH,
    Siju Dasan

  • TDS Addon,XL Reporter addon installation failed while connecting Citrix

    Hai!
    I am using SAP B1 PL 42
    I have installed, MS sql Client,SAP B1 client and Addons  in my citrix
    server.
    It's installed successfully and i able to log in,Connect TDS,XLR
    Addons.
    I publieshed SAP B1 in citrix.While i log in through citrix.
    TDS Addon and XL-reporter addon's are showing error and failed to
    connect.
    Error Msg screen shot is attahched in the SAP B1 Support Message.
    Message No: 922695
    [https://websmp102.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000610167&_SCENARIO=01100035870000000183&_ADDINC=&]
    Pl help me out in this issue.
    Note:i log SAP  with same user name
    Thank you.
    K.Thanga Raj
    09710445987

    Hi,
    I cant view the link of the error. are you running citrix remotely or from the box? are all components installed for TDS and XLR?
    Please refer to the link also :
    Refer this link
    ftp://ftp.citixsys.net/
    user name: national
    password: national
    Regards,
    Clint
    Edited by: clint pow on Nov 11, 2008 8:06 AM

  • Addon Installation Error on 2008 Server (64Bit)

    I have installed an Add-On of our development on various PCs' without any problem. However on a specific server during the installation process we get an error:
    "Error: An attempt was made to load a program with an incorrect format (Exception from HRESULT:0X800700008)"
    thats why i am cahanging my addon Code & Ard Proprties With CPU to x86
    but i am facing new problem with this " Error : Wrong Digital Signature"
    Client's Server is 2008 Small busness server 64 bit
    B1 PL is  13
    Thannks .

    Hello,
    after you have rebuilded your application in x86 mode, of cource you should rebuild the installer also and generate a new ard file.
    > but i am facing new problem with this " Error : Wrong Digital Signature"
    This error message coming by the ard should be regenerated.
    This means, all the exisiting installation should be updated.
    Regards,
    J.

  • Client Server product installation over Windows Terminal Server

    Hi,
    Have anyone tried installing oracle based client/server applications over WTS? I have a specific requirement wherein my WAN is connected on low speed lines. I've tried this installation but the performance seems to degrade very badly. Can you suggest me a solution to this issue. Further I'm facing problems when trying to print on Local printers. Any ideas???
    Thank in advance
    vinod

    Please see http://otn.oracle.com/products/forms/htdocs/formsservicesfaq.html
    It's stated here that this kind of installation is not supported. You would need to post a question on the Forms Forum for more details.
    Regards,
    Danny

  • Windows Patches installation fail on Windows Server 2008 R2

    Dear MS support
    We met a problem that we could not install any Windows patches on 3 Windows 2008 R2 Servers.
    Below is the Screen shot. Any Advice?
    Thanks
    Zi Feng
    TechNet Community Support

    Hi,
    Have you tries the fix:
    Error code 0x80000FFFF when you download updates on a Windows Vista-based computer by using Windows Update or Microsoft Update
    http://support.microsoft.com/kb/946414
    Hope this helps.

  • Print Dialog Box for Addon is not showing in Terminal Server

    Dear All,
    I have created a addon for Automatic Sales Invoice printing that prints the crystal report directly to the printer bu opening a
    print dialog box for printer selection through SDK code.
    The Same addon works fine on the server with print dialog box being showing through SDK code.
    But while running on Terminal Server , print dialog box is not showing any printer though printers are redirected to that
    terminal server.I am not getting whether the problem is in my addon or in the terminal server printer settings.
    Please suggest as i need to know the reason urgently.
    Thanks
    Amit

    Hello Edward,
    Thanks for your reply .
    But the problem is that while running on normal server the print dialog box appear with the printer name in my addon for printer selection .
    But while using terminal server , the print dialog box is not getting any printer in the dialog box .That's the major concern for me
    is their any way to check that why the printers are not showing in print dialog box.
    Thanks ,
    Amit

  • W2k3 End of Support 14 July 2015 + Terminal Server

    Hi, all!
    We use W2k3 for new installation projects with Terminal Server Licencing. We activate now our Termainal Server Licencing on https://activate.microsoft.com. After that we install CALs licenses per users and use this PC for our old applications.
    As Microsoft will support activation our servers licencing after 14 July 2015 when W2k3 is out of support?
    Thanks
    P.S: If I choose wrong place with my question please give me a link

    Hi, all!
    We use W2k3 for new installation projects with Terminal Server Licencing. We activate now our Termainal Server Licencing on https://activate.microsoft.com. After that we install CALs licenses per users and use this PC for our old applications.
    As Microsoft will support activation our servers licencing after 14 July 2015 when W2k3 is out of support?
    Thanks
    P.S: If I choose wrong place with my question please give me a link
    If it is already activated then it will remain activated. If you are asking if you will need to do extra activation in the future after that the OS gets out support then you might to check with a Microsoft Activation Center in your country.
    This posting is provided AS IS with no warranties or guarantees , and confers no rights.
    Ahmed MALEK
    My Website Link
    My Linkedin Profile
    My MVP Profile

  • Restrict Customised Addon Installation (Usage)

    Hi All,
    I have done the development for our one of the clients requirements. We are going to install the same in the client location. Actually we want to restrict the addon installation to only one server i.e., subsequently that addon shouldnt be used by some other company, it could be even their sister concern.
    Is there any way to restrict the addon installation? Is there any way to do through coding without getting SAP Licencing?
    Please clarify.
    Regards,
    SAPB1Use.

    Hi János,
    I feel your solution will work well. And one more clarification. I thought of giving the same Addon to other companys who are in Same Industry. But I want to restrict their use for 15 days only. I can capture the Addon Installation Date & I can compare the same with the Current date. By this logic, I could control.
    But actually, I want to restrict 2nd installation of Addon in the same server. How I can go ahead with that. I have one logic in mind, please tell me that will work or not.
    I will capture the System name in any of the system table while installing the Addon for the first time. In the 2nd installation, I will cross check the System Name. If it exists, I want to restrict the installation.
    My query is that, where can I restrict whether in installation of Addon or while opening the Customised screen.
    Please clarify.
    Regards,
    SAPB1Use

  • Restrict Customised Addon Installation

    Hi All,
    I have done the development for our one of the clients requirements. We are going to install the same in the client location. Actually we want to restrict the addon installation to only one server i.e., subsequently that addon shouldnt be used by some other company, it could be even their sister concern.
    Is there any way to restrict the addon installation? Is there any way to do through coding without getting SAP Licencing?
    Please clarify.
    Regards,
    SAPB1Use.

    Hi SAP B1 Use....
    Such kind of qusetion you should ask in SAP Business One SDK Forum.'
    There you get the right and quick answer.
    This forum is related to Functional side......
    Thanks & Regards,
    Rahul

  • IS_RETAIL Addon Installation

    Hi,
    I have installed SAP ERP 6.0 SR2 system.
    We need IS_RETAIL component on this same system.
    Is it possible to do addon installation IS_RETAIL on this server??
    If possible please let me know the steps.
    Thanks
    Amit

    Amit,
    Below thread may help you
    IS-RETAIL
    IS- RETAIL
    IS  RETAIL
    Thanks
    Sushil

Maybe you are looking for