I am trying to get an XP machine to insert data into a linked Windows
2003 SBS Premium machine. I have done it w/ XP to 2003 but the SBS seems
to have a different Security Configuration on the MSDTC tab in the
COmponent Services. There are no options for inbound or outbound, only:
Network DTC access (checked)
Network Administration (not checked)
Network Transactions (not checked)
Network Clients (not checked)
Transaction Internet Protocol (TIP) Transactions (not checked)
XA Transactions (not checked)
I have done the Application Server option for Network DTC Access.
Any ideas why the screen is different and what I can do to fix?
The server properties say:
Microsoft Windows Server 2003
for Small Business Server
Darin
*** Sent via Developersdex http://www.codecomments.com ***
Hi
I assume that distributed transactions are not working? You may want to ask
in the SBS newsgroup why this is different microsoft.public.windows.server.sbs
John
"Darin" wrote:
> I am trying to get an XP machine to insert data into a linked Windows
> 2003 SBS Premium machine. I have done it w/ XP to 2003 but the SBS seems
> to have a different Security Configuration on the MSDTC tab in the
> COmponent Services. There are no options for inbound or outbound, only:
> Network DTC access (checked)
> Network Administration (not checked)
> Network Transactions (not checked)
> Network Clients (not checked)
> Transaction Internet Protocol (TIP) Transactions (not checked)
> XA Transactions (not checked)
> I have done the Application Server option for Network DTC Access.
> Any ideas why the screen is different and what I can do to fix?
> The server properties say:
> Microsoft Windows Server 2003
> for Small Business Server
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***
>
Showing posts with label windows2003. Show all posts
Showing posts with label windows2003. Show all posts
Monday, March 19, 2012
component services, DTC network access
I am trying to get an XP machine to insert data into a linked Windows
2003 SBS Premium machine. I have done it w/ XP to 2003 but the SBS seems
to have a different Security Configuration on the MSDTC tab in the
COmponent Services. There are no options for inbound or outbound, only:
Network DTC access (checked)
Network Administration (not checked)
Network Transactions (not checked)
Network Clients (not checked)
Transaction Internet Protocol (TIP) Transactions (not checked)
XA Transactions (not checked)
I have done the Application Server option for Network DTC Access.
Any ideas why the screen is different and what I can do to fix?
The server properties say:
Microsoft Windows Server 2003
for Small Business Server
Darin
*** Sent via Developersdex http://www.codecomments.com ***Hi
I assume that distributed transactions are not working? You may want to ask
in the SBS newsgroup why this is different microsoft.public.windows.server.s
bs
John
"Darin" wrote:
> I am trying to get an XP machine to insert data into a linked Windows
> 2003 SBS Premium machine. I have done it w/ XP to 2003 but the SBS seems
> to have a different Security Configuration on the MSDTC tab in the
> COmponent Services. There are no options for inbound or outbound, only:
> Network DTC access (checked)
> Network Administration (not checked)
> Network Transactions (not checked)
> Network Clients (not checked)
> Transaction Internet Protocol (TIP) Transactions (not checked)
> XA Transactions (not checked)
> I have done the Application Server option for Network DTC Access.
> Any ideas why the screen is different and what I can do to fix?
> The server properties say:
> Microsoft Windows Server 2003
> for Small Business Server
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***
>
2003 SBS Premium machine. I have done it w/ XP to 2003 but the SBS seems
to have a different Security Configuration on the MSDTC tab in the
COmponent Services. There are no options for inbound or outbound, only:
Network DTC access (checked)
Network Administration (not checked)
Network Transactions (not checked)
Network Clients (not checked)
Transaction Internet Protocol (TIP) Transactions (not checked)
XA Transactions (not checked)
I have done the Application Server option for Network DTC Access.
Any ideas why the screen is different and what I can do to fix?
The server properties say:
Microsoft Windows Server 2003
for Small Business Server
Darin
*** Sent via Developersdex http://www.codecomments.com ***Hi
I assume that distributed transactions are not working? You may want to ask
in the SBS newsgroup why this is different microsoft.public.windows.server.s
bs
John
"Darin" wrote:
> I am trying to get an XP machine to insert data into a linked Windows
> 2003 SBS Premium machine. I have done it w/ XP to 2003 but the SBS seems
> to have a different Security Configuration on the MSDTC tab in the
> COmponent Services. There are no options for inbound or outbound, only:
> Network DTC access (checked)
> Network Administration (not checked)
> Network Transactions (not checked)
> Network Clients (not checked)
> Transaction Internet Protocol (TIP) Transactions (not checked)
> XA Transactions (not checked)
> I have done the Application Server option for Network DTC Access.
> Any ideas why the screen is different and what I can do to fix?
> The server properties say:
> Microsoft Windows Server 2003
> for Small Business Server
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***
>
Sunday, February 19, 2012
COMPLETE NEWBIE - sorry :-(
I have mysql running on a windows2003 webserver - it runs a
messageboard and oscommerce. Potential new client wants to replicate
information from the website to her server - is this possible with
mysql or do I need to install sql (proper) ... sorry if I sound like I
don't know fully what I am doing - i dont!!
Any advice or pointers given would be greatly appreciated.
thanks
Jeff
Jeff/Andrew,
this is a MS SQL Server Replication newsgroup - surely there are dedicated
MySQL discussion boards?
Rgds,
Paul Ibison
|||On Sun, 24 Apr 2005 19:07:16 +0100, "Paul Ibison"
<Paul.Ibison@.Pygmalion.Com> wrote:
>Jeff/Andrew,
>this is a MS SQL Server Replication newsgroup - surely there are dedicated
>MySQL discussion boards?
>Rgds,
>Paul Ibison
>
I can't find one and I suspect I will end up installing SQL for
replication - can someone please advise?
|||Have a look at http://forums.mysql.com/list.php?26
From the point of view of SQL Server Replication, you can certainly achieve
your aim. For the new client you need to consider latency (time between
change on the publisher and corresponding change arriving at the subscriber)
, autonomy (can they be offline) and if the subscriber is read-only or
read-write. Answering these will lead to the correct type of replication.
Having SQL Server on the webserver would mean this is the publisher.
Heterogenous subscribers are supported to differing extents, but
connectivity to MYSQL is possible and is illustrated in Hilary's book below.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||while I'd love you to buy my book
1) its covered on the free downloadable sample chapter
http://www.nwsu.com/lowres_replication_ch02.pdf
2) Replication to MySQL doesn't work - or works until the distribution agent
stops and then you have to resync to get it working again due to a SQL
Server bug.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23CtbxJQSFHA.2748@.TK2MSFTNGP09.phx.gbl...
> Have a look at http://forums.mysql.com/list.php?26
> From the point of view of SQL Server Replication, you can certainly
> achieve your aim. For the new client you need to consider latency (time
> between change on the publisher and corresponding change arriving at the
> subscriber) , autonomy (can they be offline) and if the subscriber is
> read-only or read-write. Answering these will lead to the correct type of
> replication. Having SQL Server on the webserver would mean this is the
> publisher. Heterogenous subscribers are supported to differing extents,
> but connectivity to MYSQL is possible and is illustrated in Hilary's book
> below.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Interesting - thanks for the clarification. In that case your (Andrew's)
client might want to consider MSDE as a replacement for a MySQL subscriber.
Rgds,
Paul Ibison
messageboard and oscommerce. Potential new client wants to replicate
information from the website to her server - is this possible with
mysql or do I need to install sql (proper) ... sorry if I sound like I
don't know fully what I am doing - i dont!!
Any advice or pointers given would be greatly appreciated.
thanks
Jeff
Jeff/Andrew,
this is a MS SQL Server Replication newsgroup - surely there are dedicated
MySQL discussion boards?
Rgds,
Paul Ibison
|||On Sun, 24 Apr 2005 19:07:16 +0100, "Paul Ibison"
<Paul.Ibison@.Pygmalion.Com> wrote:
>Jeff/Andrew,
>this is a MS SQL Server Replication newsgroup - surely there are dedicated
>MySQL discussion boards?
>Rgds,
>Paul Ibison
>
I can't find one and I suspect I will end up installing SQL for
replication - can someone please advise?
|||Have a look at http://forums.mysql.com/list.php?26
From the point of view of SQL Server Replication, you can certainly achieve
your aim. For the new client you need to consider latency (time between
change on the publisher and corresponding change arriving at the subscriber)
, autonomy (can they be offline) and if the subscriber is read-only or
read-write. Answering these will lead to the correct type of replication.
Having SQL Server on the webserver would mean this is the publisher.
Heterogenous subscribers are supported to differing extents, but
connectivity to MYSQL is possible and is illustrated in Hilary's book below.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||while I'd love you to buy my book
1) its covered on the free downloadable sample chapter
http://www.nwsu.com/lowres_replication_ch02.pdf
2) Replication to MySQL doesn't work - or works until the distribution agent
stops and then you have to resync to get it working again due to a SQL
Server bug.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23CtbxJQSFHA.2748@.TK2MSFTNGP09.phx.gbl...
> Have a look at http://forums.mysql.com/list.php?26
> From the point of view of SQL Server Replication, you can certainly
> achieve your aim. For the new client you need to consider latency (time
> between change on the publisher and corresponding change arriving at the
> subscriber) , autonomy (can they be offline) and if the subscriber is
> read-only or read-write. Answering these will lead to the correct type of
> replication. Having SQL Server on the webserver would mean this is the
> publisher. Heterogenous subscribers are supported to differing extents,
> but connectivity to MYSQL is possible and is illustrated in Hilary's book
> below.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Interesting - thanks for the clarification. In that case your (Andrew's)
client might want to consider MSDE as a replacement for a MySQL subscriber.
Rgds,
Paul Ibison
Friday, February 17, 2012
Compatilbilies issues with windows server 2003
I was wondering if anyone has issues installing SQL Server 2000 on Windows
2003 server?
If you have could you please let me know thanks.
The only issue is with installing SQL 2000 on a Windows 2003 cluster using
named instances. That procedure is fully documented in the Knowledge Base.
I strongly recommend Windows 2003 as a host OS for SQL 2000. If you are
upgrading an existing installation, make sure your SQL Server is at or above
Service Pack 3a.
If this is a new installation, you will get a warning about required the
service pack level for SQL 2000. Continue the installation and then
immediately apply SP3a or higher (SP4 is currently the highest level service
pack).
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Ryan" <Ryan@.discussions.microsoft.com> wrote in message
news:553F3C8C-D5CF-476C-8E02-97C3C10638B8@.microsoft.com...
>I was wondering if anyone has issues installing SQL Server 2000 on Windows
> 2003 server?
> If you have could you please let me know thanks.
2003 server?
If you have could you please let me know thanks.
The only issue is with installing SQL 2000 on a Windows 2003 cluster using
named instances. That procedure is fully documented in the Knowledge Base.
I strongly recommend Windows 2003 as a host OS for SQL 2000. If you are
upgrading an existing installation, make sure your SQL Server is at or above
Service Pack 3a.
If this is a new installation, you will get a warning about required the
service pack level for SQL 2000. Continue the installation and then
immediately apply SP3a or higher (SP4 is currently the highest level service
pack).
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Ryan" <Ryan@.discussions.microsoft.com> wrote in message
news:553F3C8C-D5CF-476C-8E02-97C3C10638B8@.microsoft.com...
>I was wondering if anyone has issues installing SQL Server 2000 on Windows
> 2003 server?
> If you have could you please let me know thanks.
Compatilbilies issues with windows server 2003
I was wondering if anyone has issues installing SQL Server 2000 on Windows
2003 server?
If you have could you please let me know thanks.The only issue is with installing SQL 2000 on a Windows 2003 cluster using
named instances. That procedure is fully documented in the Knowledge Base.
I strongly recommend Windows 2003 as a host OS for SQL 2000. If you are
upgrading an existing installation, make sure your SQL Server is at or above
Service Pack 3a.
If this is a new installation, you will get a warning about required the
service pack level for SQL 2000. Continue the installation and then
immediately apply SP3a or higher (SP4 is currently the highest level service
pack).
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Ryan" <Ryan@.discussions.microsoft.com> wrote in message
news:553F3C8C-D5CF-476C-8E02-97C3C10638B8@.microsoft.com...
>I was wondering if anyone has issues installing SQL Server 2000 on Windows
> 2003 server?
> If you have could you please let me know thanks.
2003 server?
If you have could you please let me know thanks.The only issue is with installing SQL 2000 on a Windows 2003 cluster using
named instances. That procedure is fully documented in the Knowledge Base.
I strongly recommend Windows 2003 as a host OS for SQL 2000. If you are
upgrading an existing installation, make sure your SQL Server is at or above
Service Pack 3a.
If this is a new installation, you will get a warning about required the
service pack level for SQL 2000. Continue the installation and then
immediately apply SP3a or higher (SP4 is currently the highest level service
pack).
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Ryan" <Ryan@.discussions.microsoft.com> wrote in message
news:553F3C8C-D5CF-476C-8E02-97C3C10638B8@.microsoft.com...
>I was wondering if anyone has issues installing SQL Server 2000 on Windows
> 2003 server?
> If you have could you please let me know thanks.
Subscribe to:
Posts (Atom)