|
Home > Archive > BizTalk Server > July 2004 > EDI receiver does not scan the pickup edi location at all
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
EDI receiver does not scan the pickup edi location at all
|
|
| Montaque 2004-07-26, 8:52 pm |
| I have succefully started the edi and biztalk service, and deployed the Get
started with edi sample. when i throw a edi file to the default edipickup
directory, the edi file can not be picked up.
when i use filemon to monitor the edi and biztalk process, they did not scan
the pickupedi directory, the events.log have the following entry.
Tue Jul 27 09:47:51 Communicate, submit session started for BizTalk(R) 2004
Tue Jul 27 09:47:51 Communicate, submit batch started for BizTalk(R) 2004
Tue Jul 27 09:47:51 Communicate, session finished successfully for
BizTalk(R) 2004
Tue Jul 27 09:47:59 Communicate, submit session started for File system
Tue Jul 27 09:47:59 Communicate, submit batch started for File system
Tue Jul 27 09:48:00 Communicate, session failed for File system //what's
wrong?
Tue Jul 27 09:48:19 Notification process, OUTGOING CheckRequestTimeout
session started
Tue Jul 27 09:48:19 Notification process, OUTGOING CheckRequestTimeout
session finished
Tue Jul 27 09:48:19 Notification process, INCOMING CheckRequestTimeout
session started
Tue Jul 27 09:48:19 Notification process, INCOMING CheckRequestTimeout
session finished
EDI in biztalk is easy to crash 
I am so dispointed. 55555555
--
Thank you for your time!
| |
| EastOx 2004-07-27, 5:53 pm |
| I got same problem. Please post message when you fix it. as well as me. Thanks.
"Montaque" wrote:
> I have succefully started the edi and biztalk service, and deployed the Get
> started with edi sample. when i throw a edi file to the default edipickup
> directory, the edi file can not be picked up.
>
> when i use filemon to monitor the edi and biztalk process, they did not scan
> the pickupedi directory, the events.log have the following entry.
>
> Tue Jul 27 09:47:51 Communicate, submit session started for BizTalk(R) 2004
> Tue Jul 27 09:47:51 Communicate, submit batch started for BizTalk(R) 2004
> Tue Jul 27 09:47:51 Communicate, session finished successfully for
> BizTalk(R) 2004
> Tue Jul 27 09:47:59 Communicate, submit session started for File system
> Tue Jul 27 09:47:59 Communicate, submit batch started for File system
> Tue Jul 27 09:48:00 Communicate, session failed for File system //what's
> wrong?
> Tue Jul 27 09:48:19 Notification process, OUTGOING CheckRequestTimeout
> session started
> Tue Jul 27 09:48:19 Notification process, OUTGOING CheckRequestTimeout
> session finished
> Tue Jul 27 09:48:19 Notification process, INCOMING CheckRequestTimeout
> session started
> Tue Jul 27 09:48:19 Notification process, INCOMING CheckRequestTimeout
> session finished
>
>
> EDI in biztalk is easy to crash
> I am so dispointed. 55555555
> --
> Thank you for your time!
>
>
>
>
| |
| larry franks 2004-07-27, 5:53 pm |
| Hi Montaque, can we try enabling EDI tracing and see if additional
information is logged?
First stop the Base EDI service.
Next go to \program files\microsoft biztalk server 2004\edi\subsystem and
open EDIBTSMMC.msc.
In here expand the Microsoft Biztalk Server 2004 Base EDI Adapter entry,
click on parameters, and right click on the server listed in the right pane
and select properties.
Here go to the trace tab. Set the tracefile path to c:\tetrace.log and
check off all the checkboxes.
Ok out of here and restart the EDI service and reproduce the problem, then
post the logfile created and turn logging back off.
Larry Franks
This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/defaul...msdn/nospam.asp
&SD=msdn
--------------------
| From: "Montaque" <Rainman_am_I@hotmail.com>
| Subject: EDI receiver does not scan the pickup edi location at all
| Date: Tue, 27 Jul 2004 09:49:49 +0800
| Lines: 32
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.3790.181
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181
| Message-ID: <O8qkHv3cEHA.3260@TK2MSFTNGP09.phx.gbl>
| Newsgroups: microsoft.public.biztalk.server
| NNTP-Posting-Host: 218.79.97.48
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA06.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08
.phx.gbl!TK2MSFTNGP09.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.server:10017
| X-Tomcat-NG: microsoft.public.biztalk.server
|
| I have succefully started the edi and biztalk service, and deployed the
Get
| started with edi sample. when i throw a edi file to the default edipickup
| directory, the edi file can not be picked up.
|
| when i use filemon to monitor the edi and biztalk process, they did not
scan
| the pickupedi directory, the events.log have the following entry.
|
| Tue Jul 27 09:47:51 Communicate, submit session started for BizTalk(R)
2004
| Tue Jul 27 09:47:51 Communicate, submit batch started for BizTalk(R) 2004
| Tue Jul 27 09:47:51 Communicate, session finished successfully for
| BizTalk(R) 2004
| Tue Jul 27 09:47:59 Communicate, submit session started for File system
| Tue Jul 27 09:47:59 Communicate, submit batch started for File system
| Tue Jul 27 09:48:00 Communicate, session failed for File system
//what's
| wrong?
| Tue Jul 27 09:48:19 Notification process, OUTGOING CheckRequestTimeout
| session started
| Tue Jul 27 09:48:19 Notification process, OUTGOING CheckRequestTimeout
| session finished
| Tue Jul 27 09:48:19 Notification process, INCOMING CheckRequestTimeout
| session started
| Tue Jul 27 09:48:19 Notification process, INCOMING CheckRequestTimeout
| session finished
|
|
| EDI in biztalk is easy to crash
| I am so dispointed. 55555555
| --
| Thank you for your time!
|
|
|
|
|
|
|
|
|