Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...iWeb upsets upgrade to dnn 05.04.02iWeb upsets upgrade to dnn 05.04.02
Previous
 
Next
New Post
5/23/2010 6:50 AM
 
When I opgraded my dnn, the upgrade failed completely and my only option left was to restre from my backup. The error output indicated that iWeb was using obsolete expressions. I did not save that error output.

I did not use the iWeb installation. I had it installed to do some experiments with Silverlight, but I had not yet written anything for it. So I completely uninstalled iWeb. After this, my upgrade succeeded normally.

After doing all the maintenance after updates, I decided to try and install iWeb again. The installation occurred normally but that was the last page my system displayed. After that, I had error in application /

This time, I saved the output, but I had to restart one more time from my backup.

It cannot be I am the only one?

Server Error in '/' Application.
--------------------------------------------------------------------------------

Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: BC30521: Overload resolution failed because no accessible 'ExecuteSQL' is most specific for these arguments:

Source Error:



Line 117:            mySqlString.Append("Or MethodName not in (" & strMethods & ")")
Line 118:
Line 119:            DotNetNuke.Data.DataProvider.Instance().ExecuteSQL(mySqlString.ToString(), Nothing)
Line 120:        End Sub
Line 121:#End Region
 

Source File: C:\inetpub\wwwroot\dnn\App_Code\IWeb\IWebCore\IWEBMethods.vb    Line: 119


The compiler error messages list a large number of compile error such as:

Warning: BC40000: 'Public Shared Function GetUserByName(portalId As Integer, username As String, isHydrated As Boolean) As Entities.Users.UserInfo' is obsolete: 'Deprecated in DNN 5.1. This function has been replaced by UserController.GetUserByName'.
Source Error:

C:\inetpub\wwwroot\dnn\App_Code\IWeb\IWebMethods\IWebFileManager.vb 

Line 491:
Line 492:
Line 493:            Dim user As UserInfo = UserController.GetUserByName _
Line 494:                (Me.IWebCredentials.PortalID, Me.IWebCredentials.Username, False)
Line 495:
 

Anybody knows what is going on?

____________________________________
The one-eyed in the land of the blind.
 
New Post
5/23/2010 12:41 PM
 
It appears that in DotNetNuke 5.04.02, a new overload of the ExecuteSQL method (found in Library\Providers\DataProviders\SqlDataProvider.vb) was added to temporarily solve a different issue. Unfortunately, this broke iWeb's use the ExecuteSQL method as the dynamic compiler can no longer resolve which overload to call.

I'll add an issue to the Gemini issue tracker if it one has not already been added. EDIT: This has been submitted as Issue DNN-12554

In the meanwhile, and if you really need to use the iWeb module, you could try making the following modification to the file App_Code\IWeb\IWebCore\IWEBMethods.vb at line 119.

Replace the line:
DotNetNuke.Data.DataProvider.Instance().ExecuteSQL(mySqlString.ToString(), Nothing)

with:
DotNetNuke.Data.DataProvider.Instance().ExecuteSQL(mySqlString.ToString())

I have not check to see if this same issue occurs in other areas of the iWeb code but the fix should be the same.



Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
5/23/2010 4:43 PM
 
Normally I would say, we will just fix IWeb, but this is a much bigger issue. A core change to the method signature of ExecuteSQL affects a LOT of code out there.

I will wait until I hear the change is permanent.


Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
New Post
5/27/2010 3:58 AM
 
Michael Washington wrote:
Normally I would say, we will just fix IWeb, but this is a much bigger issue. A core change to the method signature of ExecuteSQL affects a LOT of code out there.

I will wait until I hear the change is permanent.

 Thanks for being on top of this. in the meantime, what would you suggest that IWeb users do as this is blocking upgrade to 5.4.2 and making the site unusable. Is there a way to temporarily disable or uninstall the IWeb module ? Remember that there is no interface available as the process is stuck in the site upgrade... so it has to be some sort of database hack!

 
New Post
5/28/2010 1:17 PM
 
This just got upgraded to major:
http://support.dotnetnuke.com/issue/V...

This is not just about IWeb. Web is just one of the applications affected by this.


Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...iWeb upsets upgrade to dnn 05.04.02iWeb upsets upgrade to dnn 05.04.02


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out