Thanks to Diana Balan for all her work on this case of a failure in the PowerShell upgrade scripts when migrating from Project Server 2010 to Project Server 2013. We do have a fix request in to overcome this issue (I’ll try to remember to update when it is released!) – and there is a workaround too. The problem occurs when running the ConvertTo-SPProjectDatabase command – and it will fail after a short while with a message like the following:
ConvertTo-SPProjectDatabase : Action 22.214.171.124 of Microsoft.Office.Project.Server.Upgrade.ReportingDatabaseSequence failed.
At line:1 char:1
+ ConvertTo-SPProjectDatabase -WebApplication http://<servername> -Dbserver bris ...
+ CategoryInfo : InvalidOperation: (Microsoft.Offic...baseImplementor:ConvertToProjec...baseImplementor) [ConvertTo-SPProjectDatabase], SPU
+ FullyQualifiedErrorId : Microsoft.Office.Project.Server.Cmdlet.PSCmdletConvertToProjectServiceDatabase
This will occur if you have edited the SQL language of the user running the PowerShell command in the following dialog in SQL Management Studio (or you may have set it in SQL):
In my case to reproduce the issue I have set the language to German. This results in a German language error in the ULS logs too – the start of which says:
System.Data.SqlClient.SqlException (0x80131904): Bei der Konvertierung eines varchar-Datentyps in einen datetime-Datentyp liegt der Wert außerhalb des gültigen Bereichs.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
which even with my poor schoolboy German tells me that something about the date/time format is causing the problem. The actual problem is that using the German language (and others) will then set the ISO date format which mandates time as well as date. If you run a profiler trace then you see we have statement WHILE @CurrentTimeByDay <= '2149-12-31' and it is this which throws the exception.
Workaround - Setting the language to English for the user running the command will avoid the error.
For the search engines – the error you will get in the ULS logs in various languages (In no particular order):
These are just the Project supported languages – you could of course be set in SQL for a language that Project does not support – so the error may not be listed here…
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.