Just to check, you followed KB article https://support.na.sage.com/selfservice/viewdocument.do?externalId=107036 to regenerate the adxodbc file?

Hi Mike, thank you for your response, yes I recreated the adxodbc as per those instructions with no success, everything else works fine but printing and fixed assets not. I checked the SQL connection logs since my initial post and it turns out the application server is actually using the database name from this file instead of the user name when attempting to connect and of course there is no user with this name, so instead of using line 3 of the adxodbc file as the username it's using line 2 which is the database, and yet in SEED it works and the adxodbc file in SEED is identical.

Sounds a bit weird!   I would suggest to take a look at my blog https://www.sagecity.com/gb/sage-x3-uk/b/sage-x3-uk-support-insights/posts/illustrated-guide-to-tracing-debugging-sage-x3-report-server and first do step 6 "Testing the Print Server database connectivity" and if nothing pops up from that, then try generating printer debug file as per the section "Running Print Server in debug mode"

I will run through that and post here if it turns up something, thanks again.

Hi Mike, I went through your blog as suggested and learned that it was passing the ~1 from the first line of adxodbc as the database name, and passing the database name from line 2 of adxodbc as the username, but while browsing through the folder structure I thought maybe I should check the TRT folder for scripts that shouldn't be there, it turns out there was a copy of ORAPASSE.adx in the child folder, by deleting this file my problem is resolved, hopefully this helps someone

OK, thanks for sharing the solution!