How can we help you today? How can we help you today?

Cannot connect to server in same domain...

I have a server in my current domain. It is a SQL 2005 SP2 box and when i add it to the monitors, it says that the multipart identifier "databases.name" could not be found.

I can connect to this server just fine with SSMS and it is the default instance and port.

It also has an incident taht the RPC server is unavailable but the RPC Service and Locator are running (both automatic starts).

I have another machine with this exact same build and it is working correctly.

Any thoughts?

SJ
swjohnson
0

Comments

4 comments

Sort by
  • Nigel Morse
    Hi - another poster on the forums also found this problem. We think it's an issue when using linked servers where for some reason you have to use a alias for the fully qualified table name which in a particular query we're not doing!

    We've made a fix for this but we want to test it fully before sending it out.
    Nigel Morse
    0
  • swjohnson
    Ok, but this is a stand alone server and there are no linked servers nor aliases with this one--it;s about a simple of a SQL Server as they come.

    However, i will try the update you spoke about and let you know.

    Thanks

    SJ
    swjohnson
    0
  • Nigel Morse
    I've just realised that the new build should (hopefull) fix the SQL connection error - but you also have that RPC error. Is the account that is running the Incident Repository an admin on the machine you're monitoring?
    Nigel Morse
    0
  • swjohnson
    Yes it is in the Administrators group.
    swjohnson
    0

Add comment

Please sign in to leave a comment.