Pete Bradley
Guest
|
 Posted:
Tue Jan 18, 2005 2:59 pm Post subject:
Please help! SDAPI import problem |
|
|
Hi,
We have been hired by our client to write an automated
system that packages up the content created on their
staging server MCMS installation, transmits via FTP the
SDO to their production server (hosted by a different
company at a different location), and imports the SDO into
the production server MCMS installation.
We have written the system and it works perfectly when the
SDO file side is less than around 3.5 MB. When the SDO
file size is larger than this approximate limit, the
exception thrown by the import operation is: "The
compressed file could not be opened - it is possibly
corrupt".
The system includes CRC checking so we know the file is
not corrupt. Additionally, if we use Site Manager to
manually import the exact same file on the production
server, it imports just fine. We have looked at disk space
and quota issues - there is a huge amount of disk space,
no quotas enforced, and the server has over 1GB of RAM.
The service user (it runs as a windows service) has full
access to the temp folders, and is part of the MCMS
Adminstrators group. The SQL Server is on a seperate
server to the MCMS server.
The system uses the server-side site deployment API object
from C#
(Microsoft.ContentManagement.Interop.NRSiteDeployServer.Cms
DeployImportClass).
We have had 5 seperate MCMS-experienced brains thinking
and researching this problem all day, and we still don't
know what could be causing this. Please if you could
possibly offer any insight, it would be greatly
appreciated.
Thanks and regards,
Pete Bradley |
|
Stefan [MSFT]
Guest
|
| Posted:
Tue Jan 18, 2005 5:25 pm Post subject:
Re: Please help! SDAPI import problem |
|
|
Hi Pete,
you should open a support case with Microsoft for this as this requires
deeper investigations.
Cheers,
Stefan.
"Pete Bradley" <peterb@changecoroporation.com.au> wrote in message
news:039801c4fd3b$fa0536c0$a601280a@phx.gbl...
| Quote: | Hi,
We have been hired by our client to write an automated
system that packages up the content created on their
staging server MCMS installation, transmits via FTP the
SDO to their production server (hosted by a different
company at a different location), and imports the SDO into
the production server MCMS installation.
We have written the system and it works perfectly when the
SDO file side is less than around 3.5 MB. When the SDO
file size is larger than this approximate limit, the
exception thrown by the import operation is: "The
compressed file could not be opened - it is possibly
corrupt".
The system includes CRC checking so we know the file is
not corrupt. Additionally, if we use Site Manager to
manually import the exact same file on the production
server, it imports just fine. We have looked at disk space
and quota issues - there is a huge amount of disk space,
no quotas enforced, and the server has over 1GB of RAM.
The service user (it runs as a windows service) has full
access to the temp folders, and is part of the MCMS
Adminstrators group. The SQL Server is on a seperate
server to the MCMS server.
The system uses the server-side site deployment API object
from C#
(Microsoft.ContentManagement.Interop.NRSiteDeployServer.Cms
DeployImportClass).
We have had 5 seperate MCMS-experienced brains thinking
and researching this problem all day, and we still don't
know what could be causing this. Please if you could
possibly offer any insight, it would be greatly
appreciated.
Thanks and regards,
Pete Bradley
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in