.NET Error

[mor_eli]

I've tried to install EWA as instructed. I stop the Recording Service, delete the all the files except the BIN folder, and in the Bin Folder I delete AjaxPro2.dll and the ICSharpCode.SharpZipLib.dll As instructed.
I've then extracted the content of the Zip file to the Web folder.

When I re-enable the Recording Service, GBPVR reinstalls the orginal files (The ones i've deleted), and I can't get the EWA to work.

When I try to get to the address of the Web Server, I get the following error thru explorer:

[ATTACHMENT NOT FOUND]


I've tried this three times, with the same result every time.
Any advice will be appreciated.

[UncleJohnsBand]

First....are you running version 97.x or 98.x of GBPVR?

The problem is that you have a gbweb.dll (which is part of EWA in version 97.x) file in your web/bin directory. This file is no longer used in GBPVR and the EWA in versions 98.x and higher.

Per the wiki instructions this needs to be deleted since it is not part of the EWA that comes with 98.x.

You indicated that when you remove the files they get reinstalled....which does occur when you remove things from the web/bin directory.....but....gbweb.dll should not cause this if you are running 98.x of GBPVR.

TRy just removing the gbweb.dll file from the web/bin and let me know what happens.

[mor_eli]

I followed your seggetion, and deleted gbweb.dll, and I've got a new error message, this time complaining about global.aspa, whice i've deleted also.

After deleting these two files, it started working. Tnx!!

I'm using version 9.8.13, the latest one posted yesterday.

[UncleJohnsBand]

That's good news.

[Beefaloo]

Anyone else got this?
Installed latest EWA by the book, and got a .NET error when posting on the Config-page. After enabling detailed errormessages, I found out that it was complaining about a string.format:

guideParams.strmVideoScaleSize = String.Format("{0:00.00}",Convert.ToDecimal(streamVideoScaleSize.Text));

in Admin.aspx.cs

Decided to make it just
guideParams.strmVideoScaleSize = streamVideoScaleSize.Text;

and then it works fine.

I run on a Swedish XP with langpack in .NET
//

[UncleJohnsBand]

Anyone else got this?
Installed latest EWA by the book, and got a .NET error when posting on the Config-page. After enabling detailed errormessages, I found out that it was complaining about a string.format:

guideParams.strmVideoScaleSize = String.Format("{0:00.00}",Convert.ToDecimal(streamVideoScaleSize.Text));

in Admin.aspx.cs

Decided to make it just
guideParams.strmVideoScaleSize = streamVideoScaleSize.Text;

and then it works fine.

I run on a Swedish XP with langpack in .NET
//

One other person reported this type of problem (also from Sweden). The video scale size is to be a decimal number such as 1.0 for 100% of the recorded size or 0.50 to be 1/2 the recorded size.

What number do you have in this field. The default should be 1.0.

Hopefully the below helps....set it to just a 1.....this may be a regional issue.....

Below are the guts of the conversation I had on this issue in another thread:

I get error when trying to save/activate settings in the latest version of EWA.

I installed it OK and everything works until I try to submit the changes I made on the Admin.aspx page I get the following error message:

Code:

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.FormatException: Input string was not in a correct format.

Code:

Line 278:            guideParams.strmVideoSizeOpt    = streamVideoSizeOpt.Text;
Line 279:            guideParams.strmVideoSize       = streamVideoSize.Text;
Line 280:            guideParams.strmVideoScaleSize  = String.Format("{0:00.00}",Convert.ToDecimal(streamVideoScaleSize.Text));
Line 281:            streamVideoScaleSize.Text = guideParams.strmVideoScaleSize;
Line 282:

With the following Stack trace:

Code:

[FormatException: Input string was not in a correct format.]
   System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +2753251
   System.Number.ParseDecimal(String value, NumberStyles options, NumberFormatInfo numfmt) +119
   System.Decimal.Parse(String s, IFormatProvider provider) +26
   System.Convert.ToDecimal(String value) +85
   gbweb.Admin.hlSubmit_Click(Object sender, EventArgs e) in f:\Program Files\devnz\gbpvr\web\Admin.aspx.cs:280
   System.Web.UI.WebControls.LinkButton.OnClick(EventArgs e) +75
   System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument) +97
   System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7
   System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11
   System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +172
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4921

Code:

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210

It is set to Preset. Can this be related to regional settings. In Sweden we do not use decimal point, we use decimal comma. Could this be causing a problem?

It does not matter if I change nothing. It still produces the same error and teh only setting it changes is the colour scheme. Anything else does not change.

It is a bit annoying, I wonder why I am the only one with this problem. That is why I wonder if regional settings could be the cause?

Perhaps....I am not real familiar with how regional settings work....

Try selecting scale and then enter just the number one in the box and let me know what happens.

Actually it worked, but as standard it sys 1:00. I changed it to just 1 and after that it worked...

Strange, but it seems to be working right now so thanks :-)

/forzaKGB

So when you switched over it was set to 1:00 and then you entered just a 1 and now it is ok....correct?

Interesting......

That is correct. But since I got it working I can set it to anything and it works. Could it be that some setting was not the correct as per default and when it got set OK things started to work?

Right now everything is working so I am happy :-)