Are you importing via the on-line workflow or batch?
If on-line is the source file in the FDM Inbox / location folder or in a windows folder on another server?
If the source file is not in the FDM Inbox (or the Inbox / location folder) then place it there before performing the import and see if you get the same result.
Thanks for your reply
we are able to import data file from FDM inbox folder ,but not able to load data from local system or from other location
is there any solution for this ?
Sounds like a security issue. when you import from a local drive, the first thing FDM does is copy the file into the inbox. It could be that the nexessary security has been set up to allow this write to occur to the inbox / folder structure.
Thanks for the replies
issue Issue resolved
I have done following changes Request Filtering Size in IIS 7 need to be extended.
Even we are facing similar issue at our clients end and we suggested the same but the issue persists.Anymore directions needed to resolve the issue.
Import,validate is fine and in export the data file gets created but doesn't get loaded to the target system and the error 404 pops up.