Question

WebLinkControls.WLConnectionManager.GetConnectionByVdirAndRepoName(String vdirName

WebLink

Updated May 2, 2022

asked on July 18, 2018

Anyone have any ideas? Happening randomly couple times a day. I cannot reproduce the error by doing anything in weblink. I did find similar strings located in WebFiles/LFDS

4 Errors listed below:

Error 1

An unhandled exception occurred and the process was terminated.

Application ID: /LM/W3SVC/1/ROOT/WebLink

Process ID: 880

Exception: System.Exception

Message: vdirName cannot be empty

StackTrace: at WebLinkControls.WLConnectionManager.GetConnectionByVdirAndRepoName(String vdirName, String repoName, Boolean forceNew)
at WebLink.Global._Closure$__19-0._Lambda$__0(Object o)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()

Error 2

Application: w3wp.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Exception
at WebLinkControls.WLConnectionManager.GetConnectionByVdirAndRepoName(System.String, System.String, Boolean)
at WebLink.Global+_Closure$__19-0._Lambda$__0(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()

Error 3

Faulting application name: w3wp.exe, version: 10.0.14393.0, time stamp: 0x57899b8a
Faulting module name: KERNELBASE.dll, version: 10.0.14393.2312, time stamp: 0x5b1a1651
Exception code: 0xe0434352
Fault offset: 0x0000000000033c58
Faulting process id: 0x1844
Faulting application start time: 0x01d41c5b6e7fb217
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 6952711a-e052-48ef-8eed-c59ca3dc974a
Faulting package full name:
Faulting package-relative application ID:

Error 4

An unhandled Microsoft .NET Framework exception occurred in w3wp.exe [6212]. Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on.

Check the documentation index for 'Just-in-time debugging, errors' for more information.

0 0

Answer

APPROVED ANSWER

replied on May 2, 2022

This was fixed (Bug 336279) and released Oct/Nov 2021 with WebLink 11.0

0 0

replied on May 2, 2022

Tricia, is there a way to fix it in WebLink 10.1.0.151?

0 0

replied on May 2, 2022

Blake, we do not currently have plans for a WebLink 10.1 update. You can contact support to discuss options for this if you are unable to upgrade to WebLink 11.0.

0 0

Replies

replied on November 18, 2021

Bug #336279 and will be in WebLink 11.0

1 0

replied on September 18, 2018

Hello,

Did you ever find out what was causing those errors?

0 0

View 6 previous replies

replied on September 18, 2018

I did not, they are still happening. I'm hoping to install the new version of weblink and rebuild soon. I've done a lot of searching on answers and other forums with no luck as to what vdir it's looking for.

0 0

replied on September 18, 2018

I am seeing this issue in WebLink 10. I am curious if Laserfiche has seen this before.

0 0

replied on September 18, 2018

Yes I'm on Weblink 10.0 and 10.3 is out now so I was going to do a fresh rebuild.

0 0

replied on September 19, 2018

Please let me know if that resolves the issue for you.

0 0

replied on November 30, 2020

I am checking to see if there has been an update on this issue, and whether or not Laserfiche ever advised what may have been causing the unhandled exception error messages [in version 10.1].

0 0

replied on December 24, 2020

I am checking on this as well, as we have a customer who is experiencing the same issue.

Thanks,
Jeff Curtis

0 0

replied on December 24, 2020

I still get them, not as frequent but I still get them.

0 0

replied on December 28, 2020

I had this issue with a customer and upgraded their version of WebLink to 10.2. That resolved the issue.

0 0

replied on December 29, 2020

Thanks Wesley and Drew

We updated this customer to WL 10.2 and the issue still occurs.

Jeff Curtis

0 0

replied on November 26, 2019

Does anyone have an update on this issue? We are also on WebLink Version: 10.1.0.151 and getting the same errors.

Thanks!

-Marina

0 0

replied on November 27, 2019

I still get them on 10.4.0.309, no fix here. They don't seem to cause any problems that I can see other than I see the error.

0 0

replied on February 19, 2021

on the latest version of weblink and still getting this issue. Agree, no issues that I can see but would still be nice to not have weblink throw this error ;)

0 0

replied on November 17, 2021

I believe this should fix this error:

1. Open up the Web.config file for the WebLink Designer located usually in \Program Files\Laserfiche\WebLink\WebLinkDesigner\ folder.

2. Find the element (at the bottom of the file) <appSettings>.

3. Add the following code after the <appSettings> element:

<add key="DefaultVirtualDirectoryName" value="WebLink"></add>

4. Save the file and close it.

5. Perform an IIS reset just to make sure the changes are applied all across.

0 0

replied on May 2, 2022

Did you ever find a fix for this issue? I tried adding the key as Wes instructs, but it did not fix the issue.

0 0

You are not allowed to follow up in this post.

Question

Question

WebLinkControls.WLConnectionManager.GetConnectionByVdirAndRepoName(String vdirName

Answer

Replies

Sign in to reply to this post.