|
Home > Archive > Microsoft Content Management Server > January 2006 > sdo import
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Charly 2006-01-24, 8:54 pm |
| I am getting the internal serrver error
"The remote server returned an error: (500) Internal Server Error."
The only thing I have in the sdo is one template... (I added a
placeholder to the template in Dev, and I am trying to migrate the
modified template to the QA, amnd then to Produciton).
My question is, if the destination server already has this template,
(the old version) with existing postings connected to it, would that
cause this issue?
| |
| Stefan [MSFT] 2006-01-25, 8:34 am |
| Hi Charly,
have a look at the following article on how to troubleshoot 500 server
errors during import:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm#DD159085-1AFB-4244-AE6D-D0A1C0E9E274
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------
"Charly" <cbretana@areteind.com> wrote in message
news:1138148644.028675.133590@f14g2000cwb.googlegroups.com...
>I am getting the internal serrver error
>
> "The remote server returned an error: (500) Internal Server Error."
>
> The only thing I have in the sdo is one template... (I added a
> placeholder to the template in Dev, and I am trying to migrate the
> modified template to the QA, amnd then to Produciton).
>
> My question is, if the destination server already has this template,
> (the old version) with existing postings connected to it, would that
> cause this issue?
>
| |
| Charly 2006-01-29, 9:09 pm |
| Stefan,
Been through all that, none of it applies or fixes the problem...
And from the same machine, using the same sql server, the import works
when done against an old backup of database, but fails when performed
against crrent database... The only difference I can see is that the
current database has postings in it which are attached to the template
I am trying to import.
| |
| Stefan [MSFT] 2006-01-29, 9:09 pm |
| Hi Charly,
if you have gone through all these steps as you outlined below, then please
send me the network monitor trace file you created in step 7 to
webmaster@stefan-gossner.de
Thanks,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------
"Charly" <cbretana@areteind.com> wrote in message
news:1138205917.070830.111600@g49g2000cwa.googlegroups.com...
> Stefan,
>
> Been through all that, none of it applies or fixes the problem...
> And from the same machine, using the same sql server, the import works
> when done against an old backup of database, but fails when performed
> against crrent database... The only difference I can see is that the
> current database has postings in it which are attached to the template
> I am trying to import.
>
| |
| Charly 2006-01-29, 9:09 pm |
| Will do... Stand by... shortly...
| |
| Charly 2006-01-29, 9:09 pm |
| Stefan,
In running through the steps again, I discovered the problem, My
root MCMS web site is running as the root web site, not as vurtual
directory... And so it has a web.config with all the CMS http modules
being loaded in it. I can't remove them from that web.config without
breaking my MCMS web site, but the site manager deployment web entry
point ha it's own web.config,
(<MCMSInstllFolder>\Server\MCMS\web.config) that was also trying to
load them... I had to deltete the reference to the http Modules from
the latter web.config, and that fixed the problem.
Thanks,
Charly
| |
| Stefan [MSFT] 2006-01-29, 9:09 pm |
| Hi Charly,
this is not the recommended solution but it will work also.
The recommended solution here would be to have two IIS websites - one with
your project in the root and one pointing ot an empty directory.
Configure the latter as read-write entry point and configure Site Manager
and site deployment to use this empty website.
Now no web.config would be in the root that could interact with the
web.config in the /MCMS virtual directory.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------
"Charly" <cbretana@areteind.com> wrote in message
news:1138224972.539310.202650@g14g2000cwa.googlegroups.com...
> Stefan,
>
> In running through the steps again, I discovered the problem, My
> root MCMS web site is running as the root web site, not as vurtual
> directory... And so it has a web.config with all the CMS http modules
> being loaded in it. I can't remove them from that web.config without
> breaking my MCMS web site, but the site manager deployment web entry
> point ha it's own web.config,
> (<MCMSInstllFolder>\Server\MCMS\web.config) that was also trying to
> load them... I had to deltete the reference to the http Modules from
> the latter web.config, and that fixed the problem.
>
> Thanks,
>
> Charly
>
| |
| Charly 2006-01-29, 9:09 pm |
| Yes, I understand your solution... but I have a question.
When you install MCMS out of the box, it asks for the web entry points
for the MCMS web site.
I assumed this meant the entry point for the site I would be using for
my MCMS project. (where authors will be going to create/edit
postings)
But the install places the MCMS web ssite entry point (Virtual
Directory) under the web entry point selected during the install. You
can't really select a different one during this porocess for your web
site project... So, is this something you just have to "know", and
change after the install is completed ?
Regards,
Charly
| |
| Stefan [MSFT] 2006-01-29, 9:09 pm |
| Hi Charly,
actually the problem is that you created the template project in the root of
the website.
That is what is not recommended.
You should create the template project in a subfolder (e.g.
http://localhost/MCMSTemplates)
Then the problem will not occur.
If you are creating the template project in the root, then you need to
manually change this.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
Check out the new book as well: Advanced MCMS development:
http://tinyurl.com/8ugwj
----------------------
"Charly" <cbretana@areteind.com> wrote in message
news:1138297499.256351.70970@g49g2000cwa.googlegroups.com...
> Yes, I understand your solution... but I have a question.
>
> When you install MCMS out of the box, it asks for the web entry points
> for the MCMS web site.
> I assumed this meant the entry point for the site I would be using for
> my MCMS project. (where authors will be going to create/edit
> postings)
> But the install places the MCMS web ssite entry point (Virtual
> Directory) under the web entry point selected during the install. You
> can't really select a different one during this porocess for your web
> site project... So, is this something you just have to "know", and
> change after the install is completed ?
>
> Regards,
>
> Charly
>
|
|
|
|
|