|
Home > Archive > Microsoft Content Management Server > March 2004 > Sitemanager Export Error
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]
| Author |
Sitemanager Export Error
|
|
|
| Hallo,
i get a strange error everytime i want to export a
package from the sitemanager (CMS 2002, SP1a,
Win2003Server). I can't export anything.
Error: 0
Description: Bad file name or number
Severity: 5
Source: NRSiteDeployUI
Debug info: N/A
Extra info: N/A
Client Source: CSiteDeploy::Init
Recommended Action: N/A
Any solution around?
Thanks and best regards,
Nick
| |
| Stefan [MSFT] 2004-03-30, 11:43 am |
| Hi Nick,
as indicated yesterday this error seems to indicate a problem when opening
the SiteDeployment Manager window.
Try if reinstalling SiteManager solves the issue. If not I would suggest to
open a support call with Microsoft.
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Nick" <anonymous@discussions.microsoft.com> wrote in message
news:156a101c4163e$c60caf40$a301280a@phx
.gbl...
> Hallo,
>
> i get a strange error everytime i want to export a
> package from the sitemanager (CMS 2002, SP1a,
> Win2003Server). I can't export anything.
>
> Error: 0
> Description: Bad file name or number
> Severity: 5
> Source: NRSiteDeployUI
> Debug info: N/A
> Extra info: N/A
> Client Source: CSiteDeploy::Init
> Recommended Action: N/A
>
> Any solution around?
> Thanks and best regards,
> Nick
| |
|
| Hi Stefan,
re-installing does not solve the problem  So only way
left is to open a support call?
Pretty strange thing... Could this be a problem of
running CMS on a Win2003 server? This error never showed
up before on our old installation (on Win2000 Server).
Thanks and regards,
Nick
>-----Original Message-----
>Hi Nick,
>
>as indicated yesterday this error seems to indicate a
problem when opening
>the SiteDeployment Manager window.
>Try if reinstalling SiteManager solves the issue. If not
I would suggest to
>open a support call with Microsoft.
>
>Cheers,
>Stefan.
>
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>
>"Nick" <anonymous@discussions.microsoft.com> wrote in
message
> news:156a101c4163e$c60caf40$a301280a@phx
.gbl...
>
>
>.
>
| |
| Stefan [MSFT] 2004-03-31, 12:44 pm |
| Hi Nick,
no this is not a problem with Windows Server 2003.
This is not a known problem. You should open a support case for this.
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Nick" <anonymous@discussions.microsoft.com> wrote in message
news:1672401c41703$0999ed80$a101280a@phx
.gbl...[color=darkred]
> Hi Stefan,
>
> re-installing does not solve the problem So only way
> left is to open a support call?
>
> Pretty strange thing... Could this be a problem of
> running CMS on a Win2003 server? This error never showed
> up before on our old installation (on Win2000 Server).
>
> Thanks and regards,
> Nick
>
>
> problem when opening
> I would suggest to
> confers no rights.
> message
|
|
|
|
|