File ReceiveLocation - ServiceWindow Issue

File ReceiveLocation - ServiceWindow Issue

Post by c3VsbH » Fri, 14 Jul 2006 20:29:02


Hi All,

I have created a pretty simple ReceivePort with PassThru pipeline and i have
specified the service window properties of the receive location using Biztlak
explorer as..


StartDate : 13/07/2006
StopDate :13/07/2006
Enable the Service Window = true
Start Time : 10:30
Stop Time : 11:00

and the Receive Location is Enabled.

Now when i drop a input file in the file location..it is not been picked up...
even during the service window time..

what is wrong with the settings and how to make this to work..




--
Many Thanks,
Sulaiman Abubacker
 
 
 

File ReceiveLocation - ServiceWindow Issue

Post by RmlzaWNhY2 » Wed, 19 Jul 2006 23:56:01

Hi,

I suppose so, but:

- Were receive folder and input mask defined?
- Was send port enlisted?

I think so, but you should confirm...

Regards,

 
 
 

File ReceiveLocation - ServiceWindow Issue

Post by skade » Thu, 20 Jul 2006 05:38:22

I donot think there should be any problem with as simple as file receive
during the service window period.

- Can you check if the receive location is enabled?
- Can you check the URI of the receive location?
- Can you check if the host instance is running?
- Can you check if ther is any event log message? Probably it picked up but
could not delete the file or something?

Thanks
Sultan

This posting is provided "AS IS" with no warranties, and confers no rights.

Business Process Integration Team


Get Connected!
Meet and interact with key BizTalk Server program managers, developers, and
testers, and let them and other BizTalk Server community team members and
Most Valuable Professionals help you solve your product questions.

Navigate to http://www.yqcomputer.com/
webrowser and register as a managed customer to receive MSDN Managed
Newsgroup Support!

MSDN managed newsgroups are available in English to MSDN Universal,
Enterprise, Professional, and Operating Systems subscribers to receive
free, unlimited technical support on select Microsoft technologies as well
as to share ideas with other subscribers.
--------------------
have
Biztlak
up...
 
 
 

File ReceiveLocation - ServiceWindow Issue

Post by Tom » Fri, 21 Jul 2006 00:10:02

Sulaiman,
Please turn off the File Receive Service window and simply get the
receive location working first. This is probably not an issue with the
Service Window, but a problem with the receive location.


-------------------------------
Files Are Not Being Read
The File receive adapter does not read a file from the receive location
if any of the following conditions apply:

The file is read-only.

The file has a system attribute.

The File receive adapter does not have permissions to read and write to
the file.

When the File receive adapter encounters such a file, it logs an error
in the event log and leaves the file in the receive location.

-----------------------

Please check each of these, and check the event log for any errors.

Also, the BizTalk Administrator UI does not automatically refresh, so
the receive location may display as Enabled until you exit and restart
or click Refresh. So the state displayed may not match the actual state
until you refresh. This includes clicking on another node and then
clicking back on the receive locations. This does not force a refrresh.

Tom Canter

----------------------------
Receive Location is Disabled
The File receive adapter disables the receive location if any of
following occur:

The File receive adapter cannot access the receive location on the file
system or network share because the specified path does not exist. For
a network share, the File receive adapter disables the receive location
after all retry attempts have been exhausted.


The File receive adapter cannot access the receive location on the file
system or network share because it does not have read-write permission
for that location. For a network share, the File receive adapter
disables the receive location after all retry attempts have been
exhausted.


Files with names longer than 256 characters are encountered in the
receive location.
------------------------------