Hi,

Its strange that the error only happens there and it should not happen in mixed mode. However I don't think the cause or solution to this problem will be found in mojoportal. I think you will have to google for the answer. Maybe this link will help, if not keep googling. Its some kind of sql server configuration issue in my opinion.

If you just now configured it for mixed mode you might try restarting the db or rebooting.

Hope it helps,

Joe

I don't think thats the solution. Thats should not be needed in mixed mode with sql logins. Is the db on a different machine? Is IIS configured for anonymous and integrated windows (as it should be)?

Are you using Sql for the stateserver instead of in process?

Are you using impersonation? (I don;t recommend it)

Are you up to date on service packs for SQL 2005?

These ere the things I would look at and if its not a production machine I would reboot the sql box and see if that solves it.

Hope it helps,

Joe

In mixed mode it should work without Trusted_Connection="yes" by using a sql login.

If your sql login was not dbo of the db I would try making him dbo.

With Trusted_Connection="yes" I'm not sure if its connecting to the db as you, the user logged into windows, or the aspnet account or iuser_machinename. I'd have to research it.

In any case if you changed the connection string since running the setup it could possibly be a factor in current issue as the context in which objects are created in the db can affect how they are used. I would try creating a new clean db and run setup again using your new connection string and see if  it works better after that.

Hope it helps,

Joe