Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • apload-gmbh 39 posts 109 karma points
    Dec 13, 2023 @ 07:25
    apload-gmbh
    0

    MSSQL 2017 error invalid column name 'alias' with Umbraco 9.5.0

    Good morning everyone

    If we go to the info tab in the umbraco backend, we get an error message and also if we like to unpublish a single site or a list item. We could find several column names 'alias' or 'Alias' in the SQL database, but in the system tables and (so far we can see) not in the individual content tables.

    Has anyone else occurred to this issue and/or has a solution idea?

    Kind regards

    Jan

    An error occurred

    Invalid column name 'alias'. Ausnahmedetails System.Data.SqlClient.SqlException, System.Data.SqlClient, Version=4.6.1.3, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a: Invalid column name 'alias'. Stacktrace at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

    at System.Data.SqlClient.SqlInternalConnection.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)

    at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)

    at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)

    at StackExchange.Profiling.Data.ProfiledDbCommand.ExecuteDbDataReader(CommandBehavior behavior) in C:\projects\dotnet\src\MiniProfiler.Shared\Data\ProfiledDbCommand.cs:line 236

    at Umbraco.Cms.Infrastructure.Persistence.FaultHandling.RetryPolicy.ExecuteAction[TResult](Func`1 func)

    at NPoco.Database.ExecuteReaderHelper(DbCommand cmd)

    at NPoco.Database.ExecuteDataReader(DbCommand cmd)

    at NPoco.Database.QueryImp[T](T instance, Expression1 listExpression, Func2 idFunc, Sql Sql)+MoveNext()

    at System.Collections.Generic.List1..ctor(IEnumerable1 collection)

    at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)

    at NPoco.Database.

    at NPoco.Database.PageImp[T,TRet](Int64 page, Int64 itemsPerPage, String sql, Object[] args, Func`3 executeQueryFunc)

    at NPoco.Database.Page[T](Int64 page, Int64 itemsPerPage, String sql, Object[] args)

    at NPoco.Database.Page[T](Int64 page, Int64 itemsPerPage, Sql sql)

    at Umbraco.Cms.Infrastructure.Persistence.Repositories.Implement.TrackedReferencesRepository.GetPagedRelationsForItem(Int32 id, Int64 pageIndex, Int32 pageSize, Boolean filterMustBeIsDependency, Int64& totalRecords)

    at Umbraco.Cms.Core.Services.Implement.TrackedReferencesService.GetPagedRelationsForItem(Int32 id, Int64 pageIndex, Int32 pageSize, Boolean filterMustBeIsDependency)

    at Umbraco.Cms.Web.BackOffice.Controllers.TrackedReferencesController.GetPagedReferences(Int32 id, Int32 pageNumber, Int32 pageSize, Boolean filterMustBeIsDependency)

    at lambda_method2002(Closure , Object , Object[] )

    at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)

    at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()

    at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)

    at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()

    --- End of stack trace from previous location ---

    at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)

    at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)

    at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()

    --- End of stack trace from previous location ---

    at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.

  • apload-gmbh 39 posts 109 karma points
    Dec 15, 2023 @ 12:45
    apload-gmbh
    0

    Another issue is that the error shows up every time you try to delete an item: media item, sub-site, ...

  • apload-gmbh 39 posts 109 karma points
    Dec 19, 2023 @ 09:13
    apload-gmbh
    0

    We found out that the problem occurs due to an MS SQL Update, which cannot be taken back according our hoster.

    Are we really the only ones, who suffer this problem?

  • apload-gmbh 39 posts 109 karma points
    Dec 27, 2023 @ 14:23
    apload-gmbh
    0

    The new SQL version is 2022. We have still this problem.

  • David Armitage 510 posts 2081 karma points
    Feb 19, 2024 @ 04:38
    David Armitage
    0

    Hi,

    Did you get a solution for this? I am getting the exact same issue with an Umbraco 9 site.

    I tested all my other sites on this server Umbraco 11, 12, 13 and I am not getting this issue.

    Did you try upgrading the Umbraco version to fix this?

    I have a few more Umbraco 9 sites on the same server using SQL 2022 and they are all facing the same issue.

    I am going to try and upgrade one of them to 10 and then 11 to see how that goes.

  • David Armitage 510 posts 2081 karma points
    Feb 19, 2024 @ 05:47
    David Armitage
    0

    Hi,

    Just to confirm here. Upgrading to Umbraco 10 did the trick.

    I updated to the latest minor version of 10 (10.8.4) and this issue no longer existed.

    I hope this helps someone.

  • apload-gmbh 39 posts 109 karma points
    Feb 20, 2024 @ 08:11
    apload-gmbh
    0

    Our quick fix was to migrate to a SQL server with 2019. But good to know that Umbraco 10 seems to work properly.

Please Sign in or register to post replies

Write your reply to:

Draft