R2i DotNetNuke® Forum

R2i wants you to have the opportunity to ask questions, post reviews, help others or just rant and rave about DotNetNuke® or any of the R2i Modules and Skins. Our team spends hour upon hour, day after day, working on custom DotNetNuke® modules and services; please feel free to ask us anything.
 
ToolBar crashes
Last Post 01 Jan 1900 05:00 AM by . 3 Replies.
Printer Friendly
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages Informative
Beau GeekUser is Offline
New Member
New Member
Posts:16

--
17 Dec 2006 03:57 AM  
Hi.  I'm using Toolbar 1.7.6 on DNN 4.3.7.  I do a fresh install of Toolbar, drop an instance on a tab.  I view options, and try to add a button.  When I hit "Update," I get:

A critical error has occurred.
Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index

I've tried uninstalling Toolbar, restarting the application, and reinstalling.  Same error.

Help!

   Vikram
Beau GeekUser is Offline
New Member
New Member
Posts:16

--
17 Dec 2006 04:07 AM  
To add to the above: the ToolbarSettings table contains values in the TabID and ModuleID fields; SettingValue is Null.

  Vikram
kevinmschreinerUser is Offline
Advanced Member
Advanced Member
Posts:729

--
21 Dec 2006 02:06 PM  
The general cause of this problem is usually related to a misconfiguration of the Microsoft XML library. To veryify this, the user will experience a basic inability to save any configuration parameters - and may experience other runtime errors due to the inability to save the XML configuration during runtime.

Do you have any ListX or Toolbar modules in place that are working? If not, this is most probably the cause of your troubles.

Toolbar and ListX save their configuration in Serialized XML format, which requires the use of the standard Microsoft XML library in order to perform serialization and deserialization of the configurations. The problem is identified through the Microsoft Support article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;823196

If this is in a hosted environment, you should identify this issue directly to the hoster support, they are generally quick to comply because it is based on a Microsoft KB article (Noted Above).

"The XmlSerializer class generates and compiles code on the fly to perform serialization and deserialization. XmlSerializer uses Code Document Object Model (CodeDom) to perform the compilation. CodeDom compilation uses temporary files on a disk. If the worker process does not have the read permissions on the Temp directory and the write permissions on the Temp directory, then all calls to the Web service fail. Therefore, the worker process requires the read permissions on the Temp directory and the write permissions on the Temp directory. "

The problem is occurrs because the worker process does not have permissions to read to the process Temp directory, and the worker process does not have permissions to write to the process Temp directory.

To resolve this problem, the ASP.NET worker process account (ASPNET or NETWORK SERVICE under Windows 2003) must have read and write access to the Temp directory. To assign the required permission to the worker process on the Temp directory follow these steps:

To assign required permissions to the worker process account on the Temp directory, follow these steps:

1. In Microsoft Windows Explorer, locate the %windir%\temp directory.

2. Right-click %windir%\temp, and then click Properties.

3. In the Properties window, click the Security tab.

4. Click Add, type ServerName\ASPNET, and then click OK.

Note Replace ServerName with the name of the Web server.

Replace ASPNET with NETWORK SERVICE if you deployed your
application on IIS 6.0.

5. Under Allow, click to select the Full Control check box, and then click
OK.

Beau GeekUser is Offline
New Member
New Member
Posts:16

--
21 Dec 2006 05:08 PM  
I have an instance of ListX on the same site, same portal that's working perfectly. In fact, it's on the very page that I'm trying to add an instance of Toolbar.

So, what are the other possibilities?  I don't think it's elated to a misconfiguration of the Microsoft XML library.

  Vikram
You are not authorized to post a reply.

Active Forums 4.1
 

New York, NY • Baltimore, MD • Vienna, VA • St. Louis, MO • Seatle, WA • 410.327.0007 • info@R2Integrated.com

Bookmark & Share Bookmark and Share