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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Module Upload Error: Cannot access a closed file...Module Upload Error: Cannot access a closed file...
Previous
 
Next
New Post
10/21/2006 12:13 PM
 
it looks like you misconfigured your installation. you should not use another databaseowner in your web config, if not explicitely requested and set up by our host.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/21/2006 3:18 PM
 
This is the result of an error in the sqldataprovider script.  I see this frequently in modules being reviewed.  It occurs because the script uses a {databaseOwner}sysobjects reference (which causes an error when {databaseOwner} is anything other than "dbo").  The {databaseOwner} and {objectQualifier} tags should only be used with objects created by DNN or another module, and should never be used with any system tables or views.

Joe Brinkman
DNN Corp.
 
New Post
10/21/2006 4:19 PM
 
OK - but I'm not sure what to do about it.  It is happening with just about every module that I try to load.  The error posted in this thread was from trying to upload the core links module.  I assume that I need to change a script somewhere, but I don't know if the sqldataprovider script that you mentioned is module specific or if there is there one that all modules use.  Would I have to search through all the stored procedures and make changes or is there a central place where this is controlled?  I Just don't know where to go next.

I don't think there is an error in my installation as suggested by Sebastian, since the  HOST has it set up to automatically add the object qualifier when a table is created (apparantly a lot of hosts do that), and that parameter is set up properly in web.config  Apparantly the system objects always have 'dbo' as the owner, so i don't have any choice in the  matter.

It seems like I need to find all the places where the script(s) specifies {databaseowner}.sysobjects and change it to dbo.sysobjects.

I found this in the bug reporting database:
"There is a bug when installing with the config setting of databaseowner different than "dbo".

If you do so, some core modules will not be installed because the SQL-Scripts requests the {databaseOwner}sysobjects table instead of dbo.sysobjects. This will result in failing such modules like HTMLText and others.

Please change the scripts in the ...SQLDataProvider files to dbo.sysobjects or better to INFORMATION_SCHEMA.TABLES (Microsoft recommendation)"

I don't totally understand what thie above quote refers to, but it looks like there may be a more generic method of referring to the sysobjects table.

Any suggestions as to where these changes should be made? - an example would be really good.

 
New Post
10/21/2006 5:16 PM
 
I just went through all the files in /providers/dataproviders/sqldataprovider and did not find any file where the word "sysobjects" was proceeded by anything except "dbo".  Most references were in the form of "SELECT * FROM SYSOBJECTS".

I also looked through a bunch of stored procedures and did not ANY reference to "sysobjects".

totally baffled!



 
New Post
11/9/2006 12:30 PM
 
Any solution to this problem.... I am having the same issue?
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Module Upload Error: Cannot access a closed file...Module Upload Error: Cannot access a closed file...


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