Which mssql driver are you using in config.php?

The odbc_mssql driver.

Sorry, can't reproduce. When I export the startdate is empty here. I guess for some reason there is a 0 in your mysql DB in the startdate field. Can you check?

lisnalinchy, please give feedback or we will have to close this issue.

My apologies, I have just returned from annual leave.

Just had a look in the lime_surveys table - startdate is set to NULL across the board bar one which has an actual start date of 2010-11-23 00:00:00

lisnalinchy, I don't understand - either the startdate is set to NULL or it is set to 2010-11-23 00:00:00 ?

There are 15 surveys - all the surveys in the table with the exception of one have a start date of NULL. There is only one survey in the table with an actual start date.

So when you export such a survey with a startdate of NULL in the DB then the export file contains a 0 instead? Can you attach such a file? What driver are you using, mysql or mysqli on server?

I can replicate this if, on the linux/mysql box I set a start date for the survey and then try to import it into the windows/MSSQL box.

The error on import into the Windows/MSSQL box is:

Error: Failed to insert data
INSERT INTO lime_surveys ( SID, OWNER_ID, ADMIN, ACTIVE, EXPIRES, ADMINEMAIL, PRIVATE, FAXTO, FORMAT, TEMPLATE, LANGUAGE, ADDITIONAL_LANGUAGES, DATESTAMP, USECOOKIE, NOTIFICATION, ALLOWREGISTER, ALLOWSAVE, AUTONUMBER_START, AUTOREDIRECT, ALLOWPREV, PRINTANSWERS, IPADDR, REFURL, DATECREATED, LISTPUBLIC, HTMLEMAIL, TOKENANSWERSPERSISTENCE, USECAPTCHA, BOUNCE_EMAIL, STARTDATE, PUBLICSTATISTICS, PUBLICGRAPHS, ASSESSMENTS, USETOKENS, ATTRIBUTEDESCRIPTIONS, EMAILRESPONSETO, TOKENLENGTH ) VALUES ( 33397, 1, 'Michael Ross', 'N', '2011-04-26', 'michael.ross@nhsleeds.nhs.uk', 'Y', '', 'G', 'default', 'en', '', 'N', 'N', '0', 'N', 'Y', 0, 'N', 'Y', 'N', 'N', 'N', '2011-04-12', 'N', 'Y', 'N', 'D', 'michael.ross@nhsleeds.nhs.uk', 2011, 'N', 'N', 'N', 'N', '', '', 15 )
[Microsoft][ODBC SQL Server Driver][SQL Server]Operand type clash: int is incompatible with datetime2

I have uploaded the LSS file I used for import as requested.

I am using the mysql driver on the Linux server.

If I do not specify a start date, the import works fine. If I do specify a start date, I get the error.

Looking at the importsurvey.php script, it actually sets the start date to 0 rather than NULL which (as you can see from the error) does not work. This is actually a documented issue with MSSQL 2008 and above.

Correct to the above feedback:

It does not matter if I specify a start date or not, I still get this error. I had forgotten to remove my fix before testing. Returning the original importsurvey.php file results in this error being generated every time.

I can import the attached file just fine on my MSSQL 2008 server with LimeSurvey 1.90 (9642)
Are you sure the LimeSurvey version on the destination server is up to date?

Version is reporting as: Version 1.90+ Build 9642 on both servers.

I will try creating a new instance of Limesurvey on our Windows/MSSQL box and test the import.

Please do. Maybe the installation on the server was updated in the past and not allf iles were properly replaced with new versions.

lisnalinchy, I too have MSSQL2008 (R2) and have discovered that more than just this one table have NO default values set. Can you confirm if any default values are set in any tables and if any identity parameters have been set?

In MSMS you can open columns, right click and choose modify. Then scroll through the properties. The default value should be set there and if an identity is required it will be set to Yes and 1 and 1. Thanks!

medicnick, this is not a problem of neither a missing default value nor missing identity. Please don't interfere.

I must apologies that I have not yet managed to get round to this. I am currently snowed under with other work. I will be doing this on Monday.

I have built a new Limesurvey/Windows/MSSQL box and the issue appears to have gone. It looks like the issue was due to some files that had not been updated during that last update. For reference, I had used the web based in-line upgrade. I will probably do this by hand in future.

Many thanks for all your help and time.

There is still an issue here. I have just clean installed the latest version on both our linux and windows boxes. Testing an import, the import fails with the same error. Both version are identical except one is running on linux with MySQL and the other is running on Windows Server 2008R2 (iis 7.5) with MSSQL 2008R2.

A simple fix is to insert:
$insertdata['startdate']='null';
into import_functions.php at or around line 1170.

As far as I understand, startdate is supposed to be set to null anyway for an import. No harm in reinforcing it and it resolves the issue.

I am sorry but by now your version is old. Please update to 1.91+ and see if the issue is resolved there. Feel free to re-open this if you can still reproduce it.

Apologies, perhaps I was not very clear. In my comment I referred to the latest version - I should have been more specific and said '1.91+' - the latest available stable release as of today - is the one I am using.

There does not appear to be any way to change the 'Product version' in the details table above i'm afraid. Do you want me to re-open this as a new report?

Even though I cannot reproduce the issue at all I put in a similar fix now for the .lss import.

New 1.91+ version released