Showing posts with label runs. Show all posts
Showing posts with label runs. Show all posts

Wednesday, March 7, 2012

Distruibuted Reports showing old machine name in the url.

I have a machine with Sql Server 2005 running the Reporting Services. The
server runs both the front-end and back-end.
I change the machine name after installation of Sql Server 2005 and the
Reporting Services.
I subscribed to a report, but the report is delivered to me with the old
machine name in the url.
E.g.
http://ewisql4/reportserver?%2fUNAUTHORIZED+JOB+CREATION+MONITORING%2fUNAUTHORIZED+JOB+CREATION+ORS&rs%3aParameterLanguage=en-US
But it should be:
http://ewisql3/reportserver?%2fUNAUTHORIZED+JOB+CREATION+MONITORING%2fUNAUTHORIZED+JOB+CREATION+ORS&rs%3aParameterLanguage=en-US
What can do to resolve this? Thanks in advanceHi,
Try to change the SSRS box name in the %Program Files%\Microsoft SQL
Server\MSSQL.3\Reporting Services\ReportServer\ folder,
rsreportserver.config file.
Change the value of the <UrlRoot>http://ewisql4/reportserver</UrlRoot> to
<UrlRoot>http://ewisql3/reportserver</UrlRoot> or whatever the new server
name.
Restart the SSRS service, then try to render the report again.
I hope it will help for you.
Regards,
Janos
"yardi4life" <yardi4life.nospam@.discussions.microsoft.com> wrote in message
news:6C3C9E0C-0F36-4DDD-BB2F-F960FED4299F@.microsoft.com...
>I have a machine with Sql Server 2005 running the Reporting Services. The
> server runs both the front-end and back-end.
> I change the machine name after installation of Sql Server 2005 and the
> Reporting Services.
> I subscribed to a report, but the report is delivered to me with the old
> machine name in the url.
> E.g.
> http://ewisql4/reportserver?%2fUNAUTHORIZED+JOB+CREATION+MONITORING%2fUNAUTHORIZED+JOB+CREATION+ORS&rs%3aParameterLanguage=en-US
> But it should be:
> http://ewisql3/reportserver?%2fUNAUTHORIZED+JOB+CREATION+MONITORING%2fUNAUTHORIZED+JOB+CREATION+ORS&rs%3aParameterLanguage=en-US
> What can do to resolve this? Thanks in advance
>
>

Saturday, February 25, 2012

Distribution Problem

I have a crystal reports porject that runs great on my computer, but when I put it on another computer, it has an unhandled exception. It won't run on any computer that doesn't have visual studio installed. What do I do to fix this?You have to search for a list of the dlls that need to be installed. CR 8.5 came with a file called runtime.hlp. If you can't find that file, try Crystal's website:
http://support.businessobjects.com/search/advsearch.asp

Distribution of MSDE to 5,000 end users - good idea or bad?

Our company has an application that we distribute to our agents for generating sales quotes and it currently runs against an Access database. There is some interest in changing to MSDE and we're just trying to solicit some feedback from people that either investigated this or have tried it.

Here is our application and end user profile:

The application is a relatively small VB application that is distributed to about 5,000 agents. The data is stored in two separate physical database files (with many tables in each). One database stores the user-created data like prospects and configured options, and the other database stores the configuration options and rating data. The configuration option and rating data changes quarterly which is handled today through a new download of the software which overwrites the Access database that contains just that data. The agents are independent and sell for many companies, not just ours, and they own and use their own computer equipment. I would say they are probably at or below average for technical experience for end users. The proposal is to convert the application to run against an MSDE database and to include and install a copy of MSDE as part of the application installation. We would probably distribute service packs along with the quarterly updates, but agents do not always install the updates or could stop selling for us at any time, so there is no guarantee that the updates will ever be applied.

