Clustered SQL Server issue.

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

Clustered SQL Server issue.

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Operating System Deployment >> Clustered SQL Server issue.

Page: [1]

Message

<< Older Topic Newer Topic >>

Clustered SQL Server issue. - 11/24/2008 6:10:25 PM

JonathanRandle

Posts: 1
Score: 0
Joined: 11/24/2008
Status: offline

I'm having an issue running ZTIGather against a SQL 2005 Cluster using integrated security. We've been running BDD2007/MDT2008 against a non-clustered SQL server for over a year with no issues. We're standing up a new instance at another location that is using clustered SQL 2005. When ZTIGather runs with the image user account logged in, it is able to connect to the cluster and process fine.

When logged in with a local account and running ZTIGather, it errors out

![LOG[ZTI error opening SQL Connection: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. (-2147467259)]LOG]!><time="11:18:50.000+000" date="11-24-2008" component="ztigather" context="" type="3" thread="" file="ztigather">

Here's the contents of customsettings.ini:

Priority= Default, CRoles
[DEFAULT]
UserID=USERNAME
UserPassword=PASSWORD
UserDomain=DOMAIN

[CROLES]
SQLServer=SERVERNAME
Instance=INSTANCENAME
Database=DATABASENAME
Netlib=DBNMPNTW]
Table=ComputerRoles
SQLShare=admin$
ParameterCondition=Or

Has anyone run into this issue when using a SQL Server Cluster?

Post #: 1

RE: Clustered SQL Server issue. - 11/25/2008 1:03:44 PM

kodiak_da_bear

Posts: 33
Score: 0
Joined: 5/5/2008
From: Minneapolis, MN
Status: offline

I had this same issue, but it wasn't with a clustered sql. It turned out my local account didn't have access to the table in sccm, but the account had access to the database. Check your access on the table in sql to make sure you have access to it with that account.

(in reply to JonathanRandle)

Post #: 2