Even though the collection security properties allow my user account all the permissions I cannot create any new collections. Every time I do the message below appears. Has anyone else had the same issue or even better got a fix for it. I'm running SCCM R2 as a single primary site server connected to a SQL Cluster database which is a seperate server. Setup was unable to create collections(s). verify that your account has create rights on the collection class. 0x80041001

Hello,I think that error means exactly what it says - your account has no permissions.Please try SCCM | Site Database | Security Rights | Rights and check from the list if your particular account with which you are running the admin console has Name [account], Class Collection, Instance (All Instances), Permissions - Read, Modify, Delete, Create, Read Resource as the minimum.Restart your Admin Console later on, just in case there is an MMC issue.Regards,Akin

The permissions seem to look OK. I've used the same account throughout the whole process, server build, sccm build etc. Is there a way of looking a llittle bit deeper into the permissions to see if its filtered through OK. BTW thanks for your response.

Hello,The results pane where you viewed users is probably the best visual indicator of what rights an account has.Try to see if your account can create a Package, Advertisement or Report, since it was the account that built the environment.Then consider copying rights from the NT AUTHORITY/SYSTEM account, this should set all the rights for your account.I have seen one instance of administrators removing the account that installed the site or reducing the privileges that account has - in which case Running Setup to do a site maintenance or reset and reapplying default file and registry permissions should be a last resort resolution.Let us know how you get on.Regards,Akin

If you are using the same account you used to install Configuration Manager, then you would have all the rights required. You should very easily be able to go to: Security Rights\Users\useraccount and then use User Security Rights to see what is set. If you have Create on the Collections class, then you should be fine.

Well, I cracked it in the end. The DBA's who look after the SQL server had applied an audit style stored procedure to any new databases collected. It had a negative result as it didn't allow tables with NULL values to be created. *%$*%"^ DBA's!!! I figured it was a SQL problem as in the status logs it was coming up with loads of SQL issues. Thanks for your time helping me with this appreciated.

I'm having this problem - can you explain how to configure SQL to allow NULL values please? Thanks, MRaybone.

me too - same problemplease expand on your solution masbyMikebigmike

Hi This issue comes since you had login in diffenent account. So check your system account since you had installed sccm application and sql database. Hope issue will be resolved.