Developer forum

Forum » Dynamicweb 9.0 Upgrade issues » DW 9.3.1 UpdateLog.log massive errors

DW 9.3.1 UpdateLog.log massive errors

Hans Kloppenborg
Reply

Hi folks,

We are seeing massive amounts of errors in the updateLog.log after rerunning the updates. Is this normal behaviour? Can it be caused with our use of an Azure database? Or the use of GlobalSettings.config and Database.config?

Some examples:

Package 862 from updates.xml.aspx<br /><b>9/15/2017 1:14:01 PM</b>&nbsp;&nbsp;&nbsp;Standard SQL applied.
                    UPDATE [Module] SET [ModuleIsBeta] = 1 WHERE [ModuleSystemName] = 'ItemCreator' AND [ModuleIsBeta] = 0
                <br /><b>9/15/2017 1:14:01 PM</b>&nbsp;&nbsp;&nbsp;Package 863 from updates.xml.aspx<br /><b>9/15/2017 1:14:01 PM</b>&nbsp;&nbsp;&nbsp;Package 864 from updates.xml.aspx<br /><b>9/15/2017 1:14:01 PM</b>&nbsp;&nbsp;&nbsp;file <font color="red">D:\home\site\wwwroot\Files\Templates\eCom7\CartV2\Step\InformationSaveCart.html</font> already exists.<br /><b>9/15/2017 1:14:01 PM</b>&nbsp;&nbsp;&nbsp;Package 865 from updates.xml.aspx<br /><b>9/15/2017 1:14:01 PM</b>&nbsp;&nbsp;&nbsp;Standard SQL applied.
                    IF NOT EXISTS(SELECT * FROM sys.columns WHERE ( name = 'Statv2ObjectPageID' ) AND ( object_id = ( SELECT object_id FROM sys.tables WHERE ( name = 'Statv2Object' ) ) ) )
                        ALTER TABLE [Statv2Object] ADD [Statv2ObjectPageID] INT NULL
                <br /><b>9/15/2017 1:14:01 PM</b>&nbsp;&nbsp;&nbsp;<font color="red"> - error: 'NOW' is not a recognized built-in function name. - System.Data.SqlClient.SqlException (0x80131904): 'NOW' is not a recognized built-in function name.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteScalar()
   at Dynamicweb.Frontend.Update.ProcessDatabase(XmlNode& xmlNode)

 

9/15/2017 1:14:21 PM</b>&nbsp;&nbsp;&nbsp;Package 409 from ecom.xml.aspx<br /><b>9/15/2017 1:14:21 PM</b>&nbsp;&nbsp;&nbsp;Standard SQL applied.
                    IF (NOT EXISTS(SELECT * FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'EcomProductFieldTranslation'))
                    BEGIN
                        CREATE TABLE dbo.[EcomProductFieldTranslation](
                         [ProductFieldTranslationID] [int] IDENTITY(1,1) NOT NULL,
                         [ProductFieldTranslationFieldID] [nvarchar](255) NOT NULL,
                         [ProductFieldTranslationLanguageID] [nvarchar](50) NOT NULL,
                         [ProductFieldTranslationName] [nvarchar](255) NULL,
                        CONSTRAINT [PK_EcomProductFieldTranslation] PRIMARY KEY CLUSTERED ([ProductFieldTranslationID] ASC))
                    END
                <br /><b>9/15/2017 1:14:21 PM</b>&nbsp;&nbsp;&nbsp;Package 410 from ecom.xml.aspx<br /><b>9/15/2017 1:14:21 PM</b>&nbsp;&nbsp;&nbsp;<font color="red"> - error: Column names in each table must be unique. Column name 'LoyaltyRewardArchived' in table 'EcomLoyaltyReward' is specified more than once. - System.Data.SqlClient.SqlException (0x80131904): Column names in each table must be unique. Column name 'LoyaltyRewardArchived' in table 'EcomLoyaltyReward' is specified more than once.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Dynamicweb.Frontend.Update.ProcessDatabase(XmlNode& xmlNode)

As a solution we have copied all the sql queries from the log and executed them, and that seemed to change some things, like the homepage widgets updated to the new versions.

Greets Hans


Replies

 
Nicolai Pedersen
Reply

Yes. It will give you an error if you rurun a trisillion packages that have already been applied.

BR Nicolai

 
Hans Kloppenborg
Reply

Okey Nicolai,

But the first error comes down on a syntax error as far as I can see

'NOW' is not a recognized built-in function name.

​And running the sql statements from the log in sql manager on the same server somehow fixed my dashboard so it showed the new widgets. So something changed after running the queries in management studio.

Trouble with the log as it works now is that you cannot see if there are real errors if the default effect of re-running updates is to generate errors.

Greets Hans

 

You must be logged in to post in the forum