April 7, 2016 at 7:01 am
Hi,
Are you trying to create this folder "dev" by SSMS, T-SQL or PowerShell ?
Johan Jezequel
** Sorry for my english, I promess you I do my best **
April 8, 2016 at 3:43 am
Through SSMS only i am trying to create.
April 8, 2016 at 3:54 am
It seems it could be a collation issue, please check this out :
Johan Jezequel
** Sorry for my english, I promess you I do my best **
July 11, 2016 at 10:30 am
Johan_1975 (4/8/2016)
It seems it could be a collation issue, please check this out :
Nice find. Unfortunately it isn't very helpful, since the link is from 2010, reported "bug is fixed", and the work-around is to use native US-English collation. Not a good option for companies who isn't already using that collation.
July 11, 2016 at 10:36 am
I just had - and solved - the same issue. I found many suggestions which didn't work. This one did the trick for me:
ALTER AUTHORIZATION ON DATABASE ::[SSISDB] TO sa;
ALTER DATABASE [SSISDB] SET TRUSTWORTHY ON;
(Of course: change the database name according to your environment)
It didn't matter that the database authorization belonged to a sysadmin. It doesn't matter either that sa is disabled on my system (a disabled login can own objects, but do nothing with them!). It had to be set like this, right now.
Then I was allowed to change the TRUSTWORTHY setting (regardless whether it was already "TRUSTWORTHY ON").
And then I was allowed to create a new folder. :w00t: Problem solved.
February 11, 2020 at 3:28 am
I know this thread is old but whoever comes across the same issue , try with Windows Authentication instead and see if that fixes your issue. It did for me
Viewing 6 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply