This might be a Beta issue. And I'm using MySQL, which is working fine on other nodes and sections of the CMS.
I had a hiccup during setup, where MySQL rights weren't setup correctly. After a fail I submitted the connection information again and the dropdown was set on SQL Server. When I changed that back to MySQL all went well.
However on the root Content node it seems to try to connect to SQL Server anyway:
"System.Data.SqlClient.SqlException: Login failed for user 'myusername'"
On my dev machine I do have SQL Server installed, but no user named 'myusername'. (And I want to use MySQL because that's what I have on the server)
Apart from the UmbracoDns, is there another location where the connection is stored?
EDIT - I setup the site again and now it works. Not sure how it was stored though, restarting the AppPool didn't change anything.
Content node tries to connect to SQL Server on 6.1
This might be a Beta issue. And I'm using MySQL, which is working fine on other nodes and sections of the CMS.
I had a hiccup during setup, where MySQL rights weren't setup correctly. After a fail I submitted the connection information again and the dropdown was set on SQL Server. When I changed that back to MySQL all went well.
However on the root Content node it seems to try to connect to SQL Server anyway:
"System.Data.SqlClient.SqlException: Login failed for user 'myusername'"
On my dev machine I do have SQL Server installed, but no user named 'myusername'. (And I want to use MySQL because that's what I have on the server)
Apart from the UmbracoDns, is there another location where the connection is stored?
EDIT - I setup the site again and now it works. Not sure how it was stored though, restarting the AppPool didn't change anything.
is working on a reply...