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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Error in saving page content in production server ...Error in saving page content in production server ...
Previous
 
Next
New Post
12/20/2010 8:25 PM
 
no, please check properties of the database in SQL Server Management Studio (SSMS)

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/21/2010 3:46 PM
 
Matti;
Please re-check the permissions into your Production SQL server. Your IIS account from the web site and your account on the web folders both need read/write/modify rights against the database

Ken Grierson
DotNetNuke Corporation
Test Lead
 
New Post
12/22/2010 7:24 PM
 
..Hi, DNN experts, have you found anything out of the error information which points you to the cause of the problem?

Matti
 
New Post
12/23/2010 6:55 PM
 
Sebastian Leupold wrote:
no, please check properties of the database in SQL Server Management Studio (SSMS)

 Sebastian,  in my local pc I am using Sql-Server 2008 R2 Express, and I checked the compatibility level with the following T-SQL statement.

 sp_dbcmptlevel "DB-Name"

... which confirmed that the compatibility level is 90.

My hoster has SQL-server 2008 standard edition

Originally, I have migrated  - by myself - my DNN-sql-server database to hoster's  SQL-server  via SMSSE's copy database option
which created me an sql-script-file that I then ran against the hoster's database. In the process f creating the sql-script file I selected the
compatibility to 2008 version (=100). Maybe this way to migrate the DNN database is related to the problem ..?

Also, I noticed that with the following statement in SSMSE

DBCC TRACEON (3604);
GO
DBCC DBINFO('DB_NAME')
GO

.. I can find out that the the version number of the Database is differing between the R2 (=661) and SQL-server 2008 (=651).
When, for the purpose of testing I asked my hoster to attach my local R2 DNN-database to their SQL server 2008, they informed me
that they could not attach the database to SQL-server 2008 because of an version error.

Does this info illumine the issue any better for you?

Matti

 
New Post
12/23/2010 7:36 PM
 
Ken Grierson wrote:
Matti;
Please re-check the permissions into your Production SQL server. Your IIS account from the web site and your account on the web folders both need read/write/modify rights against the database


Ken, I submitted a request to my hoster to check these things out as you suggested, thank you!

Also, I would like to ask if DotNetNuke 5.6.0. reguires
necessarily ASP.NET 4.x version to be set in production server's virtual directory to work properly - i,e. does ASP.NET 2.x version cause the application to fail? Also, is this DNN version supposed to work well in IIS6?

For in my hoster's server there is IIS6 and ASP.NET 2.x version set in the virtual directory of the installation folder.

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Error in saving page content in production server ...Error in saving page content in production server ...


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