PropertiesGet + BaseItemGet

[deblaerer]

Hi Team!

After the upgrade of ASG RD to 12.0.6420.1 Al the users are getting errors:

An error occured on executing an sql statement
PropertiesGet
Execution Timeout Expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

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

  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.TdsParserStateObject.TryProcessHeader()
  at System.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer()
  at System.Data.SqlClient.TdsParserStateObject.TryReadUInt32(UInt32& value)
  at System.Data.SqlClient.TdsParserStateObject.TryReadPlpLength(Boolean returnPlpNullIfNull, UInt64& lengthLeft)
  at System.Data.SqlClient.TdsParser.TryReadPlpUnicodeChars(Char[]& buff, Int32 offst, Int32 len, TdsParserStateObject stateObj, Int32& totalCharsRead)
  at System.Data.SqlClient.TdsParser.TryReadSqlStringValue(SqlBuffer value, Byte type, Int32 length, Encoding encoding, Boolean isPlp, TdsParserStateObject stateObj)
  at System.Data.SqlClient.TdsParser.TryReadSqlValue(SqlBuffer value, SqlMetaDataPriv md, Int32 length, TdsParserStateObject stateObj, SqlCommandColumnEncryptionSetting columnEncryptionOverride, String columnName)
  at System.Data.SqlClient.SqlDataReader.TryReadColumnData()
  at System.Data.SqlClient.SqlDataReader.TryReadColumnInternal(Int32 i, Boolean readHeaderOnly)
  at System.Data.SqlClient.SqlDataReader.TryReadColumn(Int32 i, Boolean setTimeout, Boolean allowPartiallyReadColumn)
  at System.Data.SqlClient.SqlDataReader.GetSqlString(Int32 i)
  at CloudAdminDataAccess.SqlDataAccessor.GetStringFromReader(SqlDataReader reader, Int32 columnIndex)
  at CloudAdminDataAccess.SqlDataAccessor._PropertiesGet(Guid userId, Guid itemId, Guid rolePropertyId)


An error occured on executing an sql statement
BaseItemGet
ParentItemId

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

  at System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName)
  at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)
  at CloudAdminDataAccess.SqlDataAccessor.GetBaseItemFromReader(SqlDataReader reader)
  at CloudAdminDataAccess.SqlDataAccessor.BaseItemGet(Guid itemId, Guid userId)


Are these issues related to the update of ASG or is this just on SQL?

[DevOma]

From which version do you upgrade?

[deblaerer]

I think this one is patch 4 and we came from patch 3

[DevOma]

Ok, so only a minor update - so there should be not really a difference between the two versions

Can you install Patch3 again - and check if the error still exists?

[deblaerer]

What we also did was a copy of a sql 2008 to a sql 2016
can this be a problem too?

[DevOma]

Sure - can be :-)

Did you make a backup of your database on 2008 server and restore it on 2016? That should normally have no effect on the program - but you should try to bind Patch4 with your old database server and/or use Patch3 with the new SQL server to see what might be the reason

[Jorgen]

Sure - can be :-)

Did you make a backup of your database on 2008 server and restore it on 2016? That should normally have no effect on the program - but you should try to bind Patch4 with your old database server and/or use Patch3 with the new SQL server to see what might be the reason

Hi,

I think it has more to do with the sql Server move from on prem to SQL on Azure VM.

I have just installed the version 5 of ASG 2019.

[DevOma]

Did you use the migration wizard (in SQL Server) to transfer a database to AZURE? We have several customers who are working on AZURE databases - so it should not be a general problem

For testing purposes you can create a new database (choose option for create a new database in AZURE) - and test if this works or if you get some other errors.

[Jorgen]

Hi Olivier,

Yes we used the wizzard, but due to version differences not the migration but copy wizzard, but that should not make any difference.
I made sure all asg stored procedures were there to begin with by 1st creating a new DB on the target server and then filled with our on prem data.
in the mean time some of my colleagues have reverted back to patch 3 and are reporting that the errors are gone.

kind regards,
Jorgen

[DevOma]

The initial error was a timeout problem - what you should check is that you do not have large logs in your database…

Does the error also occurs if you just create a new AZURE SQL database without any data? Or is it only after restoring the data? Don't know how many objects to you have and if the internet connection could be a limitation?!?

And really curious is that Patch3 is working and Patch4 not - there is really no difference in data reading in these 2 versions...