hi,

i added 4 new schema fields from the deployment manager (2 to accounts, 2 to
opportunities) and map them. and i publish the customization. it was ok in
test server but when i did the same thing in production server i received
the following error. any ideas?

thanks in advance
orkun

error:
Event Type: Error
Event Source: DMSNAPIN
Event Category: None
Event ID: 0
Date: 26.01.2005
Time: 17:23:30
User: N/A
Computer: MOSTSERVER
Description:
ProcessImportWorkItem Error : The network path was not found.
, StackTrace : at System.IO.__Error.WinIOError(Int32 errorCode, String
str)
at System.IO.File.InternalCopy(String sourceFileName, String
destFileName, Boolean overwrite)
at
Microsoft.Crm.Tools.ImportExportXml.XmlCustomizati on.ProcessImportWorkItem(Object
status)

Well it sounds like this is happening during the part where it attempts to
write the various Form XSL files to the web server's hard drive. 90% of the
time this is because the server does not respond to the URL that the Publish
Tool is using... this often happens in SBS environments, where by default
the CRM Web site will not respond to http://mostserver but instead responds
only to http://crm.mostserver or something like that. The biggest problem
is that the Deployment Tool is not very good about telling you what it was
trying to do when the error occurred.





Your best bet is to do the following (which never fails):



- Install Visual C# 2003 on the box from where you are trying to publish.

- Load the Deployment Manager

- Fire up the managed portion of the code

(Right-click on Deployment Manager | All Tasks | Publish)

- Attach the debugger to the MMC instance that is running DMSnapin (Tools |
Debug Process...)

(Select "mmc.exe")

- Choose to debug "Common Language Runtime"

- Configure VC# to "Break on all exceptions".

(Debug | Exceptions | When Exception is thrown | Break into the debugger)

- Run the publish routine...

- When the debugger breaks you will not be able to able to see the code
(since you don't have it, this is ok)... but what you can see is the value
of "sourceFileName" and "destFileName" using the Watch or Local variable
windows. This will tell you exactly what and where it is trying to write
files.



Using this information, you can verify that server is indeed reachable by
that name and that the destination location is valid.



Hope this helps,



Aaron Elder
Director, Software Development

Invoke Systems
Solid technology. Sound thinking.
http://www.invokesystems.com


"SadiBey" <sorkung@yahoo.com> wrote in message
news:O6mCo37AFHA.2316@TK2MSFTNGP15.phx.gbl...