Skip to Content
avatar image
Former Member

SAP Crystal Server 2016

We're trying to install a trial version of Crystal Server 2016 onto a 64 bit Windows 2012 R2 Server to ensure it would work for our customer's purposes.

We installed with the default settings, using a new Tomcat server and etc., except for the database type, where we opted to use Microsoft SQL Server. We already have a Microsoft SQL Server instance already installed onto this server.

After a few menus, we find that our Microsoft SQL Server instance isn't found/recognized by the installer. It doesn't show up in the menu which asks us to select the server instance to continue the install. An old DB on the server instance does appear, named BOE11, but this DB is from an installation of Crystal Server XI and as such the installer pulls up an error that the architecture of the BOE11 DB is incompatible with the new install.

We are not sure why the server is not recognized by the installer. We have had troubles with Crystal recognizing our administrator login info to that server, which may be causing the problem, or it could be something else.

We would like to continue using Microsoft SQL Server, but we need to know how to fix this issue before we continue to purchasing a license.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Apr 13, 2018 at 11:14 AM

    To add to Daniels reply - this could also be due to DNS configuration, maybe your new SQl Server DNS is not setup in the System DNS, so that is why only old SQL DNS shows up ?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      This is the issue we were having. We had to configure a new DNS and once we did, the installation proceeded smoothly. Thank you!

  • avatar image
    Former Member
    Apr 12, 2018 at 11:49 PM

    Hi Seth,

    There are a few things that could be part of a solution.

    Firstly I would ensure that the versions being used are listed as supported in the SAP Product Availability Matrix (PAM) document for C

    rystal Server 2016, however for some unknown reason there doesn't seem to be one currently for this version of the product. is the information page for the product which you may already know.

    The PAM for BI Platform 4.2 should be the same for Crystal Server 2016 however not 100% certain. I generally work with full BI Platform and not Crystal Sever which is a subset. On the CMS + Audit Repository page it will list the versions of SQL Server that are supported for the CMS database and the database driver that would be needed for it to work.

    There are times when what we have customers do is install the full product, including the database that ships with the product. Then once that is done and all is working well, you go into the CCM (Central Configuration Manager) and point the CMS database to an external database that we support. Once that is done then you can simply stop and disable the database that ships with the product and go ahead with using the product. This way you can get past the issue, and know better if there is an issue with supporting the database that you want to use.

    It can also be an issue with any installed database driver, need to remember CR Server is 64 bit so the database client for the CMS needs to be 64 bit. Developing Crystal Reports would use 32bit drivers.


    Add comment
    10|10000 characters needed characters exceeded