BizTalk Server Orchestration - Problems executing XLANG schedules with BizTalk 2002 on Win2003

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Orchestration > December 2004 > Problems executing XLANG schedules with BizTalk 2002 on Win2003





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 Problems executing XLANG schedules with BizTalk 2002 on Win2003
jeremy@pdq.net

2004-12-21, 5:51 pm

I've installed BizTalk Server 2002 Standard edition on Windows 2003
Server Standard and I am unable to execute XLANG schedules through a
moniker VBScript or otherwise.

My install plan was as follows:
- Update Windows 2003 with latest patches (all available updates were
applied)

Installed
1. IIS and MSMQ services
2. SQL Server 2000 Enterprise Server
3. SQL Server 2000 SP3a
4. Microsoft visio 2002 Professional (sR1)
5. BizTalk 2002 Standard Edition
6. BizTalk 2002 SP1

After installing I created two public Message Queues named test_in and
test_out

I then opend BizTalk Orchestration designer and created a simple XLANG
that reads from test_in and sends to test_out (no processing) just two
Action and two ports. The XLANG successfully compiled

I then created a VBScript file to act as a moniker for my schedule:

'------------------------
On Error Resume Next
Set objExecute = GetObject("sked:///c:\XLANGs\test1.skx")

If Err.number <> 0 Then
msgbox "Error number is: " & err.number & vbcrlf & "Error Description
is: " & err.description
Else
MsgBox "Success"

'------------

When I use Windows Explorer to execute the VBScript file it runs and
returns the following error:

Error number is: -2147467238
Error description:

I've tried creating two other XLANG schedules (by simplistic and
slightly different) and continue to get this problem. I've also rebuilt
the server from scratch one time and the problem continues to persist.

Some additional steps I've tried:

Under IIS Server Extenshions I have gone in and set WebDav and ASP to
"Allowed", they were disabled by default.

Under Component Services->COM+ Applications I've set the Identity on
the XLANG Schedule Pool to an account with local Admin rights. I've
also experimented creating a user account with full SQL Server admin
rights as well as local system Admin rights, with no luck. Identity can
not be set on the other COM+ apps.
I've confirmed the XLANG Schedule Pool is running/started.

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com