I’m not able to connect to my Azure database using “Azure Active Directory – Integrated” when using SSMS 17 or x86 ODBC connections, but I’m able to connect with SSMS 19 and x64 ODBC connections.
I know this has been discussed extensively before, my issue is similar to this posting:
Unable to load adalsql.dll error when calling Invoke-sqlcmd
In my case the x86 applications are not working and the x64 are fine. All of this seem to have started after installing SSMS 19, I have:
Both x86 and x64 ADAL files, I have also tried with each one without the other on my system:
C:\Windows\SysWOW64\AdalSQL.dll
C:\Windows\System32\AdalSQL.dll
…and their Registry entries is there:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSADALSQL]\TargetDir = C:\WINDOWS\system32\adalsql.dll
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\MSADALSQL]\TargetDir =
C:\WINDOWS\SysWOW64\adalsql.dll
When I use SSMS 17 I get this message:
I have removed both SSMS 18 and 19 and started from scratch but that did not help. I have followed the recommendations on the posting above with no luck. It seems that I have everything I need, but I can’t pinpoint what the issue is or what is that I’m missing.
Please read below.
If any of your applications use the Azure Active Directory Authentication Library (ADAL) for authentication and authorization functionality, it's time to migrate them to the Microsoft Authentication Library (MSAL).
All Microsoft support and development for ADAL, including security fixes, ends in December, 2022.
For more information, please read here.
As you can read here Microsoft intended to end support back in June 2022, but it extended support 6 months more. Have you considered to quickly migrating to MSAL.
Related
I am trying to access a file stored in a Microsoft Access database (I am working in Visual Studio Community 2015) and I ALSO have Office 365 64-bit version on my machine.
I set the Target CPU under compile to x64. I chose the database source type, and the dataset database model, when it asks me "which data connection should your application use to connect to the database?", I clicked New Connection, then I chose Microsoft Access Database File (OLE DB).
Under database file name, I clicked browse and selected the appropriate file (Sales.accdb). When I press "Test Connection" or Ok I get this error:
Unrecognized database format 'C:.....\Sales.accdb.
Any ideas as to what I am doing wrong?
It turns out that all I had to do was install the correct Access Database Engine which can be found at https://www.microsoft.com/en-us/download/details.aspx?id=13255
It installs and runs works perfectly now. I was apparently confused between the Access Database Engine needed by Visual Studio and the Access 2016 runtime which is a different thing altogether. This was pointed out to me by Gord Thompson.
The presence of the Office 365 is irrelevant - you need the correct MS Access DB Engine. See this SO post for details.
You need to do it in 32-bit MS Office (Access 2016 AKA Access 365 for now) with the 32-bit Access Database Engine. It works OK. Even though the two componets are both 32-bit, the Office has a small 64-bit installer file in it though, see the screenshot, and that has to be removed first - for how to see this advice.
The 64-bit Access 2016 with 64-bit Access Database Engine 2016 produce "The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine." problem.
On my computer SQL Server Management Studio is using NTLM rather than Kerberos as expected. Which is causing issues accessing linked servers.
I wouldn't think this would be a very hard issue to fix but there are a few weird points that prompted me to post here
If I log into another computer and launch SSMS I have kerberos
If someone else logs into my computer the auth_type is NTLM
I do get a Kerb ticket
My AD admin is assuring me that my user settings are correct and I match identically someone else that I know is not having this issue
My data architect suggested having me computer re-imaged to see if some software that I installed is making that happen but that did not help the issue if I only install SSMS on top of the fresh image.
I am currently using SSMS 2016
Any advice would be appreciated
I'm having a small issue and starting to tear my hair out unfortunately.
Please excuse me if this has been answered before but I've been searching for two days and nothing is working.
I have 2 computers, one is windows 7 which is the "Server" ( 3 administrator accounts, A,B,C)
The other windows 8.1 we'll call this "Client" (1 admin account same name as C)
The Server is running MSSQL express - 2014 with SSRS on Acc:A. I'm using the BIDS (on the server Acc:B) to create reports and deploy them onto the report server happily.
What I am needing to do is to be able to access the reports from my client pc but I cant seem to be able to find what is restricting me from accessing the reports or accessing it as a service reference in VS2013.
When I Log onto accounts (useing RDP) B,C I can access the reports server happily but I try to access the reports server from the client using "Server\C" as windows login credentials it says I don't have the privileges for the home page but I can access the Site Settings.
I have a nasty feeling this is all because I'm not running on a windows server environment with domains and such which I would rather not need to use till I deploy this (when I buy a proper server) as at the moment this is all trial and proof of concept stage.
Any help anyone can give would be absolutely amazing! Thanks
Finally managed to get it working after ages, it'll be different when I deploy it but, I simply disabled the ntlm authentication and went for windows basic authentication by doing step 4 in this documentation!
Thanks for all the help!
https://msdn.microsoft.com/en-us/library/8faf2938-b71b-4e61-a172-46da2209ff55(v=sql.110)
I am installing Srs Data Connector for MS Dynamics CRM, but on the systems checking were encountering an error "There is no such object on the server". I've tried googling it but to no avail.
UPDATE: Added some details
I'm running on 2 VM one for CRM app and the other for MSSQL
I'm installing the srs data connector to the MSSQL Server
Both Server is running on Windows 2008 r2
SQL Server is MSSQL 2008
Could be the permissions issue. Make sure NTAUTORITY\NETWORK SERVICE have permissions to access MSCRM_CONFIG. You might also need to reset IIS on CRM Machine after sorting out the access issue.
Is this on-prem?
If that's the case you may want to program in SQL as opposed to fetchxml - It's a lot more flexable.
That being said, if you want to continue to use fetchxml - make sure to point the ssrs data connector to your crm server and not the database server.
Just want to share the resolution and the cause of the problem (Well not the detailed cause).
The problem was caused by an issue on the AD configuration and the installation of the CRM and MSSQL.
After 2 weeks of trying to resolve various errors on the CRM installation including the above post the problem seems to be with the AD config.
We have many Domain controllers and changes on each DC were scheduled to be copied on the other controllers each afternoon. That's why some setup done by the CRM were not copied immediately.
We have tried re-installing the CRM and MSSQL but it also failed. The trick is to set up the CRM and MSSQL in the same DC then disable the CRM and MSSQL servers to connect to the other domain controller OR to replicate the configurations in the DC in real time.
After that all errors and warnings will be gone...
Thanks,
I've been given a VM for development purposes, in which is installed Windows 2008R2, CRM 2011, SQL Server, etc. Prior to me being given the project, the VM was being used inhouse, validating to the company's AD server.
Since I need to use the VM off-site, I have run "dcpromo" in order to install Active Directory etc. in the VM. As you may have guessed, upon doing this, nothing can now connect to SQL Server using Windows Authentication, because users are now AD users, with different IDs (at least I assume that's the problem - I'm no sys admin).
So when I run CRM Deployment Manager, it says it can't connect to the CRM_CONFIG database, assumedly because Windows Auth isn't working. SQL Server is running fine. In fact Windows Auth won't even work in SQL Mgmt Studio, I have to connect using SQL Server Auth.
How do I fix this mess? :) Is there a way of telling CRM Deployment Manager (and everything else) to use SQL Server Auth instead of Windows Auth? Or is there a way to fix Windows Auth on the machine? The latter would be preferable, as it would probably fix everything which now can't connect to SQL Server with Windows Auth.
I'm not sure how to fix this, but I would probably have a go at:
Uninstall CRM
Reinstall CRM - these steps should give you a working CRM, without any customisations or data.
Import the existing organisation - this should give you CRM as the original developers had it (as part of the import process you can remap all the users in AD).
Check out this link for detail on the process:
Import a Microsoft Dynamics CRM 2011 Organization
Also this may help:
Move the Microsoft Dynamics CRM 2011 deployment