Hi Dagur,

I can think of a few reasons:

- your account doesn't have enough rights on the MOSS content database. Since youre not running the code from a MOSS site itself, the database might not know you. Either run the code as a local admin, or make yourself a db_owner in the content database.

- In your web application policy, rights for the site owner have been overruled. See Central Administration > Application Management > Policy for Web Application

But without further details, this is a guess. Are you working on an environment were you are the administrator, and what does the log say? Do you have the

same problem if you run other external code?

The problem might also be solved if the code is run with elevated privileges (SPSecurity.RunWithElevatedPrivileges). I do not wish to create a security hazard, however.

Alfred