Dramatic overhauls of the application are not being considered at this time, and the users frequently do quotes while on-site with clients and they do not always have access to the Internet. In effect, while a web-based model may seem ideal, we would definitely lose sales if the agents are not able to quote with an off-line source of data and application, and the project is only evaluating whether or not it is a good idea to convert the database from Access to MSDE.

Thanks in advance for your comments!
ChrisYou've already pointed out the biggest issues. Service pack updates are a must. Beyond that, I would think this kind of situation lends itself to Access. I would think unless you plan on upgrading all of these machines to .NET, that it would be best to stick with the most distributable option of Access and the VB App.|||Should you decide to move this to .NET then an option might also be to just use XML for your data storage. If the amount of data is not very large, then Access or MSDE might actually be overkill. Deployment of XML based data is pretty straightforward too.

Distribution job failed

When the distribution agent runs trying to apply the snapshot at the subscriber I get the following error 20253 sql 2005

End of file reached , terminator missing or field data incomplete in SQL 2005

Consult the BOL for more information on the bcp utility and its supported options.

To obtain an error file with details on the errors encountered when initializing the subscribing table, execute the bcp command that appears below.
Consult the BOL for more information on the bcp utility and its supported options.

It could be that the snapshot files for one of your articles is corrupted. Try manually deleting the snapshot files from the snapshot folder and start over - regenerate the snapshot and try to apply it.

If it still fails, you need to tell us what's different about the article that's failing: what kinds of datatypes are in the table, did you manually edit any of the bcp files, what kind of subscriber is this, is this oracle publisher, etc.

|||

Hi,

Did you ever get this issue sorted?

I am receiving the same error message on 1 table during the snapshot sync phase on SQL2005 and it is failing the sync.

Cheers

Distribution job failed

When the distribution agent runs trying to apply the snapshot at the subscriber I get the following error 20253 sql 2005

End of file reached , terminator missing or field data incomplete in SQL 2005

Consult the BOL for more information on the bcp utility and its supported options.

To obtain an error file with details on the errors encountered when initializing the subscribing table, execute the bcp command that appears below.
Consult the BOL for more information on the bcp utility and its supported options.

It could be that the snapshot files for one of your articles is corrupted. Try manually deleting the snapshot files from the snapshot folder and start over - regenerate the snapshot and try to apply it.

If it still fails, you need to tell us what's different about the article that's failing: what kinds of datatypes are in the table, did you manually edit any of the bcp files, what kind of subscriber is this, is this oracle publisher, etc.

|||

Hi,

Did you ever get this issue sorted?

I am receiving the same error message on 1 table during the snapshot sync phase on SQL2005 and it is failing the sync.

Cheers

distribution database having problems??

