Skip to main content
K
kchaithanya1-Visitor
1-Visitor
June 10, 2015
Question

Windchill PDMLink 10.2 M030 Installed with errors at Business Reporting

  • June 10, 2015
  • 4 replies
  • 4223 views

Hi All,

I've installed Windchill PDMLink 10.2 M030. The installation has been completed  but  with leaving two error at Business Reporting and Business reporting language pack.

Unable to find the reason for this.

Request you to suggest me  how to resolve.

(I'm here by attaching  error screen shot )

Thanks In Advance

4 replies

B
BineshKumar11-Visitor
1-Visitor
June 10, 2015

This screenshot does not give enough information on why it is failing. You should be looking at Windchill_10.2\Reporting\installer\logs\WBR_Install.log and ptc\Windchill_10.2\PSI\installer\logs\PTCSOLNINSTALLER_PtcInstall for additional information.

I have noticed this error when you are trying to install Cognos from installers located in network folder.

Thanks

Binesh

Barry Wehmiller International

K
kchaithanya1-VisitorAuthor
1-Visitor
June 11, 2015

Hi Binesh,

Thanks for your response.

I've searched for the above mentioned logs and found the below error.

Starting Cognos Failed: "CFG-ERR-0101 Unable to register IBM Cognos Service

I could not find any solution for this.

Kindly request you to help me on this issue.

C
ChrisSpartz13-Aquamarine
13-Aquamarine
June 11, 2015

That message is saying that Cognos failed to start. You'll have to check the cogserver.log to see why. The cogserver.log is located in your <Reporting>/logs directory.

    B
    BineshKumar11-Visitor
    1-Visitor
    June 11, 2015

    Do you see IBM Cognos service in your services? Make sure UAC is disabled.

      K
      kchaithanya1-VisitorAuthor
      1-Visitor
      June 12, 2015

      Hi Binesh,

      I could not find cogserver.log which you've  mentioned in specified location. Please find attached screen shot of that location.

      Also, I could not find any IBM Cognos related services from Windows services.

      C
      ChrisSpartz13-Aquamarine
      13-Aquamarine
      June 18, 2015

      Try testing the cognos configuration and see if that reports any errors. Open the cognos configuration utility by running <Reporting>\bin64\cogconfig.bat. Once the utility has loaded, go to Action->Test. If that reports any problems, check the details to see what is failing.

      S
      ssingh-21-Visitor
      1-Visitor
      June 12, 2015

      HI Krishna,

      As I have installed 10.2 M030 on 6 servers till now and every time I found this issue except one server.

      As per me, this is a Bug. After cognos installation, it creates a windows service as cognos, but does not get started automatically during installation process and then installation shows as failed for both cognos and language pack.

      I found a workaround for this issue.

      when installation fails, start Cognos service from windows services-cognos-start. Confirm services started.

      then again run the psi and this time select recover failed installation. Installation will be successful.

      Regards,

      Shekhr

        K
        kchaithanya1-VisitorAuthor
        1-Visitor
        June 12, 2015

        Hi Shekhr Singh,

        Thanks for your response.

        I could not find any Cognos services from Windows services

        S
        ssingh-21-Visitor
        1-Visitor
        June 12, 2015

        Hi Krishna,

        are you updating Windchill or is it a fresh installation?

        T
        tstacy2-Explorer
        2-Explorer
        June 19, 2015

        I ran into a similar issue when I was installing Windchill 10.2 M020. Our installation is on Linux with Windchill and the Gateway Server on one machine and Cognos10 on another.  We had multiple issues including missing 32-bit shared libraries and problems with the encryption key on the Gateway Server.  We had to work with Tech Support to resolve these issues and get our installation complete.  I didn't have any trouble with the Windows installation where all components were installed on the same machine. It really helps to find the actual error message buried in the log files.

        Terms & ConditionsAccessibility statement