We already provided a whitepaper regarding WebGrid and Sharepoint Designer. In this whitepaper, it is detailed how to set WebGrid as a safe control. The error usually caused because insufficient permission for Sharepoint in accessing the required dll.

Hi Glenn, thanks for the response. I have already used that document to configure WebGrid for Sharepoint. I have also chnaged the Trust Level to Full. I am getting the following error in Sharepoint Designer:

Showing a modal dialog box or form when the application is not running in UserInteractive mode is not a valid operation. Specify the ServiceNotification or DefaultDesktopOnly style to display a notification from a service application.

Hi Gary,

Do you run the WebGrid using trial version in your production server? If so, I think that's the cause of the error since the trial attempted to show the trial dialog box.

If you have a license, make sure you have assigned the runtime license key in your web.config.

Hope this helps,
James.

Hi James, I have purchased and licensed WebUI Studio. Now I get the following error in Sharepoint Designer:

When I try to add a server control to the SPD design surface I get the following error: "Error rendering control Webgrid1 - An error occurred while fetching preview"

I am logged in as domain admin. All dlls are in GAC and bin folder and I have made all recommended entries to the Web.Config.

I have made the change in Local Security policy to allow Authenticated Users to Bypass Traverse Checking (as per Mike Walshs comment and MS KB article)

Any suggestion would be greatly appreciated as this is has halted a live development project.

Regards

Gary

Hi Gary,

Just want to make sure that you have properly applied the safe control to your site's config file. For example:

<SafeControl Assembly="ISNet.WebUI.WebGrid, Version=6.0.7200.X, Culture=neutral, PublicKeyToken=3e60b85fb8502d5e" Namespace="ISNet.WebUI.WebGrid" TypeName="*" Safe="True" />

Note that you need to specify the correct exact version of WebGrid in the definition, for instance, the latest build should be 7.0.7200.306.

Also, have you been able to see WebGrid displayed in the designer? Some shots on the error details would be helpful. Thanks!

Regards,
James.

Hi James, I have properly applied the safe control entry in web.config and have specified that latest build number - 7.0.7200.306.

When I refresh the "Server Controls" in the designer I am able to see Webgrid listed and am able to drag it onto the design surface. It adds the control reference in the code vie. The error appears on the design surface: "Error rendering control Webgrid1 - An error occurred while fetching preview"

A few questions:

I am running Sharepoint designer on a dev server but am connected to the live site. All the web.config entries are in the web.config on the live server inclusing all the assemblies. Would that make a difference? I have the WebUI Studio instaled on both the dev and live servers, with all assemblies in both bins and GACs.

I have licensed WebUI Studio on the live server. Where do I add the runtime license? Do I add it to the web.config and if so, where?

I have attached a screenshot of the eror.

Thanks for your assistance.

Regards

Gary

In order to add the runtime license key easily, please use the Deployment Manager, default location in C:\Program Files\Intersoft Solutions\WebUI Studio for ASP.NET\WebUI.NET Framework 3.0\DeploymentManager\ISNet.WebUI.DeploymentManager.exe. If you would like to add it manually in the web.config, you will need to add the key under appSettings tag.

<appSettings>    <add key="ISNet.WebUI.WebGrid.v7_0_7200.RunTimeLicenseKey" value="xxxxx-xxxx-xxxxx" />
</appSettings>

The runtime license key could be viewed in TDN, http://dev2.intersoftpt.com,  under the My Components window.

Hi Gary,

Adding to Glenn's reply, I think you should license the WebUI Studio in your dev machine instead of the live servers. The licensing for live servers should use the runtime license key, which can be inserted into the control's property individually (RuntimeLicenseKey), or into the web.config globally.

Hope this helps,
James.