Решать подобные проблемы "в уме", без снимков sysprocesses, результатов sp_lock, списка блокируемых объектов достаточно сложно. Не предоставлять достаточное количество информации - Ваше право
Если ситуация воспроизводится при единственном пользователе в системе (он лочит сам себя) - да, проблема, надо разбираться. Если нет - тоже проблема блокировок, но уже совсем другая, и AOS тут не при чем.
Что касается нескольких spid - немного конструктива (выдержка из Databases Advanced):
Цитата:
For each 2-tier session Axapta starts at least three (3) connections against
the database:
• Session used primarily for sequence-number generation and other
system management tasks. This connection is referred to as the
system connection. Reason for this session is to avoid update of
“SystemSequences” to be part of a current active transaction,
which would make it sequence-number generation a bottleneck in
the system.
• Application connection, which generally is used for running the
business logic of the application.
• Read-only connection, which is similar to the application
connection, but no data manipulation operations are executed on
this type of connections. Clients browsing data in Forms will
typically use a read-only connection.
• Optional user connections. The X++ language provides a number
of ways to have “user defined” connections, which is accomplished
by instantiating classes of type Connection, UserConnection, or
OdbcConnection (refer to the “Axapta Developer’s Guide” for
details).