Something is wrong with my distribtion database. When the distribution clean
up agent runs (or I run dbo.sp_MSdistribution_cleanup manually)
I get the following error message:
Executed as user: sa. Table error: Database ID 9, object ID 5575058, index
ID 1. Chain linkage mismatch. (1:89299)->next = (1:59339), but
(1:59339)->prev = (0:0). [SQLSTATE HY000] (Error 8908). The step failed.
SO then I run
DBCC CHECKDB
on the distribution database. The MSrepl_commands is the table with the
problem with repeated messages such as:
Table error: Object ID 5575058, index ID 1. B-tree page (1:91019) has two
parent nodes (1:93624), slot 103 and (1:89299), slot 1.
I run this:
dbcc checktable ('MSrepl_commands')
and get the same type of error message.
I have no idea how to fix this. Any advise?? (If I try and use the repair
options of the dbcc commands than it says I have to have the DB in single
user mode. Not sure if you are even suppose to do that with a distribution
db?)
Thanks so much for any and all help,
Kristy
Believe it or not these problems crop up from time to time on replicated
databases. Stop the sql server agent on the publisher, yank the network
cable (if possible), and put this database in single user mode and do the
repair.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kristy" <pleasereplyby@.posting.com> wrote in message
news:OCFMw7kPGHA.1696@.TK2MSFTNGP14.phx.gbl...
> Something is wrong with my distribtion database. When the distribution
> clean
> up agent runs (or I run dbo.sp_MSdistribution_cleanup manually)
> I get the following error message:
> Executed as user: sa. Table error: Database ID 9, object ID 5575058, index
> ID 1. Chain linkage mismatch. (1:89299)->next = (1:59339), but
> (1:59339)->prev = (0:0). [SQLSTATE HY000] (Error 8908). The step failed.
> SO then I run
> DBCC CHECKDB
> on the distribution database. The MSrepl_commands is the table with the
> problem with repeated messages such as:
> Table error: Object ID 5575058, index ID 1. B-tree page (1:91019) has two
> parent nodes (1:93624), slot 103 and (1:89299), slot 1.
> I run this:
> dbcc checktable ('MSrepl_commands')
> and get the same type of error message.
> I have no idea how to fix this. Any advise?? (If I try and use the
> repair
> options of the dbcc commands than it says I have to have the DB in single
> user mode. Not sure if you are even suppose to do that with a distribution
> db?)
> Thanks so much for any and all help,
> Kristy
>
>
|||Thanks Hilary. I will check to see if we can yank the network cable. Not
sure if we can though because it is on a remote server hosted by another
company in another state.
If not, is there something else I can do? (Besides redo replication and drop
the distribution DB.)
As always, thanks!
--Kristy
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eODseSmPGHA.5516@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Believe it or not these problems crop up from time to time on replicated
> databases. Stop the sql server agent on the publisher, yank the network
> cable (if possible), and put this database in single user mode and do the
> repair.
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kristy" <pleasereplyby@.posting.com> wrote in message
> news:OCFMw7kPGHA.1696@.TK2MSFTNGP14.phx.gbl...
index[vbcol=seagreen]
failed.[vbcol=seagreen]
two[vbcol=seagreen]
single[vbcol=seagreen]
distribution
>

Distribution Cleanup Job Fails

The distribution cleanup job that runs for our transactional replication on
sql server 2005 fails.
The job is:
EXEC dbo.sp_MSdistribution_cleanup @.min_distretention = 0,
@.max_distretention = 72
The Error is:
Msg 20015, Level 16, State 1, Procedure sp_MSreplremoveuncdir, Line 83
Could not remove directory
'\\sprs76\rysrepldata\unc\SPRS76_RYS_RYS_OPERATION ALTOREPLICAHIST\20060713140760\'.
Check the security context of xp_cmdshell and close other processes that may
be accessing the directory.
Replication-@.rowcount_only parameter must be the value 0,1, or 2. 0=7.0
compatible checksum. 1=only check rowcou: agent
RYSSprs76_distribution@.rowcount_only parameter must be the value 0,1, or 2.
0=7.0 compatible checksu scheduled for retry. Could not clean up the
distribution transaction tables.
If I remove this directory manually, would it cause the replication to
fail? I have tried this on a Test server and it seems that the replication
fails.
I tried to run this job in the Query window and it return this same error.
Our data file is growing and I cannot shrink it because of this issue.
What can i do to resolve this?
Thanks,
George Gopie
There's an MMC snapin to look at shared folders and their connections and
open files. This snapin could be used to drop the connections where needed.
If you have the folder open yourself locally, this snapin won't pick it up,
so you'd have to use the task manager to see what is likely to be accessing
it.
Another possibility is to drop the folder yourself then recreate it for the
distribution agent to later delete.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||No it would not cause replication to fail, only remove this portion
20060713140760
Make sure that xp_cmdshell is enabled and the SQL Serer agent account has
rights to list files and folders and delete files on the root of the
repldata directory and it subdirectories.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"georgeg" <ggg@.hotamil.com> wrote in message
news:DFE68859-01CF-4236-AC2A-F9CA596B9482@.microsoft.com...
> The distribution cleanup job that runs for our transactional replication
> on
> sql server 2005 fails.
> The job is:
> EXEC dbo.sp_MSdistribution_cleanup @.min_distretention = 0,
> @.max_distretention = 72
> The Error is:
> Msg 20015, Level 16, State 1, Procedure sp_MSreplremoveuncdir, Line 83
> Could not remove directory
> '\\sprs76\rysrepldata\unc\SPRS76_RYS_RYS_OPERATION ALTOREPLICAHIST\20060713140760\'.
> Check the security context of xp_cmdshell and close other processes that
> may
> be accessing the directory.
> Replication-@.rowcount_only parameter must be the value 0,1, or 2. 0=7.0
> compatible checksum. 1=only check rowcou: agent
> RYSSprs76_distribution@.rowcount_only parameter must be the value 0,1, or
> 2.
> 0=7.0 compatible checksu scheduled for retry. Could not clean up the
> distribution transaction tables.
>
> If I remove this directory manually, would it cause the replication to
> fail? I have tried this on a Test server and it seems that the replication
> fails.
> I tried to run this job in the Query window and it return this same error.
> Our data file is growing and I cannot shrink it because of this issue.
> What can i do to resolve this?
> Thanks,
> --
> George Gopie
>

