|
|
|
|
|
|
|
|
|
|
 To create new posts or to reply to existing ones, you must be registered and logged in! |
Edited: 6/30/2008 12:22 PM | |
|  | Content Deployment in MOSS 2007
I've setup content deployment on 2 x 64 bit machines as a test, and it worked perfect.
Then tried to set it up at a client site but this time it would deploy from a 64 bit machine to a 32 bit machine and it failed.
A call has been logged with MS in Europe but it was never resolved.
If anyone has any idea how to fix this it would be greatly appreciated if you can assist - OR if you have a definite answer if the deployment fails because it cannot deploy from 64 bit to 32 bit and vice versa, please reply to this post.
Thanks!! W.  |  |
Posted: 6/30/2008 6:00 PM | |
|  | Hi Wim,
Please can you give the error that you get. This will help a great deal!
Hope this helps,
Michael  |  |
|  | Michael
Thanks for your reply.
Unfortunately I didn't copy the error and am not on site at the client to get it. I will however try to get it and then post it.
Have a nice day!!
Ciao!
Wim.  |  |
Posted: 7/7/2008 11:59 AM | | |
|  | Hi Micheal
I finaly managed to get screen shots of some of the errors.
OK, firstly a quick rundown on the happenings around the CD we are trying to setup.
1) We have treid to setup content deployment from a 64bit setup to a 32 bit setup and got some hectic error, which I have not been able to replicate, as the servers have been moved and the environment has changed a bit.
2) We have now setup the CD to deploy from a 32bit setup to a 64 bit setup and it was able to deploy some of the content, but we got the very same errors as what was given through to Microsoft Europe to try resolve. Have not yet heard anything back from them and that was somehting like 11 or 12 months ago.
I've attached 3 screenshots of some of the 44 errors that was received.
Thanks for your help!!  |  |
Posted: 7/8/2008 11:05 AM | |
|  | Hi Wim,
Did you manage to look through the articles on Stefan's blog? I have not seen these errors before, but perhaps these few tips might help.
2. Make sure you destination site was created from blank site template
3. Common issues are around different site features being available in the source and destination site collections. Stefan has some tools to help identify these scenarios.
Michael  |  |
|
| Edit in Browser | /_layouts/images/icxddoc.gif | /forums/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /forums/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /forums/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /forums/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /forums/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /forums/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /forums/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /forums/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /forums/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
|
|
|
|