This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Where can and can't you install an automation server?

dkeyser over 11 years ago

I'm looking to install an automation server on a remote network but I'm running into an issue. When I install this on a test box on that network everything was fine. I can't keep the test box setup the way it is now so I wanted to install this on the DC (I know that's usually a very bad thing but the only other option I have is the SQL server and I think that would be a worse move) but every time I attempt this it will not connect to the SQL server to make a database. Is this due to it seeing itself attempting to be installed on a DC or is this just something funky with the SQL box? How much of an impact would this have on the SQL box if push came to shove?

0 David_Di_Blasio over 11 years ago

There's no software limitation to installing Patch Manager on a DC that I'm aware of. Are you using a domain administrator for the service account? Is this account granted sysadmin in SQL?
Cancel
Vote Up 0 Vote Down

Cancel
0 dkeyser over 11 years ago in reply to David_Di_Blasio

I'm using a credential that is domain admin and granted sysadmin and public on the SQL server.
Cancel
Vote Up 0 Vote Down

Cancel
0 dkeyser over 11 years ago

Any other thoughts as to this weird situation? I can log on every day with this user name and password as it is a domain admin for both domains. I've tried adding another user to SQL as an admin and all other categories enabled and still it won't connect.
Cancel
Vote Up 0 Vote Down

Cancel
0 David_Di_Blasio over 11 years ago in reply to dkeyser

You mention the username is domain admin for both domains, are we talking multiple domains here? Does the sql server host another EminentWare database? Typically an auto server is installed with local sql as there is not actually much stored for this role.
Cancel
Vote Up 0 Vote Down

Cancel
0 dkeyser over 11 years ago in reply to David_Di_Blasio

The patch manager is located on one domain but the automation server is to be set on another. The SQL server for the domain the the automation server is to be set on has no eminentware database on it at all though I'd like to add one for this automation server. This way I can keep the databases all together on this domain. Though I could ask the domain admin if I can install SQL express on his DC I'm not sure if he'll agree. Hence installing this on SQL 2008 r2 server that already exists. I've even had our SQL guy take a look and he doesn't understand why it's not working. Boggles the mind!
Sent from my iPad
Cancel
Vote Up 0 Vote Down

Cancel
0 David_Di_Blasio over 11 years ago in reply to dkeyser

I think the issue is likely related to the permissions the ewdgs service account has on the SQL server as this is the account that is attempting to create the database.
Cancel
Vote Up 0 Vote Down

Cancel
0 dkeyser over 11 years ago

Any steps on fixing this? I'm looking for this account in the management studio but I'm not finding it.
Cancel
Vote Up 0 Vote Down

Cancel
0 David_Di_Blasio over 11 years ago in reply to dkeyser

I don't have any specific steps I can provide, however I did discover today during a support call that we actually do now use the account you're logged in with to make the initial connection to the remote SQL server. From here you'll need to ensure the service account has DBO for ongoing communication. Are you able to connect to the remote database with SQL Management Studio from the server hosting Patch Manager?
Cancel
Vote Up 0 Vote Down

Cancel
0 dkeyser over 11 years ago in reply to David_Di_Blasio

I can with a SQL Server account. I can never figure out how to use my alternative domain credentials so I made myself a login. I can't use that login through the patch manager installer so I use my domain credentials which takes longer to return an error but still returns the same error as my local SQL account information.
Cancel
Vote Up 0 Vote Down

Cancel
0 dkeyser over 11 years ago

I've decided to create a ticket. Might as well be able to put some time to your day for help me if you are the one to pick it up.
Case #445221
Cancel
Vote Up 0 Vote Down

Cancel