Microsoft Dynamics AX (Archived)

Cannot create a record in SysXppAssembly (SysXppAssembly). Error accessing database connection

(0) Share

Report

Posted on by Community Member

Dear Experts,

I'm getting the below error in my production instance while generating the Full CIL

Cannot create a record in SysXppAssembly (SysXppAssembly). Error accessing database connection

Also, in the event logs i got the below error

Object Server 01: The database reported (session 12 (Admin)): [Microsoft][SQL Server Native Client 11.0]Communication link failure. The SQL statement was: "INSERT INTO [AX2012R3_Live_model].[dbo].SYSXPPASSEMBLY (HASHCODE,FILE_,FILENAME,VERSION,ISDEBUG,MODIFIEDDATETIME,MODIFIEDBY,CREATEDDATETIME,CREATEDBY,RECVERSION,RECID) VALUES (?,?,?,?,?,?,?,?,?,?,?)"

Tried the below workarounds,

-Stopped the AOS.

-Deleted the XppIL folder and regenerated new XppIL by starting the AOS services .

However files are creating in XppIL folder but getting the same error after the completion of Full CIL

Also tried application full compilation and DB sync but doesn't solved.

due to this issue inbound ports are not getting started automatically whenever AOS services restarts. Need to generate full CIL always to start the inbound services.

In addition i have checked the network response time and its normal, from application server to DB server

Please advise me, if any one experienced this issue before.

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

Thanks,

Best Regards,

Syed Mohamed Hussain.

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Sort by

André Arnaud de Cal... 303,988 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Syed,

Can you check Windows logs and SQL server logs for possible security permission errors? Are the permissions correct for the model database?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Andre,

Thank you for your response.

i have checked the logs and there is no permission errors, AOS service account has full permissions to all three AX databases.

I'm getting the below error in event logs, but i'm not sure this is linked to the actual issue or not.

AOS runtime

X++ Exception: invalid tracking submission expected context Workflow and expected type Submission actual context Workflow and actual type Fault.

at SysWorkflow-faultWorkflowInstance

SysWorkflow-internalFault

SysWorkflow-fault

WorkflowTrackingTable-saveTracking

SysWorkflowWorkItem-escalate

X++ Exception: invalid tracking submission expected context Workflow and expected type Submission actual context WorkItem and actual type DueDateExceeded.

at WorkflowTrackingTable-saveTracking

SysWorkflowWorkItem-escalate

Kind Regards,

Syed

Was this reply helpful? Yes No
Heinz Schweda 1,367 on at

Like (0)

Report
Copy link

Link copied!

Hello,

you can try to truncate the table SysXPPAssembly, like it is discussed here (community.dynamics.com/.../226368).

Remember to backup your system before!

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Sukrut,

I have checked with my developers team and there is no changes in the system.

However i'm going to try by truncating the table as suggested by "Heinz Schweda"and let all you know the results.

Thanks,

Syed

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Heinz,

Have followed the steps and tried by truncating the table, but it won't resolved.

Regards,

Syed

Was this reply helpful? Yes No
Verified answer

Douglas Noel 3,905 on at

Like (0)

Report
Copy link

Link copied!

Hi,

I do not really have an idea. But remember similar cases where playing around with the network packet size on the sql server resolved this.

Is your sql real or virtualized? Do you have encryption enabled?

Sorry and regards Douglas

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi Douglas,

Thank you for your advice.

After a packet capture, it was clear that SonicWALL Fire wall Gateway Antivirus detecting it to be a Trojan named "MalAgent.I_15221". Few weeks before my security engineer enabled "MalAgent.I_15221". Disabling it resolved the issue. Thank you guys for all your continuous support.

Regards,

Syed

Was this reply helpful? Yes No