
The web application at "" could not be found.verify that you have typed the URL correctly.If the URL should be serving existing content,the system administrator may beed to add a new request.
The solution to this problem is :
InfoPath is a 32 bit app and is loading a 64 bit binary (Microsoft.sharepoint.dll)
so what we have is a 32 bit process (InfoPath) running on a 64 bit OS, wow64 will
translate registry calls to the wow64 registry note, and
"HKLM\\wow6432node\SOFTWARE\\Microsoft\\Shared Tools\\Web Server
Extensions\\12.0\\Secure\\ConfigDB" does not exist. Since the 64 bit version of
SharePoint is installed, wow64 does not get involved and the registry key
"HKLM\\SOFTWARE\\Microsoft\\Shared Tools\\Web Server
Extensions\\12.0\\Secure\\ConfigDB" is used to store the farm’s connection string
info.
There is no 64 bit version of InfoPath. For Office2007, we support mixing 32-bit
and 64-bit front end servers in the same farm, with the caveat being that customer
must install 32-bit WSS on a 32-bit OS and 64-bit WSS on a 64-bit OS. We do not
support 32-bit WSS v3 on a 64-bit OS via WOW64. If InfoPath 2007 is calling our OM
and installed on a SharePoint box, then they’ll have to install it on an front end
server where 32-bit WSS is running on a 32-bit OS.
The solution would be to add a 32 bit server with 32 bit MOSS and
InfoPath installed to the farm.
And my sincere thanks to Travis Mathison,Sailaja kalidindi on helping this issue. :)