fyi all related gemini issues can be found through this issue: http://support.dotnetnuke.com/issue/ViewIssue.aspx?p=0&id=1608

DNN Blog | Twitter: @erikvb | LinkedIn:

>Unfortunately these errors are in the sqldataprovider files themselves.

it is also a problem in some 3rd party modules. Testing is being done on a default install of the sql server and the code is then being run on the 3rd party sql servers that are not set to the default install.

In house testing here on all modules used over client sites fell into the same trap - runs ok on the inhouse testing configuration but fails on the 3rd party server. We have since reconfigured the inhouse server to exactly match the 3rd party servers to find these errors before putting the modules out on client sites.

simply comes down to the use of lower case in field names and in some cases tables - also on some 3rd party modules the tables referenced in joins are not prefixed with owner.

Did further testing.

Correction on my first post. I finally found out the overall collation of the server I was working on - its Latin1_General_BIN.
Seems this is case sensitive and is the route of my problems.

I can not install onto this box and as its the main development machine for our group this is a major issue. It also can be an issue deploying third party.

What I might be able to do on my current project is run it initially off a sql express 2005 db and migrate the db file out to my 3rd party hoster (solution proposed over on www.dnncreative.com - cant remember the issue)

It shouldnt be this hard to track down the reasons for install failures - the error messages are way too cryptic - it took me a considerable amount of time to work out what was going on. Perhaps I should post on Gemini...