Jefferson ELIAS

Hi there we experience the same issue when upgrading. sk.php file exists and is accessible to apache. Same goes for settings.php. The PHP error log states an issue with null...

Hi, I think so.

Hi, unfortunately no.. I'll give a try to explain... Let's say I have following page: ``` ``` To me, there is no need to generate an almost empty ToC ......

No, not really. We finally decided to create a fresh new installation and copy passwords from legacy to new system.

I have found a way to fix it. You will find attached a customized version of Invoke-SQLCmd2 which - has a new parameter called "OutputFile" (to allow to PRINT messages...

@niphlod Personally, I'm used to use PRINT to log info/debug messages. In this case, I think neither `-Verbose` nor `MessagesToOutput` parameters are appropriate. Let's consider this simple case: ``` PRINT...

Hi, personally, I modified Invoke-SqlCmd2 to do this: ``` if ($MessagesToOutput) { ... } else { if($OutputFile) { $conn.FireInfoMessageEventOnUserErrors=$false # Shiyang, $true will change the SQL exception to information $OutToFileHandler...

Well, it's a very old subject and I don't remember all the testing I made before, but, according to my comment : ``` Let's consider this simple case: PRINT 'test...

Could you try to raise an error and check that this error would be also thrown inside Powershell ?

Well, it's almost what I want, but here is the content I get with your test script: `get-content .\t.txt` > Running Invoke-Sqlcmd2 with ParameterSet 'Ins-Que'. Performing query 'print 'hello world'...