HELP! EM wont connect after apply sp3a,reporting services and VS.net 2003

Install SQL 2000 on a completelyu up to date windows 2003 advanced server,
then applied sp3a, then a installed reporting service developer addition,
then installed VS .net 2003 the reinstalled reporting services to get the
Report Developer.
Now I can't connect to the Server using EM.
Get SQL_alloc_handle on SQL_handle_env failed.
Tried all types of registrations.
Any suggestions short of starting from scratch?Make an ODBC trace of the connection attempt & open a case with the Webdata
team. They handle the MDAC problems with SQL.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Will do that if re-install of tools SQL fails. How do I open a case with the
WEBdata Team.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:XWmAGmZ9DHA.704@.cpmsftngxa07.phx.gbl...
> Make an ODBC trace of the connection attempt & open a case with the
Webdata
> team. They handle the MDAC problems with SQL.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>

Help with Web Sync sql 2005 to sql express

Hello,

OK I finally got the subscriber connected to the IIS server for replication. I am now getting errors when trying to apply the snap shot. Below is the error? Did I setup the publication incorrectly by selecting replication with another sql 2005? Am I supposed to select something different when trying to replicate between slq 2005 and sql express?

Source: Merge Replication Provider
Number: -2147201001
Message: The schema script 'activities_2.sch' could not be propagated to the subscriber.
2005-08-24 20:52:35.920 Percent Complete: 0
2005-08-24 20:52:35.920 Category:NULL
Source: Microsoft SQL Native Client
Number: 1703
Message: Online index operations can only be performed in Enterprise edition of SQL Server.

'activities_2.sch' script

drop Table [dbo].[activities]
go
SET ANSI_PADDING ON
go

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[activities](
[activity] [varchar](50) NOT NULL,
[billing] [bit] NOT NULL,
[category] [varchar](50) NULL,
[rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL CONSTRAINT [MSmerge_df_rowguid_77F8C0F06FB942A7B7206EF4GD99AD745] DEFAULT (newsequentialid())
)

GO
SET ANSI_NULLS OFF
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
go
SET QUOTED_IDENTIFIER ON
go
ALTER TABLE [dbo].[activities] ADD CONSTRAINT [PK_activities] PRIMARY KEY CLUSTERED
(
[activity] ASC
)WITH (SORT_IN_TEMPDB = OFF, ONLINE = OFF)
GO

I've experienced the same problem but am struggling with the bitwise syntax for disabling the XMLIndex schema option using sp_changemergearticle. Could you provide an example?

Also, as an alternative workaround during development I've been manually commenting out the problem index from the .dri and .sch files in the snapshot:

--WITH (SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF)

Obviously it would better to fix the XMLIndex schema option than to have to do this everytime I create a new snapshot!

Thanks, STEVE

|||The current schema option should be something like: 0x04nnnnnn
To remove the XML index, make it 0x00nnnnnn and run snapshot again and sync (reinit).

If it is 0x07nnnnnn, then make it 0x03nnnnnn.
Basically you want to remove the 04 part in it.|||The current schema options on my tables is :

0x000000000C034FD1

I tried changing it to

0x000000000C030FD1

but that didn't work.

Any ideas?

|||The current schema option: 0x000000000C034FD1
New one to try: 0x0000000008034FD1|||This was a known problem with Express subscribers.
Which CTP are you using? This should be fixed in the further CTPs. Either try the next CTP or there is a workaround below:

Meanwhile you can workaround the issue by disabling the XMLIndex schema option (0x04000000) on the table articles.

Use sp_changemergearticle to change the schema_option to remove this and then the snapshot should be applied correctly.