This project is read-only.

Log Files does not save the all the Powershell console messages

Aug 22, 2015 at 1:38 AM
Hi guys,

I'm not sure if it is a bug or I'm missing some config here.

I'm running the new SPSP version 5.0.4.6440 and I noticed that most of the console log messages have not been saved in the log file, as it used to be in the old SPSD versions.
I've tried to config it in the both ways, with and without the LoggingConfiguration Extension. In both scenarios the behavior was the same.

Is it the expected behavior in this new version, a bug or some configuration that I'm missing?

Thanks in advance.

Regards,
Marcus Gaspar
Aug 26, 2015 at 9:15 AM
Hi Marcus,

actually the SPSD logging is just a dump of the console output. So if you are seeing the logging messages in the console it should be written into the log file.
Are you using a custom console to execute SPSD?

SPSD checks if you are using the consolehost and scripts the Transcript otherwise because it is not supported everywhere
See SPSD_Utilities.ps1
#region StartTracing
        # Desc: Start tracing the PowerShell Output to a file
        Function StartTracing()    {
            $script:LogTime = Get-Date -Format yyyyMMdd-HHmmss
            $script:LogFile = "$logDir\$LogTime-$Command.log"
            if((Get-Host).Name -eq "ConsoleHost" -and -not $isAppHost){
                Start-Transcript -Path $LogFile -Force
            }
            $script:ElapsedTime = [System.Diagnostics.Stopwatch]::StartNew()
        }
        #endregion
        #region StopTracing
        # Desc: Stop tracing the PowerShell Output to a file
        function StopTracing(){
            if((Get-Host).Name -eq "ConsoleHost" -and -not $isAppHost){
                Stop-Transcript
            }
        }
        #endregion
The LoggingConfiguration Extension has nothing to do with SPSD it self. It is implementing the (now slightly outdated) logging library of http://spg.codeplex.com/ into SharePoint and registering logging categories and areas.

Can you provide more details of what you are doing?
Aug 27, 2015 at 11:46 PM

Hi matein78,

I’m executing SPSD in the Windows command prompt console.

I’m running SharePoint 2013 on Windows Server 2012 R2.

My PowerShell version is:

$PSVersionTable.PSVersion

Major Minor Build Revision

----- ----- ----- --------

4 0 -1 -1

Please find attached following files:

· Branding.xml – my config file

· console.log – console log messages

· 20150827-191133-Redeploy.log – log file created in log folder during execution

· 20150827-191133-Redeploy-Branding.xml – config file created in log folder during execution

As you can see, the log file (20150827-191133-Redeploy.log ) does not have all log messages from the console log (console.log).

Is there any configuration that I’m missing?

Or can it be a bug due to OS version, PowerShell version, etc…?

Regards,

Marcus Gaspar

Oct 31, 2015 at 10:05 PM
Hi,
We have the same experience (SPSD 5.0.4.6438) running deploy from administrator cmd.
Kind regards
Erik Bo