Products

Solutions

Resources

Partners

Community

About

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...Administration ...Administration ...Scheduler exception after Upgrade to 7.3.0Scheduler exception after Upgrade to 7.3.0
Previous
 
Next
New Post
7/2/2014 6:02 PM
 
Thanks. I had the same problem, for some reason. The "enabled" field seems to be ignored.
JC
 
New Post
7/2/2014 10:01 PM
 
Here's MINE
ServerID ServerName CreatedDate LastActivityDate URL IISAppName Enabled ServerGroup UniqueId PingFailureCount
2 LAPTOP12 52:36.0 57:49.9 dnndev.me/dnn /LM/W3SVC/2/ROOT/dnn 1 0
15 LAPTOP12
17:43.1 17:43.1 localhost/dnn /LM/W3SVC/1/ROOT/DNN 1 0

 
New Post
7/3/2014 3:17 AM
 
The problem is the unique key on the table includes ServerName and IISAppName columns, while DNN expects during retrieval ServerName to be unique.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/3/2014 3:19 PM
 
SCTAN J wrote:

Here's MINE
ServerID ServerName CreatedDate LastActivityDate URL IISAppName Enabled ServerGroup UniqueId PingFailureCount
2 LAPTOP12 52:36.0 57:49.9 dnndev.me/dnn /LM/W3SVC/2/ROOT/dnn 1 0
15 LAPTOP12

17:43.1 17:43.1 localhost/dnn /LM/W3SVC/1/ROOT/DNN 1 0


 thanks, I've logged this as an issue to https://dnntracker.atlassian.net/brow... and assigned it to 7.3.2 - for now to fix your error you will need to remove the line for the server you are not on (as part of the fix we will make it resilient for duplicate servernames and ensure the enabled property is checked also)


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/20/2014 9:47 AM
 
Thanks Cathal and everyone for sharing. I encountered this same issue and found that the duplicate WebServers entry was created during the upgrade.

The new entry was enabled, the original that got duplicated was not.
The new entry had a URL assigned, the original entry has a NULL for URL.

I liked Chris Hammond's idea of just renaming the row and cycling the app pool. I didn't do it from within IIS, just Recyling the App Domain from the toolbar worked fine.

What a relief, cheers!

Dylan Lopez - Solution Developer, INNO Software Inc. E: http://www.innosoftware.net/contact.aspx P: 1-888-INNO-001 / 604-628-4467 W: http://www.innosoftware.net
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Scheduler exception after Upgrade to 7.3.0Scheduler exception after Upgrade to 7.3.0


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