We have a scenario that will require us to maintain a central system that
will be taking in data from 15 other locations around the state. I'm
interested in creating a situation that will allow the individual locations
the ability to have a local copy of their data, but only their data. We want
changes made to the central repository to be pushed back down the the
appropriate location. It there a way or doing this through some kind of SQL
Server transaction synchronization? Could we have each locations data use
SQL Server log/transaction shipping synchronizing into individual databases
at the central site and then have some process that would just merge each of
these databases into a single large database? Is this more of a headache to
try to create and maintain? Any ideas or suggestions would be great. The
main idea here is that each location is a separate entity collecting their
own data - we are acting as a repository for all the locations and want to
be able to do research analysis on the data as a whole. As I said, any ideas
or suggestions would be welcome! Thanks!
>
> We have a scenario that will require us to maintain a central system
that
> will be taking in data from 15 other locations around the state. I'm
> interested in creating a situation that will allow the individual
locations
> the ability to have a local copy of their data, but only their data. We
want
> changes made to the central repository to be pushed back down the the
> appropriate location. It there a way or doing this through some kind of
SQL
> Server transaction synchronization? Could we have each locations data use
> SQL Server log/transaction shipping synchronizing into individual
databases
> at the central site and then have some process that would just merge each
of
> these databases into a single large database? Is this more of a headache
to
> try to create and maintain? Any ideas or suggestions would be great. The
> main idea here is that each location is a separate entity collecting
their
> own data - we are acting as a repository for all the locations and want
to
> be able to do research analysis on the data as a whole. As I said, any
ideas
> or suggestions would be welcome! Thanks!
It looks your requirement conforms to the multiple publishers and central
subscriber physical model. For more info, please consult SQL Server Books
Online.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label scenario. Show all posts
Showing posts with label scenario. Show all posts
Wednesday, March 28, 2012
Monday, March 26, 2012
Multi location data syncronization
We have a scenario that will require us to maintain a central system that
will be taking in data from 15 other locations around the state. I'm
interested in creating a situation that will allow the individual locations
the ability to have a local copy of their data, but only their data. We want
changes made to the central repository to be pushed back down the the
appropriate location. It there a way or doing this through some kind of SQL
Server transaction synchronization? Could we have each locations data use
SQL Server log/transaction shipping synchronizing into individual databases
at the central site and then have some process that would just merge each of
these databases into a single large database? Is this more of a headache to
try to create and maintain? Any ideas or suggestions would be great. The
main idea here is that each location is a separate entity collecting their
own data - we are acting as a repository for all the locations and want to
be able to do research analysis on the data as a whole. As I said, any ideas
or suggestions would be welcome! Thanks!>
> We have a scenario that will require us to maintain a central system
that
> will be taking in data from 15 other locations around the state. I'm
> interested in creating a situation that will allow the individual
locations
> the ability to have a local copy of their data, but only their data. We
want
> changes made to the central repository to be pushed back down the the
> appropriate location. It there a way or doing this through some kind of
SQL
> Server transaction synchronization? Could we have each locations data use
> SQL Server log/transaction shipping synchronizing into individual
databases
> at the central site and then have some process that would just merge each
of
> these databases into a single large database? Is this more of a headache
to
> try to create and maintain? Any ideas or suggestions would be great. The
> main idea here is that each location is a separate entity collecting
their
> own data - we are acting as a repository for all the locations and want
to
> be able to do research analysis on the data as a whole. As I said, any
ideas
> or suggestions would be welcome! Thanks!
--
It looks your requirement conforms to the multiple publishers and central
subscriber physical model. For more info, please consult SQL Server Books
Online.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
will be taking in data from 15 other locations around the state. I'm
interested in creating a situation that will allow the individual locations
the ability to have a local copy of their data, but only their data. We want
changes made to the central repository to be pushed back down the the
appropriate location. It there a way or doing this through some kind of SQL
Server transaction synchronization? Could we have each locations data use
SQL Server log/transaction shipping synchronizing into individual databases
at the central site and then have some process that would just merge each of
these databases into a single large database? Is this more of a headache to
try to create and maintain? Any ideas or suggestions would be great. The
main idea here is that each location is a separate entity collecting their
own data - we are acting as a repository for all the locations and want to
be able to do research analysis on the data as a whole. As I said, any ideas
or suggestions would be welcome! Thanks!>
> We have a scenario that will require us to maintain a central system
that
> will be taking in data from 15 other locations around the state. I'm
> interested in creating a situation that will allow the individual
locations
> the ability to have a local copy of their data, but only their data. We
want
> changes made to the central repository to be pushed back down the the
> appropriate location. It there a way or doing this through some kind of
SQL
> Server transaction synchronization? Could we have each locations data use
> SQL Server log/transaction shipping synchronizing into individual
databases
> at the central site and then have some process that would just merge each
of
> these databases into a single large database? Is this more of a headache
to
> try to create and maintain? Any ideas or suggestions would be great. The
> main idea here is that each location is a separate entity collecting
their
> own data - we are acting as a repository for all the locations and want
to
> be able to do research analysis on the data as a whole. As I said, any
ideas
> or suggestions would be welcome! Thanks!
--
It looks your requirement conforms to the multiple publishers and central
subscriber physical model. For more info, please consult SQL Server Books
Online.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Multi location data syncronization
We have a scenario that will require us to maintain a central system that
will be taking in data from 15 other locations around the state. I'm
interested in creating a situation that will allow the individual locations
the ability to have a local copy of their data, but only their data. We want
changes made to the central repository to be pushed back down the the
appropriate location. It there a way or doing this through some kind of SQL
Server transaction synchronization? Could we have each locations data use
SQL Server log/transaction shipping synchronizing into individual databases
at the central site and then have some process that would just merge each of
these databases into a single large database? Is this more of a headache to
try to create and maintain? Any ideas or suggestions would be great. The
main idea here is that each location is a separate entity collecting their
own data - we are acting as a repository for all the locations and want to
be able to do research analysis on the data as a whole. As I said, any ideas
or suggestions would be welcome! Thanks!>
> We have a scenario that will require us to maintain a central system
that
> will be taking in data from 15 other locations around the state. I'm
> interested in creating a situation that will allow the individual
locations
> the ability to have a local copy of their data, but only their data. We
want
> changes made to the central repository to be pushed back down the the
> appropriate location. It there a way or doing this through some kind of
SQL
> Server transaction synchronization? Could we have each locations data use
> SQL Server log/transaction shipping synchronizing into individual
databases
> at the central site and then have some process that would just merge each
of
> these databases into a single large database? Is this more of a headache
to
> try to create and maintain? Any ideas or suggestions would be great. The
> main idea here is that each location is a separate entity collecting
their
> own data - we are acting as a repository for all the locations and want
to
> be able to do research analysis on the data as a whole. As I said, any
ideas
> or suggestions would be welcome! Thanks!
--
It looks your requirement conforms to the multiple publishers and central
subscriber physical model. For more info, please consult SQL Server Books
Online.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
will be taking in data from 15 other locations around the state. I'm
interested in creating a situation that will allow the individual locations
the ability to have a local copy of their data, but only their data. We want
changes made to the central repository to be pushed back down the the
appropriate location. It there a way or doing this through some kind of SQL
Server transaction synchronization? Could we have each locations data use
SQL Server log/transaction shipping synchronizing into individual databases
at the central site and then have some process that would just merge each of
these databases into a single large database? Is this more of a headache to
try to create and maintain? Any ideas or suggestions would be great. The
main idea here is that each location is a separate entity collecting their
own data - we are acting as a repository for all the locations and want to
be able to do research analysis on the data as a whole. As I said, any ideas
or suggestions would be welcome! Thanks!>
> We have a scenario that will require us to maintain a central system
that
> will be taking in data from 15 other locations around the state. I'm
> interested in creating a situation that will allow the individual
locations
> the ability to have a local copy of their data, but only their data. We
want
> changes made to the central repository to be pushed back down the the
> appropriate location. It there a way or doing this through some kind of
SQL
> Server transaction synchronization? Could we have each locations data use
> SQL Server log/transaction shipping synchronizing into individual
databases
> at the central site and then have some process that would just merge each
of
> these databases into a single large database? Is this more of a headache
to
> try to create and maintain? Any ideas or suggestions would be great. The
> main idea here is that each location is a separate entity collecting
their
> own data - we are acting as a repository for all the locations and want
to
> be able to do research analysis on the data as a whole. As I said, any
ideas
> or suggestions would be welcome! Thanks!
--
It looks your requirement conforms to the multiple publishers and central
subscriber physical model. For more info, please consult SQL Server Books
Online.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Multi level document map
Hello,
I am using SRS 2000 and was wondering if there is any way to have more than 1 level in my document map.
Here is the scenario:
I have a report that displays
Customer
Contract 1
Project 1
Project 2
Contract 2
Project 1
Project 2
etc...
I would like the document map to include a list of Customers, Contracts and Projects as some people who view the report know the contract code they are interested in, others know the project code and others know the customers.
However, when I set it up I get a list with them all jumbled together:
Report Name
Customer 1
Project 1
Customer 2
Contract 1
etc...
I would like the document map to have separate levels for each of them:
Report Name
Customer
Customer 1
Customer 2
Contract
Contract 1
Contract 2
Project
Project 1
Project 2
Does anyone know if this is possible?
Thanks,
Paul.
If this isn't possible in SRS 2000 is it possible in SRS 2005 instead?
Cheers.
Paul.
|||It looks like you are using a table group layout.
On the table group for customers, make sure to set the document label expression on the table grouping dialog. You should then get the hierarchical document map as desired.
-- Robert
|||I feel like I am getting closer but further away at the same time....
I have played around with setting up document map lables at the table level, and at the group levels instead of at the field level.
If I set it at the table level, that just gives me 1 more drill down level ie:
Report Name
Table Level Lable
Customer 1
Project 1
Customer 2
etc...
If I set it at the group level I get the following:
Report Name
Customer 1
Contract 1
Project 1
Project 2
Contract 2
Project 1
Customer 2
etc...
I think my problem is that I want a list of Customers, Contracts and Projects that are not related in any way. So that if for example you knew that you wanted to jump to project PA1234 you would not have to go through the Company and Contract levels to get there.
I want:
Report Name
Customers
Customer 1
Customer 2
Contracts
Contract 1
Contract 2
Projects
Project 1
Project 2
I am not sure that I will be able to do this due to the Customers - Contracts - Projects structure.
I'll have another play and see what I can find.
|||In order to have Customers, Contracts, and Projects at the same level, you will need to use multiple tables next to each other. The first table groups by customers, the second by contracts, and so on.
-- Robert
|||I don't know if this would be helpful to you since it was so long ago. But maybe for people who have an issue like this in the future...I wanted to display hierarchical data in the document map as a tree, and I finally stumbled upon a solution, of sorts.
I return the data hierarchically arranged in my result set already (though that may not be necessary, now that I think about it). But reporting services has in the "Details Grouping..." facility for the table, the ability to display data hierarchically for you. At the same time, there is a "Document map label" field just above the "Parent group" field. When I populated that field (in my case, with the Name value) it worked like a charm.
Actually (now that I take a quick last look), I don't know how to pre-expand the tree to my satisfaction, but I guess I can live with that for now...
Wednesday, March 21, 2012
MSTDC and windows domain
Hi,
i have this scenario :
a have web application (NT4) that use a MSTDC service on my application
server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
The service MSTDC on application server and db server start with the same
domain administration account (administrator)
Now i have install a new domain windwos 2003 and a new cluster SQL2000/MSTDC
on 2 windows 2003 server and try to modify my application to point to new
windows 2003 cluster but when i try to test it a error appared :
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction. OLE/DB provider returned
message: New transaction cannot enlist in the specified transaction
coordinator.
and found a kb article and make the modify adding a network service into
MSDTC service on cluster 2003 but the problem is not resoleved! :-(
This is because are 2 different domain and network service on 2003 isn't any
account on NT4 domain ?
If i try to trust a windows 2003 and NT4 domain i resolved it ?
The trust is only one solution or exist other solution ?
Thanks in advance.
make sure you are ussing the cluster version of DTC. On each node you
should have run comclust.exe.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
SQL2000/MSTDC
> on 2 windows 2003 server and try to modify my application to point to new
> windows 2003 cluster but when i try to test it a error appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
any
> account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>
|||Hi,
yes ai use DTC cluster .
But on windows2003 for clustering DTC i don't type comclust but i must
create it manuallty ,
are you sure ?
Thanks.
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:%23C7I0Pp5EHA.2572@.tk2msftngp13.phx.gbl...
> make sure you are ussing the cluster version of DTC. On each node you
> should have run comclust.exe.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> <io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> SQL2000/MSTDC
> 'SQLOLEDB'
> any
>
|||Hi,
i foun a solutiontoi my problem , the solution is :
- Trust 2 way from NT4 and 2K3
- Modify lmhost/host file for all server that are involved (i try for 2
hour first found the the optimal configuration of this file)
I habve used dctping.exe and dctester.exe for troubleshooting
And now work
Other solution instead trust is :
http://support.microsoft.com/default...b;en-us;827805
Thanks !
this is happy day!
:-)
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
> SQL2000/MSTDC on 2 windows 2003 server and try to modify my application to
> point to new windows 2003 cluster but when i try to test it a error
> appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
> any account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>
i have this scenario :
a have web application (NT4) that use a MSTDC service on my application
server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
The service MSTDC on application server and db server start with the same
domain administration account (administrator)
Now i have install a new domain windwos 2003 and a new cluster SQL2000/MSTDC
on 2 windows 2003 server and try to modify my application to point to new
windows 2003 cluster but when i try to test it a error appared :
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction. OLE/DB provider returned
message: New transaction cannot enlist in the specified transaction
coordinator.
and found a kb article and make the modify adding a network service into
MSDTC service on cluster 2003 but the problem is not resoleved! :-(
This is because are 2 different domain and network service on 2003 isn't any
account on NT4 domain ?
If i try to trust a windows 2003 and NT4 domain i resolved it ?
The trust is only one solution or exist other solution ?
Thanks in advance.
make sure you are ussing the cluster version of DTC. On each node you
should have run comclust.exe.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
SQL2000/MSTDC
> on 2 windows 2003 server and try to modify my application to point to new
> windows 2003 cluster but when i try to test it a error appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
any
> account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>
|||Hi,
yes ai use DTC cluster .
But on windows2003 for clustering DTC i don't type comclust but i must
create it manuallty ,
are you sure ?
Thanks.
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:%23C7I0Pp5EHA.2572@.tk2msftngp13.phx.gbl...
> make sure you are ussing the cluster version of DTC. On each node you
> should have run comclust.exe.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> <io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> SQL2000/MSTDC
> 'SQLOLEDB'
> any
>
|||Hi,
i foun a solutiontoi my problem , the solution is :
- Trust 2 way from NT4 and 2K3
- Modify lmhost/host file for all server that are involved (i try for 2
hour first found the the optimal configuration of this file)
I habve used dctping.exe and dctester.exe for troubleshooting
And now work
Other solution instead trust is :
http://support.microsoft.com/default...b;en-us;827805
Thanks !
this is happy day!
:-)
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
> SQL2000/MSTDC on 2 windows 2003 server and try to modify my application to
> point to new windows 2003 cluster but when i try to test it a error
> appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
> any account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>
MSTDC and windows domain
Hi,
i have this scenario :
a have web application (NT4) that use a MSTDC service on my application
server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
The service MSTDC on application server and db server start with the same
domain administration account (administrator)
Now i have install a new domain windwos 2003 and a new cluster SQL2000/MSTDC
on 2 windows 2003 server and try to modify my application to point to new
windows 2003 cluster but when i try to test it a error appared :
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction. OLE/DB provider returned
message: New transaction cannot enlist in the specified transaction
coordinator.
and found a kb article and make the modify adding a network service into
MSDTC service on cluster 2003 but the problem is not resoleved! :-(
This is because are 2 different domain and network service on 2003 isn't any
account on NT4 domain ?
If i try to trust a windows 2003 and NT4 domain i resolved it ?
The trust is only one solution or exist other solution ?
Thanks in advance.make sure you are ussing the cluster version of DTC. On each node you
should have run comclust.exe.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
SQL2000/MSTDC
> on 2 windows 2003 server and try to modify my application to point to new
> windows 2003 cluster but when i try to test it a error appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
any
> account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>|||Hi,
yes ai use DTC cluster .
But on windows2003 for clustering DTC i don't type comclust but i must
create it manuallty ,
are you sure ?
Thanks.
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:%23C7I0Pp5EHA.2572@.tk2msftngp13.phx.gbl...
> make sure you are ussing the cluster version of DTC. On each node you
> should have run comclust.exe.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> <io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
>> Hi,
>> i have this scenario :
>> a have web application (NT4) that use a MSTDC service on my application
>> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
>> The service MSTDC on application server and db server start with the same
>> domain administration account (administrator)
>> Now i have install a new domain windwos 2003 and a new cluster
> SQL2000/MSTDC
>> on 2 windows 2003 server and try to modify my application to point to new
>> windows 2003 cluster but when i try to test it a error appared :
>> Server: Msg 7391, Level 16, State 1, Line 2
>> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
>> was unable to begin a distributed transaction. OLE/DB provider returned
>> message: New transaction cannot enlist in the specified transaction
>> coordinator.
>> and found a kb article and make the modify adding a network service into
>> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
>> This is because are 2 different domain and network service on 2003 isn't
> any
>> account on NT4 domain ?
>> If i try to trust a windows 2003 and NT4 domain i resolved it ?
>> The trust is only one solution or exist other solution ?
>> Thanks in advance.
>>
>|||Hi,
i foun a solutiontoi my problem , the solution is :
- Trust 2 way from NT4 and 2K3
- Modify lmhost/host file for all server that are involved (i try for 2
hour first found the the optimal configuration of this file)
I habve used dctping.exe and dctester.exe for troubleshooting
And now work
Other solution instead trust is :
http://support.microsoft.com/default.aspx?scid=kb;en-us;827805http://support.microsoft.com/default.aspx?scid=kb;en-us;827805
Thanks !
this is happy day!
:-)
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
> SQL2000/MSTDC on 2 windows 2003 server and try to modify my application to
> point to new windows 2003 cluster but when i try to test it a error
> appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
> any account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>
i have this scenario :
a have web application (NT4) that use a MSTDC service on my application
server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
The service MSTDC on application server and db server start with the same
domain administration account (administrator)
Now i have install a new domain windwos 2003 and a new cluster SQL2000/MSTDC
on 2 windows 2003 server and try to modify my application to point to new
windows 2003 cluster but when i try to test it a error appared :
Server: Msg 7391, Level 16, State 1, Line 2
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction. OLE/DB provider returned
message: New transaction cannot enlist in the specified transaction
coordinator.
and found a kb article and make the modify adding a network service into
MSDTC service on cluster 2003 but the problem is not resoleved! :-(
This is because are 2 different domain and network service on 2003 isn't any
account on NT4 domain ?
If i try to trust a windows 2003 and NT4 domain i resolved it ?
The trust is only one solution or exist other solution ?
Thanks in advance.make sure you are ussing the cluster version of DTC. On each node you
should have run comclust.exe.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
SQL2000/MSTDC
> on 2 windows 2003 server and try to modify my application to point to new
> windows 2003 cluster but when i try to test it a error appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
any
> account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>|||Hi,
yes ai use DTC cluster .
But on windows2003 for clustering DTC i don't type comclust but i must
create it manuallty ,
are you sure ?
Thanks.
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:%23C7I0Pp5EHA.2572@.tk2msftngp13.phx.gbl...
> make sure you are ussing the cluster version of DTC. On each node you
> should have run comclust.exe.
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> <io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
>> Hi,
>> i have this scenario :
>> a have web application (NT4) that use a MSTDC service on my application
>> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
>> The service MSTDC on application server and db server start with the same
>> domain administration account (administrator)
>> Now i have install a new domain windwos 2003 and a new cluster
> SQL2000/MSTDC
>> on 2 windows 2003 server and try to modify my application to point to new
>> windows 2003 cluster but when i try to test it a error appared :
>> Server: Msg 7391, Level 16, State 1, Line 2
>> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
>> was unable to begin a distributed transaction. OLE/DB provider returned
>> message: New transaction cannot enlist in the specified transaction
>> coordinator.
>> and found a kb article and make the modify adding a network service into
>> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
>> This is because are 2 different domain and network service on 2003 isn't
> any
>> account on NT4 domain ?
>> If i try to trust a windows 2003 and NT4 domain i resolved it ?
>> The trust is only one solution or exist other solution ?
>> Thanks in advance.
>>
>|||Hi,
i foun a solutiontoi my problem , the solution is :
- Trust 2 way from NT4 and 2K3
- Modify lmhost/host file for all server that are involved (i try for 2
hour first found the the optimal configuration of this file)
I habve used dctping.exe and dctester.exe for troubleshooting
And now work
Other solution instead trust is :
http://support.microsoft.com/default.aspx?scid=kb;en-us;827805http://support.microsoft.com/default.aspx?scid=kb;en-us;827805
Thanks !
this is happy day!
:-)
<io.com> wrote in message news:%23NqzJ1I5EHA.2624@.TK2MSFTNGP11.phx.gbl...
> Hi,
> i have this scenario :
> a have web application (NT4) that use a MSTDC service on my application
> server (NT4) and DB and MSDTC on my cluster windows (2000/SQL2000)
> The service MSTDC on application server and db server start with the same
> domain administration account (administrator)
> Now i have install a new domain windwos 2003 and a new cluster
> SQL2000/MSTDC on 2 windows 2003 server and try to modify my application to
> point to new windows 2003 cluster but when i try to test it a error
> appared :
> Server: Msg 7391, Level 16, State 1, Line 2
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
> was unable to begin a distributed transaction. OLE/DB provider returned
> message: New transaction cannot enlist in the specified transaction
> coordinator.
> and found a kb article and make the modify adding a network service into
> MSDTC service on cluster 2003 but the problem is not resoleved! :-(
> This is because are 2 different domain and network service on 2003 isn't
> any account on NT4 domain ?
> If i try to trust a windows 2003 and NT4 domain i resolved it ?
> The trust is only one solution or exist other solution ?
> Thanks in advance.
>
Subscribe to:
Posts (Atom)