Users

All Posts (3)

avatar

jbrannick

is there a need to upgrade from 2022.2.33.0 to version 2023.3.24.0 first, then finally to 2023.3.25.0?

avatar
avatar
avatar
avatar

1) Local Machine - SSMS w/Integrated Security - NO

2) Local Machine - SSMS w/SQL Login - YES

3) RDP'd to SQL Server VM - SSMS w/Integrated Security - YES

4) RDP'd to SQL Server VM - SSMS w/SQLLogin - YES

Given this, RDM should work when SSMS works and not when... well you get the point.

It’s not necessarily an RDM issue but more of a configuration issue.

For example, is the local machine AD-joined? If you start SSMS with runas /netonly /user:domain\username ssms.exe, does that make it work?

When you say "configuration issue" ,,,is that SQL Config or AD Config or VM Config?..and any guidance on where to look?

TYVM!

is there a need to upgrade from 2022.2.33.0 to version 2023.3.24.0 first, then finally to 2023.3.25.0?

avatar
avatar
avatar
avatar

1) Local Machine - SSMS w/Integrated Security - NO

2) Local Machine - SSMS w/SQL Login - YES

3) RDP'd to SQL Server VM - SSMS w/Integrated Security - YES

4) RDP'd to SQL Server VM - SSMS w/SQLLogin - YES

Connect to RDM - RDP'd to SQL Server VM - w/Integrated Security - NO

Connect to RDM - Local Machine - w/Integrated Security - NO

Connect to RDM - RDP'd to SQL Server VM - w/SQLLogin - YES

Connect to RDM - Local Machine - w/SQLLogin - YES

is there a need to upgrade from 2022.2.33.0 to version 2023.3.24.0 first, then finally to 2023.3.25.0?

avatar
avatar
avatar
avatar

FYI: We are having the same issue , but if I create a SQL Login (vs Integrated Security) and use that login, it works. Its a work around, but at least we can get in...

1 - 3 of 3 items