Friday, February 17, 2012

distributed transaction error from CLR Trigger

I have a stored procedure in SQL2005 that queries and updates a linked oracle server. The sp runs fine from Management Studio, but when called by a CLR trigger I get the following error message:

Command attempted:

if @.@.trancount > 0 rollback tran
(Transaction sequence number: 0x000000000000000032DD00000000, Command ID: 1)

Error messages:

The operation could not be performed because OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLE_LINK" was unable to begin a distributed transaction. (Source: MSSQLServer, Error number: 7391)
Get help: http://help/7391

The operation could not be performed because OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLE_LINK" was unable to begin a distributed transaction. (Source: MSSQLServer, Error number: 7391)
Get help: http://help/7391

A .NET Framework error occurred during execution of user defined routine or aggregate 'PriorityTrigger':
System.Data.SqlClient.SqlException: The operation could not be performed because OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLE_LINK" was unable to begin a distributed transaction.
Changed database context to 'pims'.
OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLE_LINK" returned message "New transaction cannot enlist in the specified transaction coordinator. ".
System.Data.S (Source: MSSQLServer, Error number: 6549)
Get help: http://help/6549

Any thoughts or direction appreciated

Richard

Hi!

You may try to play with settings of OraOLEDB (DistribTX).

|||The procedure will probably fail the same way when run from a standard TSQL trigger. DTC is pulled in when you run the update within an existing local transaction. There should be an option for your linked server that will disable automatic enlistment if you don't need the transaction distributed to the remote machine. Otherwise you'll have to play with the Oledb provider & DTC setup to get distributed transactions working between the two.|||
--
HOW TO CONFIGURE DISTIBUTED TRANSACTION COORDINATION
--

First verify the "Distribute Transaction Coordinator" Service is
running on both database server computer and client computers
1. Go to "Administrative Tools > Services"
2. Turn on the "Distribute Transaction Coordinator" Service if it is not running

If it is running and client application is not on the same computer as
the database server, on the computer running database server
1. Go to "Administrative Tools > Component Services"
2. On the left navigation tree, go to "Component Services > Computers
> My Computer" (you may need to double click and wait as some nodes
need time to expand)
3. Right click on "My Computer", select "Properties"
4. Select "MSDTC" tab
5. Click "Security Configuration"
6. Make sure you check "Network DTC Access", "Allow Remote Client",
"Allow Inbound/Outbound", "Enable TIP" (Some option may not be
necessary, have a try to get your configuration)
7. The service will restart
8. BUT YOU MAY NEED TO REBOOT YOUR SERVER IF IT STILL DOESN'T WORK
(This is the thing drove me crazy before)

