[mdt] MDT and SQL

[garethEds]

Afternoon All,

 

I've not had an issue with MDT for a while now and it's been really smooth. Recently the MDT database connection seems to have broken - despite nothing changing on the server. The end of task sequence message throws errors that SQL cannot access the MDTDeploy$ share that it has accessed for the past x amount of months/years.

 

The database is still there in MDT. Nothing has changed.

 

Has anyone seen this before? How does the SQL server stop accessing a deployment share by itself?

 

Cheers

 

Gareth

[Boredguy]

The SQLExpress service is still running on the server isn't it, and it's not fallen over?

[garethEds]

The SQLExpress service is still running on the server isn't it, and it's not fallen over?

 

Hiya Pal,

 

Server has been checked and rechecked. The only one not currently running is SQL Server Agent - it's set to automatic and seems to only run when needed.

 

All others are running

 

SQL Server

SQL Server Browser

SQL Server VSS Writer

 

Cheers

 

Gareth

[Boredguy]

Same as we have running on ours then.

If you expand the Advanced Configuration > Database in MDT does it sill show the server name/instance that your expecting?

[garethEds]

Same as we have running on ours then.

If you expand the Advanced Configuration > Database in MDT does it sill show the server name/instance that your expecting?

 

Yes - everything looks good. Nothing has changed for ages. It just works - but slow now processing the rules.

 

Just waiting for a machine to build whilst I test recreating the shares.

 

Gareth

[garethEds]

Hi @Boredguy - here is the error message

 

Yellow box.

 

The network path was not found

 

The network path was not found

 

The network path was not found

 

The network path was not found

 

The network path was not found

 

ERROR - Unable to map a network drive to \\ygg-vMDT\MDTDeploy$

ZTI error opening SQL Connection: [DBNETLIB][ConnectionOpen (Connect().]SQL Server does not exist or access denied (-2147467259)

Unable to establish database connection using [CSETTINGS] properties.

 

Never had this before. Am at the point of uninstalling SQL and going again.

 

Gareth

Edited April 26, 2021 by garethedmondson

[Boredguy]

I assume you've already done the tried and tested technique of restarting the MDT server itself , so does sound like a strange issue.

 

Any error codes? I see the message with the codes now

[garethEds]

Question - your Build Account - what permissions does it have on the MDT Database in SQL? I'm thinking that is the issue after searching. Maybe the permissions are foobar.

 

G

[Boredguy]

Our DB is mainly used with read access as it just checks the MAC address to get the computer name/OU/Task sequence etc.

 

Server IP has not changed recently has it? Might be worth checking that TCP/IP access hasn't accidently somehow been disabled for SQL

Open SQL Server Configuration Manager

Expand SQL Server Network Configuration

Select Protocols for MSSQLSERVER

Double click TCP/IP on the right