Log in using that Account and give yourself permissions that way. Sometimes, you just need to use the Service Account that the application is using. There are multiple ways to access a SQL Server for which you don’t have access, and I have written about this in the past: What’s more, the application locked down access so that the only account able to log into the SQL Server was the application’s own. A third party Application put it there as part of it’s own install. So, why was there a 32-bit version of SQL Server there in the first place? Well, I didn’t install it. Perhaps this was the reason that Ivanti didn’t do the upgrade. Since SQL Server treats the two as entirely different products, I can understand that but it would be nice if the Installer actually warned you of the difference instead of just not finding the Instance. Turns out that the installed version was 32-bit, and the patch that I was trying to use was 64-bit. This allows it to be put on a existing SQL Server that you have full control over – much easier to manage.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |