12-16-04 11:49 PM
The problem is that you have VS 2005 beta1 on the same machine with VS
2003. It is not a supported scenario for Biztalk Server 2004.
This posting is provided "AS IS" with no warranties, and confers no rights.
EBusiness Server Team
--------------------
| >>Thread-Topic: publishing the sample ExposeWebService as WebService
| >>thread-index: AcThTaIGk7y35LYGRD+CXPGZt9NGfw==
| >>X-WBNR-Posting-Host: 83.141.72.72
| >>From: "examnotes" <Michael
Glienecke@discussions.microsoft.com>
| >>Subject: publishing the sample ExposeWebService as WebService
| >>Date: Mon, 13 Dec 2004 11:55:02 -0800
| >>Lines: 19
| >>Message-ID: <813B666A-5366-4B64-BBF1-62AECD3DBB52@microsoft.com>
| >>MIME-Version: 1.0
| >>Content-Type: text/plain;
| >> charset="Utf-8"
| >>Content-Transfer-Encoding: 7bit
| >>X-Newsreader: Microsoft CDO for Windows 2000
| >>Content-Class: urn:content-classes:message
| >>Importance: normal
| >>Priority: normal
| >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| >>Newsgroups: microsoft.public.biztalk.orchestration
| >>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| >>Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
| >>Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.orchestration:9343
| >>X-Tomcat-NG: microsoft.public.biztalk.orchestration
| >>
| >>I am sure this question has been somehow referenced in other sections,
too,
| >>but I couldn't find a 100% match to my problem.
| >>
| >>When using the provided sample from BizTalk in
| >>\orchestrations\ExposeWebService and running setup.bat everything seems
to
| >>work fine but no WebService is published. When you open VS.NET 2003 and
| >>rebuild everything (before calling cleanup.bat) and then try to run the
| >>WebService Publishing Wizard from BizTalk I always get a COMException
| >>0x80030002 (STG_E_FILENOTFOUND) for some reason.
| >>
| >>I do have XP with SP2, VS.NET 2003 and 2005 Beta 1 installed (is that
the
| >>problem?) and currently ASP.NET 1.1 active (but 2.0 is installed due to
| >>VS.NET 2005).
| >>
| >>This seems quite strange and I tried already several things about
adding to
| >>ASPNET user to the BizTalk isolated hosts group (which might be totally
| >>stupid).
| >>
| >>
| >>
[ Post a follow-up to this message ]
|