August 17, 2015 at 11:05 am
Can someone help me with this scenario..
We have a domain environment, 1 SQL instance with 3 databases.
A few days back I applied a client software update to our workstations, it did update the db.
This software does connect to one of the db's.
Something in the update hosed security. All the other database and client software within the SQL instance work fine.. This particular application does not work, however..
If I log in as a specific user (marty), he was also the user I was logged in as when I installed the update.
But if I am logged in as him, launch the application, any user can login via the application.
Some kind of windows authetication..?
Excuse the newbness, I could use a hand asap.. thanks
August 17, 2015 at 11:38 am
paulcote444 (8/17/2015)
Can someone help me with this scenario..We have a domain environment, 1 SQL instance with 3 databases.
A few days back I applied a client software update to our workstations, it did update the db.
This software does connect to one of the db's.
Something in the update hosed security. All the other database and client software within the SQL instance work fine.. This particular application does not work, however..
If I log in as a specific user (marty), he was also the user I was logged in as when I installed the update.
But if I am logged in as him, launch the application, any user can login via the application.
Some kind of windows authetication..?
Excuse the newbness, I could use a hand asap.. thanks
I'm sure that what you described is clear as a bell to you, but it's not all clear to the rest of us as to exactly what you mean. You used the word "If" to begin a sentence, only to say that this user was the user you logged in as to perform the update. Then you have your "But" in a separate sentence, paired with "if", and restating that you are logged in as this user, followed by what appears to be the action of you launching the application, at which point any user can login via the application. However, you've already stated that the application does not work, so I'm really confused about how it "doesn't work", yet any user can login via the application...
Please be considerably more specific about what you mean by "does not work". Specify what happens when you launch the application, and what is supposed to happen, along with some basic details on what kind of application it is and what it's supposed to do. While the ultimate solution might mean having to go back to the vendor that sold it to you, we're in a rather poor position to help you because we have no idea what you're saying.
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
August 17, 2015 at 12:07 pm
Are you sure this is a SQL Server issue and not an issue with the application?
August 17, 2015 at 12:29 pm
ZZartin (8/17/2015)
Are you sure this is a SQL Server issue and not an issue with the application?
This is what's confusing me. As long as I am logged in as user "marty' via ad, any user can login using their application credentials and it works fine. Also all other database dependent apps are working fine.
Thanks
August 17, 2015 at 12:44 pm
paulcote444 (8/17/2015)
ZZartin (8/17/2015)
Are you sure this is a SQL Server issue and not an issue with the application?This is what's confusing me. As long as I am logged in as user "marty' via ad, any user can login using their application credentials and it works fine. Also all other database dependent apps are working fine.
Thanks
SO....only Marty who is an AD account can access the application or anyone who is an AD account can access the application?
if this statement is true you are having application issues not database issues and the fact that you can access via 'Marty' in AD says that this is an application issue not a database issue. If it was a database issue nothing would work, it would simply say 'cannot access database'
MCSE SQL Server 2012\2014\2016
August 18, 2015 at 5:27 am
This may or may not help.
We have an ancient third party application which was updated a few months ago. The update managed to get rid of column permissions.
Running the following script on a restore of the DB before the upgrade and then running the results on the currrent DB solved our problem.
-- Generate table/column permissions
SELECT P.state_desc COLLATE DATABASE_DEFAULT + ' '
+ P.[permission_name] COLLATE DATABASE_DEFAULT + ' ON '
+ QUOTENAME(S.name COLLATE DATABASE_DEFAULT)
+ '.' + QUOTENAME(T.name COLLATE DATABASE_DEFAULT)
+ COALESCE('(' + QUOTENAME(C.name COLLATE DATABASE_DEFAULT) + ')', '')
+ ' TO ' + QUOTENAME(U.name COLLATE DATABASE_DEFAULT) + ';'
FROM sys.database_permissions P
JOIN sys.sysusers U
ON P.grantee_principal_id = U.uid
JOIN sys.tables T
ON P.major_id = T.[object_id]
JOIN sys.schemas S
ON T.[schema_id] = S.[schema_id]
LEFT JOIN sys.columns C
ON T.[object_id] = C.[object_id]
AND P.minor_id = C.column_id
ORDER BY U.name, T.name, C.column_id
We have also come across authentication problems with windows update causing problems with COM services. Restarting the server hosting the services usually works.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply