RE-add witness fails

I start with 3 servers, in High Safety mode with witness. I disconnect the network cable for the witness. Then I remove the witness from the mirroring session:

ALTER DATABASE db1 SET WITNESS OFF

I reconnect the witness network cable. Now I cannot add the witness back to the mirroring session (either with TSQL or thru the GUI). Here is the error message:

Msg 1433, Level 16, State 4, Server SERVERA, Line 1
All three server instances did not remain interconnected for the duration of the ALTER DATABASE SET WITNESS command. There may be no witness associated with the database. Verify the status and when necessary repeat the command.

I have to stop mirroring (SET PARTNER OFF) and then reconfigure a new mirroring session to be able to include the witness.

If I don't disconnect the network cable, I am able to remove and re-add the witness to the session, no problem.

Is this behavior expected?

Thanks in advance.

Regards,

Michael Lawson

I found my problem: my witness was at RTM. After upgrading to SP1 I was able to re-add the witness in the scenario I gave.

RDA Push fails with SQL Server 2005 Compact Edition

Hello
I have a SQL Server 2005 (build 9.0.3050) database with tables belonging to
different schemas. I am in the process of developing a Windows Mobile 5.0
application that will work against this database, and Iâ'm planning to use
Remote Data Access with SQL Server 2005 CE to synch data.
I have my RDA all set up and working correctly IIS-wise, and have no problem
pulling a table from my database. However, when I attempt to push a modified
table back to the database, I get an â'Internal error: Failure setting up
bindings, possibly caused by insufficient permissions.â' error (which equates
to error 28621: SSCE_M_BINDINGS), which according to
http://msdn2.microsoft.com/en-us/library/ms172898.aspx is an internal error
which â'cannot be resolved by common troubleshooting techniquesâ'. The
â'insufficient permissionsâ' is a red herring I think, since the problem
persists even if the SQL Server login that is being used for RDA is in the
sysadmin role.
Iâ've attempted to identify the problem by starting from scratch with a new
database and a new table with a couple of test columns. With the table
freshly created as dbo.TableName RDA works fine. However, when I create a
schema and transfer the table to the schema, RDA push fails as above, so to
me it looks like the schema is causing the problem.
Anyone any ideas about this? All help greatly appreciated!
Thanks - GrahamIn case this helps anyone else, I lodged a support call with Microsoft about
this and it has been confirmed that "SQL Server Compact Edition does not
support RDA.Push for non-default Schema tables". Hopefully this will be
fixed in the future.
"GrahamS" wrote:
> Hello
> I have a SQL Server 2005 (build 9.0.3050) database with tables belonging to
> different schemas. I am in the process of developing a Windows Mobile 5.0
> application that will work against this database, and Iâ'm planning to use
> Remote Data Access with SQL Server 2005 CE to synch data.
> I have my RDA all set up and working correctly IIS-wise, and have no problem
> pulling a table from my database. However, when I attempt to push a modified
> table back to the database, I get an â'Internal error: Failure setting up
> bindings, possibly caused by insufficient permissions.â' error (which equates
> to error 28621: SSCE_M_BINDINGS), which according to
> http://msdn2.microsoft.com/en-us/library/ms172898.aspx is an internal error
> which â'cannot be resolved by common troubleshooting techniquesâ'. The
> â'insufficient permissionsâ' is a red herring I think, since the problem
> persists even if the SQL Server login that is being used for RDA is in the
> sysadmin role.
> Iâ've attempted to identify the problem by starting from scratch with a new
> database and a new table with a couple of test columns. With the table
> freshly created as dbo.TableName RDA works fine. However, when I create a
> schema and transfer the table to the schema, RDA push fails as above, so to
> me it looks like the schema is causing the problem.
> Anyone any ideas about this? All help greatly appreciated!
> Thanks - Graham|||There is a workaround for this problem - you can use a synonym in place of
the base table name. Crucially, the synonym must be named the same as the
base table ie 'CREATE SYNONYM dbo.MyTable FOR MySchema.MyTable'.
"GrahamS" wrote:
> In case this helps anyone else, I lodged a support call with Microsoft about
> this and it has been confirmed that "SQL Server Compact Edition does not
> support RDA.Push for non-default Schema tables". Hopefully this will be
> fixed in the future.
> "GrahamS" wrote:
> > Hello
> >
> > I have a SQL Server 2005 (build 9.0.3050) database with tables belonging to
> > different schemas. I am in the process of developing a Windows Mobile 5.0
> > application that will work against this database, and Iâ'm planning to use
> > Remote Data Access with SQL Server 2005 CE to synch data.
> >
> > I have my RDA all set up and working correctly IIS-wise, and have no problem
> > pulling a table from my database. However, when I attempt to push a modified
> > table back to the database, I get an â'Internal error: Failure setting up
> > bindings, possibly caused by insufficient permissions.â' error (which equates
> > to error 28621: SSCE_M_BINDINGS), which according to
> > http://msdn2.microsoft.com/en-us/library/ms172898.aspx is an internal error
> > which â'cannot be resolved by common troubleshooting techniquesâ'. The
> > â'insufficient permissionsâ' is a red herring I think, since the problem
> > persists even if the SQL Server login that is being used for RDA is in the
> > sysadmin role.
> >
> > Iâ've attempted to identify the problem by starting from scratch with a new
> > database and a new table with a couple of test columns. With the table
> > freshly created as dbo.TableName RDA works fine. However, when I create a
> > schema and transfer the table to the schema, RDA push fails as above, so to
> > me it looks like the schema is causing the problem.
> >
> > Anyone any ideas about this? All help greatly appreciated!
> >
> > Thanks - Graham

