Intersoft Solutions - Community - WebScheduler - Webscheduler 4 runtime & web.config

Bernard XiangMember

Posted: February 2, 2014 10:45 PM in response to Frank Gary

Hi Frank,

I couldn't replicate your issue in our local. Although, when I look from your screenshot, I think there are missing assembly in your bin folder. Please ensure if ISNet.dll, ISNet.WebUI.dll, and ISNet.WebUI.Resources.dll has been added to your bin folder. If this issue still persist, please let me know. I will gladly help you to resolve it. Look forward to hear any feedback from you so I can help you further.

Regards,
Bernard

http://www.intersoftpt.com/Community/WebScheduler/ISDataSourceControl-Unlicensed/

Frank GaryMember

Posted: February 3, 2014 9:45 AM in response to Bernard Xiang

Hi Bernard & Yudi,

I implemented your above suggestions and those errors are now resolved.

However, I am now receiving an ISDataSource error in my deployment server. My development system works perfectly, but when I deploy to production server I get the following error when I load the webscheduler 4 in my application;

"The ISDataSourceControl used in this application is not licensed. If you have licensed this control, please perform the licensing via the web.config key".

I verified my NEW runtime license and replace in my web.config lines as follows, (XXXX is blanked out license, valid license is in my web.config);

Also, it is exact same problem as this post;

Unfortunately, the above post does not include how to resolve the issue.

Also, the above link you posted is a broken page link.

Please advise and thanks!

Frank Gary

Yudi Member

Posted: February 4, 2014 10:41 PM in response to Frank Gary

I implemented your above suggestions and those errors are now resolved.

Glad to hear that adding framework assemblies to the project's bin folder rectify the initial problem.

Regarding the runtime license key problem, I have forwarded this to the Development team to be investigated further. I'll keep this thread update with any news I heard from the team.

Bernard XiangMember

Posted: February 4, 2014 10:47 PM in response to Frank Gary

Hi Frank,

I don't think you could use WebScheduler 4 runtime license key as ISDataSource runtime license key. You should use ISDataSource Runtime license key to make ISDataSource licensed in your deployment. Altough, when using WebScheduler, ISDataSource should be licensed if ISDataSource in the same page with WebScheduler. I will ask our developer team regarding this matter. Meanwhile, you could use ISDataSource Runtime License Key to license ISDataSource. Hope this helps.

Regards,
Bernard

ISDataSource_DeployError1.jpg

Frank GaryMember

Posted: February 5, 2014 11:14 AM in response to Bernard Xiang

Hi Bernard,

In my old webscheduler v3 the webscheduler and isdatasource runtime license key was the same license code and worked when added to my web.config file. There was no separate licensing for isdatasource other than the isdatasource web.config entry.

I assumed this would still be the case with webscheduler v4. However, if isdatasource for webscheduler v4 requires a separate runtime license, there does not seem to be any way to add it.

You stated "Meanwhile, you could use ISDataSource Runtime License Key to license ISDataSource."

That is exactly what I am trying to do. When I login to my account there is no way to add an isdatasource runtime license as the isdatsource is not available as a licensable product.

I am having the exact same issue as this post > http://www.intersoftpt.com/Community/WebScheduler/ISDataSourceControl-Unlicensed/

Attached is image of error on deployment server.

It has been several days since I purchased webscheduler 4 and I must tell you I am getting frustrated that I cannot release our next software build to clients because of what should be a simple licensing issue.

Please tell me how we can expedite the resolution to this issue.

Thanks - Frank Gary

1 attachment

Bernard XiangMember

Posted: February 5, 2014 9:08 PM in response to Frank Gary

Hi Frank,

We have consider this issue as bug and we have fix it. You can download our hotfix in here:

http://sdrv.ms/1b3OBYM

Please look at our hotfix and please let me know if this issue still persist in your local end. We are really sorry for this inconvenience. Hope this helps.

Regards,
Bernard

Frank GaryMember

Posted: February 6, 2014 11:46 AM in response to Bernard Xiang

Hi Bernard,

Thank you for your quick reply. I have applied the hotfix and in my production server the webscheduler is now loading with no licensing errors.

On my development system webscheduler 4 loads and performs perfectly. However, on my deployment server, webscheduler 4 is loading "corrupted", (see attached image).

From past memory I thought it may have something to do with smart resources so I reregistered smart resources in the webscheduler designer and still same result

I am using IE 11 and Windows x64 and I have also included my redacted web.config file below.

Where do we go from here?

Thanks - Frank

*********************webconfig******************

<?xml version="1.0" encoding="utf-8"?>

<configuration>
<appSettings>
<add key="ChartImageHandler" value="storage=file;timeout=20;dir=c:\TempImageFiles\;" />
<add key="ISNet.WebUI.WebScheduler.v4_0_1000.MaxJsonLength" value="2147483647" />
<add key="ISNet.WebUI.ISRes_Registered" value="true" />
<add key="ISNet.WebUI.WebScheduler.v4_0_1000.RunTimeLicenseKey" value="XXXXX-XXXX-XXXXX" />
<add key="ISNet.WebUI.ISDataSource.v1_0_1500.RunTimeLicenseKey" value="XXXXX-XXXX-XXXXX" />
</appSettings>
<connectionStrings>
<remove name="LocalSqlServer" />
<add name="LocalSqlServer" connectionString="Data Source=XXXX;Initial Catalog=XXXX;Integrated Security=True;" providerName="System.Data.SqlClient" />
<add name="eRezCommerce_Rez" connectionString="Data Source=XXXX;Initial Catalog=XXXX;Persist Security Info=True;User ID=XX;Password=XXXX;" providerName="System.Data.SqlClient" />
<add name="eRezCommerceConnectionString" connectionString="Data Source=XXXX;Initial Catalog=XXXX;Integrated Security=True" providerName="System.Data.SqlClient" />
</connectionStrings>
<system.web>
<globalization culture="en-US" uiCulture="en-US" fileEncoding="utf-8" />

