Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Dmitrij Jazel 86 posts 179 karma points
    Nov 12, 2012 @ 12:56
    Dmitrij Jazel
    0

    Runtime error while trying to publish

    Hello Guys,

    I have really strange error here. Not sure it can happen, here is what I have:

    For some reason, I cannot "save and publish" the content I just edited. I can "save" it. But as soon as I hit save and publish - I get this "runtime error":

    Log File entry does not register this error (no precise timestamp).

    The error happens only when I am trying to "publish" the content, cause if I rightclick on node, and choose publish, after clicking OK I get the same error...

    What I did try:

    I tryed to restart the application by switching between .net versions. but that gave no results...

    Any suggestion how to fix/avoid this problem, or atleast what causes it...

    Kind regards,

    Dmitrij

  • Stephen 767 posts 2273 karma points c-trib
    Nov 12, 2012 @ 13:55
    Stephen
    0

    Can you edit your web.config as suggested in the error message (setting customErrors mode="off") and report the (more complete) error message that you get?

  • Dmitrij Jazel 86 posts 179 karma points
    Nov 12, 2012 @ 14:08
    Dmitrij Jazel
    0

    Hej Stephen,

    Sure thing, here is what I have:

    Any idea why this can be caused, and what could I do to solve it? :-)

    Regards,

    Dmitrij

  • Stephen 767 posts 2273 karma points c-trib
    Nov 12, 2012 @ 14:12
    Stephen
    0

    Er... your database refuses to allocate space so we can create a new record corresponding to the published content. I'm no expert in SQL SERVER so I cannot interpret the error message in details. Can you check the health of the database?

  • Dmitrij Jazel 86 posts 179 karma points
    Nov 12, 2012 @ 14:24
    Dmitrij Jazel
    0

    Thanks for quick response Stephen :-)

    Yes I found the problem... I called our hosting provider, and yet they checked MSSQL server, and found that the server "locked" itself somehow. Not sure how and why, but it is OK now, and it seams to be fine.

    Thanks alot for quick response!!! and have a great day! :-)

    Kind regards,

    Dmitrij

Please Sign in or register to post replies

Write your reply to:

Draft