RDA Push fails with SQL Server 2005 Compact Edition

Hello

I have a SQL Server 2005 (build 9.0.3050) database with tables belonging to
different schemas. I am in the process of developing a Windows Mobile 5.0
application that will work against this database, and I’m planning to use
Remote Data Access with SQL Server 2005 CE to synch data.

I have my RDA all set up and working correctly IIS-wise, and have no problem
pulling a table from my database. However, when I attempt to push a modified
table back to the database, I get an ‘Internal error: Failure setting up
bindings, possibly caused by insufficient permissions.’ error (which equates
to error 28621: SSCE_M_BINDINGS), which according to
http://msdn2.microsoft.com/en-us/library/ms172898.aspx is an internal error
which “cannot be resolved by common troubleshooting techniques”. The
‘insufficient permissions’ is a red herring I think, since the problem
persists even if the SQL Server login that is being used for RDA is in the
sysadmin role.

I’ve attempted to identify the problem by starting from scratch with a new
database and a new table with a couple of test columns. With the table
freshly created as dbo.TableName RDA works fine. However, when I create a
schema and transfer the table to the schema, RDA push fails as above, so to
me it looks like the schema is causing the problem.

Anyone any ideas about this? All help greatly appreciated!

Thanks - Graham

In case this helps anyone else, I lodged a support call with Microsoft about
this and it has been confirmed that "SQL Server Compact Edition does not
support RDA.Push for non-default Schema tables". Hopefully this will be
fixed in the future.
|||There is a workaround for this problem - you can use a synonym in place of the base table name. Crucially, the synonym must be named the same as the base table ie 'CREATE SYNONYM dbo.MyTable FOR MySchema.MyTable'.

RDA Push fails with SQL Server 2005 Compact Edition

Hello

I have a SQL Server 2005 (build 9.0.3050) database with tables belonging to
different schemas. I am in the process of developing a Windows Mobile 5.0
application that will work against this database, and I’m planning to use
Remote Data Access with SQL Server 2005 CE to synch data.

I have my RDA all set up and working correctly IIS-wise, and have no problem
pulling a table from my database. However, when I attempt to push a modified
table back to the database, I get an ‘Internal error: Failure setting up
bindings, possibly caused by insufficient permissions.’ error (which equates
to error 28621: SSCE_M_BINDINGS), which according to
http://msdn2.microsoft.com/en-us/library/ms172898.aspx is an internal error
which “cannot be resolved by common troubleshooting techniques”. The
‘insufficient permissions’ is a red herring I think, since the problem
persists even if the SQL Server login that is being used for RDA is in the
sysadmin role.

I’ve attempted to identify the problem by starting from scratch with a new
database and a new table with a couple of test columns. With the table
freshly created as dbo.TableName RDA works fine. However, when I create a
schema and transfer the table to the schema, RDA push fails as above, so to
me it looks like the schema is causing the problem.

Anyone any ideas about this? All help greatly appreciated!

Thanks - Graham

In case this helps anyone else, I lodged a support call with Microsoft about
this and it has been confirmed that "SQL Server Compact Edition does not
support RDA.Push for non-default Schema tables". Hopefully this will be
fixed in the future.
|||There is a workaround for this problem - you can use a synonym in place of the base table name. Crucially, the synonym must be named the same as the base table ie 'CREATE SYNONYM dbo.MyTable FOR MySchema.MyTable'.