On your client computer use the same above procedure to open the
"Security Configuration" setting, make sure you check "Network DTC
Access", "Allow Inbound/Outbound" option, restart service and computer
if necessary.

On you SQL server service manager, click "Service" dropdown, select
"Distribute Transaction Coordinator", it should be also running on
your server computer.

distributed transaction error from CLR Trigger

I have a stored procedure in SQL2005 that queries and updates a linked oracle server. The sp runs fine from Management Studio, but when called by a CLR trigger I get the following error message:

Command attempted:

if @.@.trancount > 0 rollback tran
(Transaction sequence number: 0x000000000000000032DD00000000, Command ID: 1)

Error messages:

The operation could not be performed because OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLE_LINK" was unable to begin a distributed transaction. (Source: MSSQLServer, Error number: 7391)
Get help: http://help/7391

The operation could not be performed because OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLE_LINK" was unable to begin a distributed transaction. (Source: MSSQLServer, Error number: 7391)
Get help: http://help/7391

A .NET Framework error occurred during execution of user defined routine or aggregate 'PriorityTrigger':
System.Data.SqlClient.SqlException: The operation could not be performed because OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLE_LINK" was unable to begin a distributed transaction.
Changed database context to 'pims'.
OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLE_LINK" returned message "New transaction cannot enlist in the specified transaction coordinator. ".
System.Data.S (Source: MSSQLServer, Error number: 6549)
Get help: http://help/6549

Any thoughts or direction appreciated

Richard

Hi!

You may try to play with settings of OraOLEDB (DistribTX).

|||The procedure will probably fail the same way when run from a standard TSQL trigger. DTC is pulled in when you run the update within an existing local transaction. There should be an option for your linked server that will disable automatic enlistment if you don't need the transaction distributed to the remote machine. Otherwise you'll have to play with the Oledb provider & DTC setup to get distributed transactions working between the two.|||
--
HOW TO CONFIGURE DISTIBUTED TRANSACTION COORDINATION
--

First verify the "Distribute Transaction Coordinator" Service is
running on both database server computer and client computers
1. Go to "Administrative Tools > Services"
2. Turn on the "Distribute Transaction Coordinator" Service if it is not running

If it is running and client application is not on the same computer as
the database server, on the computer running database server
1. Go to "Administrative Tools > Component Services"
2. On the left navigation tree, go to "Component Services > Computers
> My Computer" (you may need to double click and wait as some nodes
need time to expand)
3. Right click on "My Computer", select "Properties"
4. Select "MSDTC" tab
5. Click "Security Configuration"
6. Make sure you check "Network DTC Access", "Allow Remote Client",
"Allow Inbound/Outbound", "Enable TIP" (Some option may not be
necessary, have a try to get your configuration)
7. The service will restart
8. BUT YOU MAY NEED TO REBOOT YOUR SERVER IF IT STILL DOESN'T WORK
(This is the thing drove me crazy before)

On your client computer use the same above procedure to open the
"Security Configuration" setting, make sure you check "Network DTC
Access", "Allow Inbound/Outbound" option, restart service and computer
if necessary.

On you SQL server service manager, click "Service" dropdown, select
"Distribute Transaction Coordinator", it should be also running on
your server computer.

Tuesday, February 14, 2012

distributed transaction

