# Printing to Doxcycle from Taxcycle

**URL:** <https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956>\
**Category:** DoxCycle\
**Created:** [July 22, 2024, 12:08pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956 "2024-07-22T12:08:29Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Arliss](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/arliss/32/52_2.png) [@Arliss](https://www.protaxcommunity.com/u/Arliss)\
**Post date:** [July 22, 2024, 12:08pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/1 "2024-07-22T12:08:29Z")

</div>

With the new version of Doxcycle I have not been able to print to it from Taxcycle.

Has anyone else been able to? Just wondering if it something in my own setup or if it the new version’s problem?

---

<div class="post-metadata">

**Author:** ![Arliss](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/arliss/32/52_2.png) [@Arliss](https://www.protaxcommunity.com/u/Arliss)\
**Post date:** [July 22, 2024, 1:53pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/2 "2024-07-22T13:53:58Z")

</div>

Draging and dropping an email with a attached pdf file does not seem to work for me any longer either.

---

<div class="post-metadata">

**Author:** ![aaron.doucet.cpa](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/aaron.doucet.cpa/32/4089_2.png) [@aaron.doucet.cpa](https://www.protaxcommunity.com/u/aaron.doucet.cpa)\
**Post date:** [July 22, 2024, 3:16pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/3 "2024-07-22T15:16:45Z")

</div>

Thank you Arliss, the team will look into this and we will report back!

---

<div class="post-metadata">

**Author:** ![SmallBizGuy](https://avatars.discourse-cdn.com/v4/letter/s/74df32/32.png) [@SmallBizGuy](https://www.protaxcommunity.com/u/SmallBizGuy)\
**Post date:** [July 22, 2024, 3:47pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/4 "2024-07-22T15:47:52Z")

</div>

No problem here…TC version 13.2.53840.0 and DC 13.1.52818.0.

---

<div class="post-metadata">

**Author:** ![Arliss](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/arliss/32/52_2.png) [@Arliss](https://www.protaxcommunity.com/u/Arliss)\
**Post date:** [July 22, 2024, 4:14pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/5 "2024-07-22T16:14:02Z")

</div>

New version

# DoxCycle 13.2.53908.0—.NET 6 Upgrade

---

<div class="post-metadata">

**Author:** ![sarka](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/sarka/32/2667_2.png) [@sarka](https://www.protaxcommunity.com/u/sarka)\
**Post date:** [July 22, 2024, 4:22pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/6 "2024-07-22T16:22:32Z")

</div>

Can you please confirm if you on Windows 11 with the most recent TaxCycle version?

Could you please check if you have detailed logging selected in your DoxCycle options (and TaxCycle in case there is an issue there), retrace the actions you noted here and send logs to us at [info@taxcycle.com](mailto:info@taxcycle.com) ? Please tag me in the email.

---

<div class="post-metadata">

**Author:** ![Arliss](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/arliss/32/52_2.png) [@Arliss](https://www.protaxcommunity.com/u/Arliss)\
**Post date:** [July 22, 2024, 4:47pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/7 "2024-07-22T16:47:58Z")

</div>

Yes to all questions.

Error for the printing to Doxcycle is clipped below.  
There is no error generated for the drag and drp - just nothing happens.

Title: Well, this is embarrassing  
Message: DoxCycle has encountered an unexpected problem and was unable to complete this task.

Please call \*\*1-888-841-3040\*\* for assistance with this error.  
Details: DoxCycle 13.2.53908.0

System.NullReferenceException Object reference not set to an instance of an object.  
Source : Trilogy.Extensibility  
at Trilogy.Extensibility.DocumentLink.MapToProto(DocumentLink documentLink, Dictionary`2 mappedObjects) at Trilogy.Extensibility.ApplicationLink.MapToProto(ApplicationLink applicationLink, Dictionary`2 mappedObjects)  
at Trilogy.Document.Core.File.RecognitionForceInfo.op\_Implicit(RecognitionForceInfo recognitionForceInfo)  
at Trilogy.Document.Service.Client.DocumentServiceClient.RecognizeAsync(CancellationToken cancellationToken)  
at Trilogy.Document.Manager.ViewModel.MainWindowViewModel.CreateClient(String file, ImportEventInfo info, Boolean isTempFile, RecognitionForceInfo forceInfo, WorkgroupOptions workgroupOptions)  
at System.Threading.Tasks.Task.\<\>c.b\_\_128\_0(Object state)  
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)  
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

```
Stack Frames:
{
	 [06000A51] [L_000000AA]	at Trilogy.Extensibility.dll, Trilogy.Extensibility.DocumentLink::MapToProto
	 [06000B02] [L_0000009E]	at Trilogy.Extensibility.dll, Trilogy.Extensibility.ApplicationLink::MapToProto
	 [060001A3] [L_0000003C]	at Trilogy.Document.Core.File.dll, Trilogy.Document.Core.File.RecognitionForceInfo::op_Implicit
	 [060001F8] [L_000000EF]	at Trilogy.Document.Service.Client.dll, Trilogy.Document.Service.Client.DocumentServiceClient+<RecognizeAsync>d__68::MoveNext
	 [06003AFC] [L_00000011]	at System.Private.CoreLib.dll, System.Runtime.ExceptionServices.ExceptionDispatchInfo::Throw
	 [060050CB] [L_00000037]	at System.Private.CoreLib.dll, System.Runtime.CompilerServices.TaskAwaiter::ThrowForNonSuccess
	 [060050CA] [L_00000028]	at System.Private.CoreLib.dll, System.Runtime.CompilerServices.TaskAwaiter::HandleNonSuccessAndDebuggerNotification
	 [06001935] [L_0000034F]	at DoxCycle.dll, Trilogy.Document.Manager.ViewModel.MainWindowViewModel+<CreateClient>d__320::MoveNext
	 [06003AFC] [L_00000011]	at System.Private.CoreLib.dll, System.Runtime.ExceptionServices.ExceptionDispatchInfo::Throw
	 [0600335A] [L_00000000]	at System.Private.CoreLib.dll, System.Threading.Tasks.Task+<>c::<ThrowAsync>b__128_0
	 [06000EB8] [L_00000000]	at WindowsBase.dll, System.Windows.Threading.ExceptionWrapper::InternalRealCall
	 [06000EB7] [L_0000003A]	at WindowsBase.dll, System.Windows.Threading.ExceptionWrapper::TryCatchWhen
}

```

---

<div class="post-metadata">

**Author:** ![sarka](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/sarka/32/2667_2.png) [@sarka](https://www.protaxcommunity.com/u/sarka)\
**Post date:** [July 22, 2024, 5:08pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/8 "2024-07-22T17:08:46Z")

</div>

Thanks @Arliss - our team has been able to replicate the bugs you noted and engineering is investigating. Will update you when I have a timeline for a patch.

---

<div class="post-metadata">

**Author:** ![Arliss](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/arliss/32/52_2.png) [@Arliss](https://www.protaxcommunity.com/u/Arliss)\
**Post date:** [July 22, 2024, 5:20pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/9 "2024-07-22T17:20:05Z")

</div>

You might as well add the default file location for the 2024 files to the update.

---

<div class="post-metadata">

**Author:** ![SmallBizGuy](https://avatars.discourse-cdn.com/v4/letter/s/74df32/32.png) [@SmallBizGuy](https://www.protaxcommunity.com/u/SmallBizGuy)\
**Post date:** [July 22, 2024, 5:51pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/10 "2024-07-22T17:51:57Z")

</div>

> [@Arliss](#):
>
> DoxCycle 13.2.53908.0—.NET 6 Upgrade

Curious. I’m running on WinServer 2016 as a base and I expect that .NET6 hasn’t been pushed out to it. I’m still on 4.8.

---

<div class="post-metadata">

**Author:** ![sarka](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/sarka/32/2667_2.png) [@sarka](https://www.protaxcommunity.com/u/sarka)\
**Post date:** [July 22, 2024, 6:05pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/11 "2024-07-22T18:05:51Z")

</div>

> [@SmallBizGuy](#):
>
> Curious. I’m running on WinServer 2016 as a base and I expect that .NET6 hasn’t been pushed out to it. I’m still on 4.8.

The current release needs a full install. You can grab the update from our website.

> **[DoxCycle 13.2.53908.0—.NET 6 Upgrade](https://www.taxcycle.com/news/doxcycle-132539080/)**
>
> This release upgrades DoxCycle’s technology to .NET 6 to take advantage of the performance, connectivity, and security enhancements offered in this version of .NET. It also converts DoxCycle to a 64-bit only application.

---

<div class="post-metadata">

**Author:** ![SmallBizGuy](https://avatars.discourse-cdn.com/v4/letter/s/74df32/32.png) [@SmallBizGuy](https://www.protaxcommunity.com/u/SmallBizGuy)\
**Post date:** [July 22, 2024, 6:16pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/12 "2024-07-22T18:16:47Z")

</div>

Ah – K – thanks; will do.

---

<div class="post-metadata">

**Author:** ![AlbertaEFileT](https://avatars.discourse-cdn.com/v4/letter/a/3da27b/32.png) [@AlbertaEFileT](https://www.protaxcommunity.com/u/AlbertaEFileT)\
**Post date:** [July 22, 2024, 10:40pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/13 "2024-07-22T22:40:03Z")

</div>

yes please. Especially for T2. Should have that as soon as Jan 01 hits each year at the least.

---

<div class="post-metadata">

**Author:** ![david2](https://avatars.discourse-cdn.com/v4/letter/d/a87d85/32.png) [@david2](https://www.protaxcommunity.com/u/david2)\
**Post date:** [July 23, 2024, 11:22pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/14 "2024-07-23T23:22:09Z")

</div>

Arliss, a little off topic but what are you printing from Taxcycle to Doxcycle? I suspect I am not using software best practices. My doxcycle has basically the client slips and receipts

Thanks

---

<div class="post-metadata">

**Author:** ![Arliss](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/arliss/32/52_2.png) [@Arliss](https://www.protaxcommunity.com/u/Arliss)\
**Post date:** [July 24, 2024, 11:34am UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/15 "2024-07-24T11:34:42Z")

</div>

Just a backup copy of the return as filed.

---

<div class="post-metadata">

**Author:** ![sarka](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/sarka/32/2667_2.png) [@sarka](https://www.protaxcommunity.com/u/sarka)\
**Post date:** [July 31, 2024, 11:55pm UTC](https://www.protaxcommunity.com/t/printing-to-doxcycle-from-taxcycle/8956/16 "2024-07-31T23:55:47Z")

</div>

We have a patch ready and in final testing that addresses the above reported issues. Looks like it will be ready to be released tomorrow.