• State Verified Answer
  • +3 person also asked this people also asked this
  • Locked Locked
  • Replies 15 replies
  • Subscribers 62 subscribers
  • Views 32437 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Can't get SQL PI enabled on a new instance of Foglight

john.waclawski
over 7 years ago

I'm getting our 5th instance of Foglight set up and SQL PI is proving to be difficult to get running.  I'm going into detail to hopefully answer questions ahead of time.

My set up: (the specs here are the same on my previous 4 Foglight instances which work fine)

  • Database Server
  • Management Server
  • Agent Management Server

When I add a new server to this instance to be monitored, through the "Monitor -> SQL Server" wizard, this is what my initial screen looks like before I click "Monitor"

When I click "Monitor" things go through with no problems.  I've done this over 50 times so I know the drill.

It then gets to the following screen & this runs for ~10 minutes before throwing an error:

This is the error I get after about 10+ minutes of spinning:

Now I could contact Dell but I don't give up that easily.

I add the server but without SQL PI.  That works with no problems.

I go into the administration section of the server to try to add SQL PI manually but immediately notice that there isn't a repository host attached.

(I apologize for the tiny jpg.  This is actually very easy to see but it appears the editor shrinks it down.  But under "SQL PI Repository Host" it says "No SQL PI repository attached".)

 

So I attach our repository host using step #1.

 

When I click "Apply" it now shows up under the "Repository Host" column.

I select the server to have SQL PI enabled & click the "Enable" button.

It goes through its procedure that I'm familiar with and again, for 10+ minutes it sits and spins at this box:

After the customary 10+ minutes it errors out & says:

(The error says "Failed to enable SQL PI monitoring extension")

I've reconfirmed all rights to the servers & they are the same as they are on the other 4 I set up with no problems.

Now before I contact Quest for this, is there a log I can dig into to find out why this didn't enable?  Or is there something I can look at to find out what needs to be done?  I've used this procedure several times and know it works & I am familiar with it.  It would just be nice if Foglight offered some decent error logs or why something doesn't work.  Instead you are forced to go hunting.

 

Thank you for reading this far.  Hopefully if this gets fixed here, it will help someone else as well.

  • 0 over 6 years ago

    Hi foglight.admins,

    Just to confirm, with Infobright 5.0.4 installed you are getting issues where adding the PI installation when creating a new DB agent times out and then states "Failed to establish connection to the PI repository" from the FMS?

    Are all of these using the same PI repository and FglAM servers, to eliminate this as the cause?

    If these are different FglAMs or PI repository, then
    - each FglAM and PI repository server must have the Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) installed. There is an error in the release notes that will be fixed in the next cartridge to correct a note that later versions are compatible. This is incorrect, it specifically must be the 2010 version.
    - The 5029 TCP port must also be open between the FMS and PI repository.
    - The sizing requirements for the FglAM and PI repository must be met or exceeded. Right now about 80% of the SQL PI issues are related to incorrect sizing or missing CPU and memory reservations.

    For logs, I can suggest trying the connection or enabling the PI extension for the agent, and then looking at the tail end (last few hundred lines) of these two files
    - FMS log
    - DB_SQL_Server_Installer log (this is on the FglAM server where the Database Agents are installed, which may not be the PI repository).

    To expedite troubleshooting, I would recommend opening a Service Request for a Support Engineer (SE) to assist with this as it is easier to investigate directly in the environment and the SE is familiar with logs coming from the DB agents.

    John

  • 0 over 6 years ago

    Hello John,

    thank you for the follow up.

    We get the next error:

    All of the Agents are using same PI repository and FglAM.

    We have a Support Case opened with all the information: SR Number:4166244

    Thank you and regards,

  • 0 over 6 years ago

    Hi foglight.admins,

    KB 232399 is a comprehensive list of some of the common issues and KB 146730 is more specifically for this error message.

    Insufficient sizing for one of the PI environment components and the lack of VM reservations are the most common PI issues. An installation that might complete one time may not at a different time because of the shared nature of resources on the VM server. In this example, monitoring an Express installation of SQL Server would require less resources than monitoring an Enterprise edition.

    Our Support Team will review will follow up through the Service Request process where they have access to the log files (support bundles) and your contact information for a webex to review the environment.

    John

  • 0 over 6 years ago
    Hello John,

    as discussed via the Support Case the solution has been to upgrad the SQL Server cartridge to latest version "5.7.5.41" (we were running version "5.7.5.35").

    After that, finally, we are able to enable SQL PI in our Agents.

    Once again thank you very much for your support.

    Best regards,

    Eneko
  • 0 over 6 years ago
    Thank you Eneko for confirming that the issue was resolved with the newer cartridge.

    For clarification, the most recent discussed was a permissions-related issue caused defect SSFOG-400 that was present in a an early release of the 5.7.5.35 cartridge. Related errors could be seen from the SQL Server database agent log file. Example messages and more information on these types errors are detailed in KB 226170.

    As a general note, since each new database cartridge includes known fixes and enhancements from the previous releases, we typically recommend installing the most current database cartridge as a path of investigation.