does the following error causes any problem to activate distributed
transaction.
My sp which runs on XXXXXX pushes data from XXXXXX to YYYYY. With the BEGIN
TRAN enabled the Sp hangs. it works fine when i comment the begin/ commit
trans. it take only 5 sec to execute.
Both XXXXXX and YYYYY runs on VMWare virtual machine
Event Type:Error
Event Source:NETLOGON
Event Category:None
Event ID:5516
Date:23/10/2006
Time:15:50:48
User:N/A
Computer:XXXXXX
Description:
The computer or domain XXXXXX trusts domain YYYYY. (This may be an indirect
trust.) However, XXXXXX and YYYYY have the same machine security identifier
(SID). NT should be re-installed on either XXXXXX or YYYYY.
Data:
0000: 01 04 00 00 00 00 00 05 ......
0008: 15 00 00 00 8a 5a 41 60 ...?ZA`
0010: 93 e3 62 48 43 17 0a 32 ??bHC..2
thanks
Just a guess: Are the operating systems derived from the same installation? If so, perhaps the DTC
services has the same GUID... You could try the last step of
http://www.karaszi.com/SQLServer/inf...rver_name.asp, just make sure you have backup etc
first.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"vinu thomas" <vinuthomas@.discussions.microsoft.com> wrote in message
news:7D24D271-D90F-495B-9AC8-8821B8A01E9A@.microsoft.com...
> does the following error causes any problem to activate distributed
> transaction.
> My sp which runs on XXXXXX pushes data from XXXXXX to YYYYY. With the BEGIN
> TRAN enabled the Sp hangs. it works fine when i comment the begin/ commit
> trans. it take only 5 sec to execute.
> Both XXXXXX and YYYYY runs on VMWare virtual machine
> Event Type: Error
> Event Source: NETLOGON
> Event Category: None
> Event ID: 5516
> Date: 23/10/2006
> Time: 15:50:48
> User: N/A
> Computer: XXXXXX
> Description:
> The computer or domain XXXXXX trusts domain YYYYY. (This may be an indirect
> trust.) However, XXXXXX and YYYYY have the same machine security identifier
> (SID). NT should be re-installed on either XXXXXX or YYYYY.
> Data:
> 0000: 01 04 00 00 00 00 00 05 ......
> 0008: 15 00 00 00 8a 5a 41 60 ...?ZA`
> 0010: 93 e3 62 48 43 17 0a 32 ??bHC..2
> thanks
>

distributed transaction

does the following error causes any problem to activate distributed
transaction.
My sp which runs on XXXXXX pushes data from XXXXXX to YYYYY. With the BEGIN
TRAN enabled the Sp hangs. it works fine when i comment the begin/ commit
trans. it take only 5 sec to execute.
Both XXXXXX and YYYYY runs on VMWare virtual machine
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5516
Date: 23/10/2006
Time: 15:50:48
User: N/A
Computer: XXXXXX
Description:
The computer or domain XXXXXX trusts domain YYYYY. (This may be an indirect
trust.) However, XXXXXX and YYYYY have the same machine security identifie
r
(SID). NT should be re-installed on either XXXXXX or YYYYY.
Data:
0000: 01 04 00 00 00 00 00 05 ......
0008: 15 00 00 00 8a 5a 41 60 ...?ZA`
0010: 93 e3 62 48 43 17 0a 32 ??bHC..2
thanksJust a guess: Are the operating systems derived from the same installation?
If so, perhaps the DTC
services has the same GUID... You could try the last step of
http://www.karaszi.com/SQLServer/in...erver_name.asp, just make sure
you have backup etc
first.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"vinu thomas" <vinuthomas@.discussions.microsoft.com> wrote in message
news:7D24D271-D90F-495B-9AC8-8821B8A01E9A@.microsoft.com...
> does the following error causes any problem to activate distributed
> transaction.
> My sp which runs on XXXXXX pushes data from XXXXXX to YYYYY. With the BEGI
N
> TRAN enabled the Sp hangs. it works fine when i comment the begin/ commit
> trans. it take only 5 sec to execute.
> Both XXXXXX and YYYYY runs on VMWare virtual machine
> Event Type: Error
> Event Source: NETLOGON
> Event Category: None
> Event ID: 5516
> Date: 23/10/2006
> Time: 15:50:48
> User: N/A
> Computer: XXXXXX
> Description:
> The computer or domain XXXXXX trusts domain YYYYY. (This may be an indire
ct
> trust.) However, XXXXXX and YYYYY have the same machine security identif
ier
> (SID). NT should be re-installed on either XXXXXX or YYYYY.
> Data:
> 0000: 01 04 00 00 00 00 00 05 ......
> 0008: 15 00 00 00 8a 5a 41 60 ...?ZA`
> 0010: 93 e3 62 48 43 17 0a 32 ??bHC..2
> thanks
>

