Internal Error 500

For technical questions regarding estimation of single equations, systems, VARs, Factor analysis and State Space Models in EViews. General econometric questions and advice should go in the Econometric Discussions forum.

Moderators: EViews Gareth, EViews Moderator

tslay
Posts: 3
Joined: Wed Sep 30, 2009 12:55 am

Internal Error 500

Postby tslay » Wed Sep 30, 2009 1:10 am

Hi,

I'm trying to run a Blanchard-Quah-type VAR decomposition using Proc->Estimate Structural Factorization. But I need both Short-Run and Long-Run restrictions on the VAR estimation. However, when I do so, it gives me an error "Internal Error 500". I'm just wondering if this error number corresponds to an error in my specification of the model and/or the restrictions, or if eViews 6 (Enterprise Edition Jun 3 2008 build) is not able to handle having both Short-Run and Long-Run restrictions at the same time.

Thanks in advance!

EViews Gareth
Fe ddaethom, fe welon, fe amcangyfrifon
Posts: 13600
Joined: Tue Sep 16, 2008 5:38 pm

Re: Internal Error 500

Postby EViews Gareth » Wed Sep 30, 2009 8:06 am

Internal Error 500 is something that should never happen, and usually indicates a bug in EViews. Would it be possible for you to send us your workfile, and instructions on exactly what you did to get that error to occur?

tslay
Posts: 3
Joined: Wed Sep 30, 2009 12:55 am

Re: Internal Error 500

Postby tslay » Wed Sep 30, 2009 5:58 pm

I've attached my workfile (impst_realgdpc). What I did was select DLIND and DLI_P and created a VAR (1 lag only and constant) with them. Then I selected Proc->Estimate Structural Factorization and typed in the following restrictions:

@e1 = C(1)*@u1 + C(2)*@u2
@e2 = -C(1)*@u1+C(1)*@u2
@lr1(@u2)=0
Attachments
impst_realgdpc.wf1
Workfile
(64.81 KiB) Downloaded 268 times

EViews Gareth
Fe ddaethom, fe welon, fe amcangyfrifon
Posts: 13600
Joined: Tue Sep 16, 2008 5:38 pm

Re: Internal Error 500

Postby EViews Gareth » Wed Sep 30, 2009 6:28 pm

Ok, that's not really a bug other than EViews isn't giving a proper error message. The problem is because you've mixed a long-run specification with a short-run one, which you cannot do. I'll see if we can get the error message changed to something better than the current one.


Return to “Estimation”

Who is online

Users browsing this forum: No registered users and 2 guests