SQLMonitoring Tool Client Issue

Oct 28, 2010 at 6:08 PM

This my first attempt at running SQLMonitoring Tool.  Client gives "stopped working" error at startup.

Setup Summary:

  • Database was installed on Server A
    • Server 2008 R2 Standard 64/SQL Server 2008 Enterprise 64
    • Files were copied in and attached in default instance
    • Domain Login A was created to run the SQL Server Service
    • Firewall - Off
  • Service was installed on Server B
    • Server 2008 R2 Datacenter 64/SQL Server 2008 Enterprise 64
    • Files were copied in
    • Domain Login B was created to run the service
    • Config file was edited
      • FQDN of Server A was used as the ConnectionString
      • Path to local folder was created for ErrorLog
      • CheckHeartBeat was true - left it as it was
    • Installutil was used to install the service
      • Install phase completed successfully
      • Commit phase completed successfully
      • Service started successfully
    • Domain Login B is in the SysAdmin Role and Local Admin Group
  • Installed Client on Workstation A
    • Windows 7 Enterprise 64
    • Files were copied in
    • Config file was edited
      • FQDN of Server A was used as the ConnectionString
    • Workstation Session Login is SysAdmin on default instance of Server A, and in the db_owner role of the SQLMonitoring database

Similar client error occurred when trying to run the client on Server A with a Domain Admin Login

Any ideas?

Coordinator
Oct 29, 2010 at 4:45 AM

Thanks for installing the SqlMonitoring tool.

The setup shouldn’t be a problem. I haven’t put the most try/catch effort in the client. The most crashes are due to missing information. Is this on startup? Or when you navigate to one of the menu’s?

Could you check the windows eventlog for more information. There should be an entry there.

From: SurferMike [mailto:notifications@codeplex.com]
Sent: donderdag 28 oktober 2010 20:09
To: robert@hartskeerl.nl
Subject: SQLMonitoring Tool Client Issue [sqlmonitoring:232689]

From: SurferMike

This my first attempt at running SQLMonitoring Tool. Client gives "stopped working" error at startup.

Setup Summary:

  • Database was installed on Server A
    • Server 2008 R2 Standard 64/SQL Server 2008 Enterprise 64
    • Files were copied in and attached in default instance
    • Domain Login A was created to run the SQL Server Service
    • Firewall - Off
  • Service was installed on Server B
    • Server 2008 R2 Datacenter 64/SQL Server 2008 Enterprise 64
    • Files were copied in
    • Domain Login B was created to run the service
    • Config file was edited
      • FQDN of Server A was used as the ConnectionString
      • Path to local folder was created for ErrorLog
      • CheckHeartBeat was true - left it as it was
    • Installutil was used to install the service
      • Install phase completed successfully
      • Commit phase completed successfully
      • Service started successfully
    • Domain Login B is in the SysAdmin Role and Local Admin Group
  • Installed Client on Workstation A
    • Windows 7 Enterprise 64
    • Files were copied in
    • Config file was edited
      • FQDN of Server A was used as the ConnectionString
    • Workstation Session Login is SysAdmin on default instance of Server A, and in the db_owner role of the SQLMonitoring database

Similar client error occurred when trying to run the client on Server A with a Domain Admin Login

Any ideas?

Read the full discussion online.

To add a post to this discussion, reply to this email (sqlmonitoring@discussions.codeplex.com)

To start a new discussion for this project, email sqlmonitoring@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com