distributed transaction

does the following error causes any problem to activate distributed
transaction.
My sp which runs on XXXXXX pushes data from XXXXXX to YYYYY. With the BEGIN
TRAN enabled the Sp hangs. it works fine when i comment the begin/ commit
trans. it take only 5 sec to execute.
Both XXXXXX and YYYYY runs on VMWare virtual machine
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5516
Date: 23/10/2006
Time: 15:50:48
User: N/A
Computer: XXXXXX
Description:
The computer or domain XXXXXX trusts domain YYYYY. (This may be an indirect
trust.) However, XXXXXX and YYYYY have the same machine security identifier
(SID). NT should be re-installed on either XXXXXX or YYYYY.
Data:
0000: 01 04 00 00 00 00 00 05 ......
0008: 15 00 00 00 8a 5a 41 60 ...Â?ZA`
0010: 93 e3 62 48 43 17 0a 32 �ãbHC..2
thanksJust a guess: Are the operating systems derived from the same installation? If so, perhaps the DTC
services has the same GUID... You could try the last step of
http://www.karaszi.com/SQLServer/info_change_server_name.asp, just make sure you have backup etc
first.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"vinu thomas" <vinuthomas@.discussions.microsoft.com> wrote in message
news:7D24D271-D90F-495B-9AC8-8821B8A01E9A@.microsoft.com...
> does the following error causes any problem to activate distributed
> transaction.
> My sp which runs on XXXXXX pushes data from XXXXXX to YYYYY. With the BEGIN
> TRAN enabled the Sp hangs. it works fine when i comment the begin/ commit
> trans. it take only 5 sec to execute.
> Both XXXXXX and YYYYY runs on VMWare virtual machine
> Event Type: Error
> Event Source: NETLOGON
> Event Category: None
> Event ID: 5516
> Date: 23/10/2006
> Time: 15:50:48
> User: N/A
> Computer: XXXXXX
> Description:
> The computer or domain XXXXXX trusts domain YYYYY. (This may be an indirect
> trust.) However, XXXXXX and YYYYY have the same machine security identifier
> (SID). NT should be re-installed on either XXXXXX or YYYYY.
> Data:
> 0000: 01 04 00 00 00 00 00 05 ......
> 0008: 15 00 00 00 8a 5a 41 60 ...Â?ZA`
> 0010: 93 e3 62 48 43 17 0a 32 �ãbHC..2
> thanks
>

distributed query runs indefinitely

Matt,
I never tire of queries I'm just very pressed for time
at the moment as we're in the middle of moving our
servers to a hosted environment and I'm managing the
database side of things. If possible, I'll take a look
late this afternoon (UK time) if nobody else has replied.
Rgds,
Paul Ibison (SQL Server MVP)
Paul,
Thanx, I greatly appreciate any time you can set aside whenever it is
Hope your transition goes smoothly,
Matt
|||Matt,
please try this type of approach:
CREATE TRIGGER ti_tst ON [dbo].[tst]
FOR INSERT
AS
set xact_abort on
insert into [dhsrvskh504\stst].dba_admin.dbo.tst (name)
select name from inserted
This works fine for me - hopefully for you as well.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Matt,
if you still have problems, please look at these
troubleshooting guides:
http://www.kbalertz.com/Feedback.aspx?kbNumber=250367
http://support.microsoft.com/kb/306212
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
I greatly appreciate all help that you have provided. It appears that what
you have telling me the whole time was correct. After much looking,
searching, and cussing I found that it was a problem with windows 2003 and
the way it handles RPC requests. For any other here is a link to article to
work around.
http://support.microsoft.com/?kbid=555017
Once again thank you for all your help through this.
Matt