<compilation debug="false" targetFramework="4.0">
<assemblies>
<add assembly="System.Web.Extensions.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
<add assembly="System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="System.Transactions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
<add assembly="Microsoft.ReportViewer.Common, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
<add assembly="Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
<add assembly="System.Web.DataVisualization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
<add assembly="ISNet.WebUI, Version=3.0.5000.1, Culture=neutral, PublicKeyToken=B1F2A8511635667A" />
<add assembly="ISNet.ActiveReports.Exporting, Version=5.0.7200.1, Culture=neutral, PublicKeyToken=B1F2A8511635667A" />
<add assembly="ISNet, Version=3.0.5000.1, Culture=neutral, PublicKeyToken=B1F2A8511635667A" />
<add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
<add assembly="ISNet.WebUI.ISDataSource, Version=1.0.1500.1, Culture=neutral, PublicKeyToken=C4184EF0D326354B" />
</assemblies>
<buildProviders>
<add extension=".rdlc" type="Microsoft.Reporting.RdlBuildProvider, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</buildProviders>
</compilation>

<authentication mode="Forms">
<forms loginUrl="~/Pages/Home.aspx" />
</authentication>
<authorization>
<allow users="?" />
</authorization>
<roleManager enabled="true" />
<siteMap defaultProvider="XmlSiteMapProvider" enabled="true">
<providers>
<add name="XmlSiteMapProvider" type="System.Web.XmlSiteMapProvider" siteMapFile="Web.sitemap" securityTrimmingEnabled="true" />
</providers>
</siteMap>
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.

1 attachment

Bernard XiangMember

Posted: February 6, 2014 9:01 PM in response to Frank Gary

Hi Frank,

You should add our handler inside system.webServer tag. Here's the example:

<system.webServer>
	...
	<handlers>
		<add name="ISCoverFlow.axd_GET" path="ISCoverFlow.axd" verb="GET" type="ISNet.WebUI.Silverlight.WebAqua.WebCoverFlowRequestHandler, ISNet.WebUI.Silverlight.WebAqua" preCondition="integratedMode"/>
		<add name="ISChart.axd_GET, POST" path="ISChart.axd" verb="GET, POST" type="ISNet.WebUI.WebGrid.Chart.ChartRequestHandler, ISNet.WebUI.WebGrid" preCondition="integratedMode"/>
		<add name="ISRes.axd_GET" path="ISRes.axd" verb="GET" type="ISNet.WebUI.WebResourceHandler, ISNet.WebUI, Version=3.0.5000.1, Culture=neutral, PublicKeyToken=b1f2a8511635667a" preCondition="integratedMode"/>
		<add name="WebFileUploaderHttpHandler.axd_GET" path="WebFileUploaderHttpHandler.axd" verb="GET" type="ISNet.WebUI.WebTextEditor.WebFileUploaderHttpHandler, ISNet.WebUI.WebTextEditor" preCondition="integratedMode"/>
		<add name="ISScheduler.axd_GET" path="ISScheduler.axd" verb="GET" type="ISNet.WebUI.WebScheduler.WebSchedulerRequestHandler, ISNet.WebUI.WebScheduler" preCondition="integratedMode"/>
		<add name="IntersoftResource" path="ISRes.axd" verb="GET" preCondition="integratedMode" type="ISNet.WebUI.WebResourceHandler, ISNet.WebUI, Version=3.0.5000.1, Culture=neutral, PublicKeyToken=b1f2a8511635667a"/>
	</handlers>
	<modules>
		<add name="WebFileUploaderHttpModule_GET" preCondition="managedHandler" type="ISNet.WebUI.WebTextEditor.WebFileUploaderHttpModule, ISNet.WebUI.WebTextEditor"/>
	</modules>
</system.webServer>

This would resolve your problem. Hope this helps.

Regards,
Bernard

Frank GaryMember

Posted: February 6, 2014 11:42 PM in response to Bernard Xiang

Hi Bernard,

I added the above to the webconfig and there was no change. The webscheduler still displays "corrupted". Some of the settings were already in my webconfig from the previous webscheduler 3 as shown above in my webconfig. I also tried removing those previous settings and still no success.

It has now been a full week since I purchased webscheduler 4.

Please advise and thanks -

Frank Gary

Frank GaryMember

Posted: February 7, 2014 4:46 PM in response to Bernard Xiang

Hi Bernard,

I think we have a resolution to our problem. One of our developers "manually" registered the webscheduler dll on our deployment server using gacutil. After that the webscheduler began performing perfectly.

We were concerned that we would have to do this on every client production server. We uploaded our new software build to a client server and everthing just worked without any manual steps.

We assumed that since we could not get the webscheduler to work on our development deployment server that we would have the same issues on our client servers. Not sure why we had the issue on our deployment server.

Looks like this issue is resolved. Appreciate all of your and Yudi's attention.

Thanks - Frank

Bernard XiangMember

Posted: February 9, 2014 9:29 PM in response to Frank Gary

HI Frank,

You should add ISNet.WebScheduler.dll, ISNet.WebScheduler.Resources.dll, and ISNet.WebDesktop.Resources.dll, ISNet.dll, ISNet.WebUI.dll and ISNet.WebUI.Resources.dll to your Bin folder. Please also ensure if there are no assembly reference in your web.config that refer to your GAC folder. This issue might be happen because there was configuration in your web.config that refer to your GAC folder and might be the assembly inside your GAC is not the right one that causing this issue occurs in your local end. If you have any further question, please don't hesitate to ask us. Hope this helps.

Regards,
Bernard