Useful Searches

We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Debug info file name not set

I've been making a (for me) very complicated IVR system for our support staff, and it has been going very well. However after around 200ish builds of the IVR, I can no longer build and then execute debug submissions.

In the Errors_Debug.log there are lines like:

System.ApplicationException: Debug info file name not set
at ASP.supportivr_debug_288_supportivr_errorhandler_debuginfo_aspx.Page_Load(Object sender, EventArgs e) in c:\ProgramData\3CX\Data\Http\Interface\ivr\SupportIVR_Debug_288\SupportIVR_ErrorHandler_DebugInfo.aspx:line 30

Click to expand...

One for each ASPX of the IVR. This suddenly happened from one build to the next, I tried researching how to fix but was unsuccessful. Additionally, I looked around to see if I could specify this file, but came up empty-handed.

This seems to be a bug, which happens when the error occurs at the beggining, I'll investigate it...

But the real issue you're experiencing is something else, the problem is that this bug doesn't let you know what you're doing wrong.

The page that you're executing is this:
SupportIVR_ErrorHandler_DebugInfo.aspx

That means that you're experiencing an error, so the handler is triggered, and then another error happens.

You need to fix the first error to continue working. In order to diagnose the problem, please take a look at the log "3CXIvrServer.log", pretty sure there you have the root cause. This article explains a bit more on troubleshooting VAD apps:
http://www.3cx.com/blog/docs/troubleshooting-vad-applications/

Hope the information helps, if you still can't get over it send me a PM so I get into your server and check the issue.

Redacted my ODBC UN and Pass for obvious reasons. From the look of the string it is the setting of all the project variables. However I'm not certain which of these is failing it out -- is it the session.dnis=852MethodGETError-404 dropping this out or something along the line?

The deployment works without issue if I change the Incoming Rule to use the 851 (Release) build of the IVR. If I use the 852 (Debug) build it errors out, as we see. The SupportIVR_DebugInfo.aspx is present in the proper folder, and as far as I can tell permissions are OK. The timestamp suggests that it is created by the VAD at the same time as the other aspx.

Looking at the code it looks to be mostly auto-generated by your process. Nothing custom or special is really in it, save for the flow name. It seems to be parsed in some way, as the below code is handled; unless this is equally present in other sections:

System.ApplicationException: Debug info file name not set
at ASP.supportivr_debug_288_supportivr_errorhandler_debuginfo_aspx.Page_Load(Object sender, EventArgs e) in c:\ProgramData\3CX\Data\Http\Interface\ivr\SupportIVR_Debug_288\SupportIVR_ErrorHandler_DebugInfo.aspx:line 30