Showing posts with label failed. Show all posts
Showing posts with label failed. Show all posts

Monday, March 19, 2012

DMO SQLServer->Connect failed for user name with special characters

Hi,
If I give a user name or password having special character (mainly
semi-colon) then I cannot connect to the SQL Server. Following is the error:
Login failed for user 'a`~!@.#$%^&*()_+|-=[]'.
TCP Provider: An existing connection was forcibly closed by the
remote host.
Communication link failure
Invalid connection string attribute
However, this error was coming in my Cpp code. I tried with VB, I
works. Also, I got same error from Enterprise Manager.
Is this a defect or known behavior in DMO?
TIA,
AjeyActual user name was a`~!@.#$%^&*()_+|-=[];',./{}:"<>?
"Ajey" <ajey5@.hotmail.com> wrote in message
news:ujnaqXcjFHA.1428@.TK2MSFTNGP10.phx.gbl...
> Hi,
> If I give a user name or password having special character (mainly
> semi-colon) then I cannot connect to the SQL Server. Following is the
> error:
> Login failed for user 'a`~!@.#$%^&*()_+|-=[]'.
> TCP Provider: An existing connection was forcibly closed by the
> remote host.
> Communication link failure
> Invalid connection string attribute
> However, this error was coming in my Cpp code. I tried with VB, I
> works. Also, I got same error from Enterprise Manager.
> Is this a defect or known behavior in DMO?
>
> TIA,
> Ajey
>|||/ is an escape character in cpp, you have to replace / with // in your
string for it to work properly.
hth
--
Vikram Vamshi
Database Engineer
Eclipsys Corporation
"Ajey" <ajey5@.hotmail.com> wrote in message
news:OqwRXccjFHA.3316@.TK2MSFTNGP14.phx.gbl...
> Actual user name was a`~!@.#$%^&*()_+|-=[];',./{}:"<>?
> "Ajey" <ajey5@.hotmail.com> wrote in message
> news:ujnaqXcjFHA.1428@.TK2MSFTNGP10.phx.gbl...
>|||I think it's mainly due to semi-colon. The error message displays the user
names till the character before the semi-colon. Also, same username &
password does not work while registering the sql server using Enterprise
Manager or connecting through Query Analyser.
- Ajey
"Vikram Vamshi" <vikram.vamshi@.online.eclipsys.com> wrote in message
news:uMKZSCkjFHA.3900@.TK2MSFTNGP10.phx.gbl...
>/ is an escape character in cpp, you have to replace / with // in your
>string for it to work properly.
> hth
> --
> Vikram Vamshi
> Database Engineer
> Eclipsys Corporation
> "Ajey" <ajey5@.hotmail.com> wrote in message
> news:OqwRXccjFHA.3316@.TK2MSFTNGP14.phx.gbl...
>|||Can you post your cpp code that can reproduce the issue?
Vikram Vamshi
Database Engineer
Eclipsys Corporation
"Ajey" <ajey5@.hotmail.com> wrote in message
news:uZXxuFojFHA.2644@.TK2MSFTNGP09.phx.gbl...
>I think it's mainly due to semi-colon. The error message displays the user
>names till the character before the semi-colon. Also, same username &
>password does not work while registering the sql server using Enterprise
>Manager or connecting through Query Analyser.
> - Ajey
> "Vikram Vamshi" <vikram.vamshi@.online.eclipsys.com> wrote in message
> news:uMKZSCkjFHA.3900@.TK2MSFTNGP10.phx.gbl...
>|||Also try to put quotes around the user name (try both single quotes and
double quotes, one of them should be able to handle special characters)
hth
Vikram Vamshi
Database Engineer
Eclipsys Corporation
"Ajey" <ajey5@.hotmail.com> wrote in message
news:uZXxuFojFHA.2644@.TK2MSFTNGP09.phx.gbl...
>I think it's mainly due to semi-colon. The error message displays the user
>names till the character before the semi-colon. Also, same username &
>password does not work while registering the sql server using Enterprise
>Manager or connecting through Query Analyser.
> - Ajey
> "Vikram Vamshi" <vikram.vamshi@.online.eclipsys.com> wrote in message
> news:uMKZSCkjFHA.3900@.TK2MSFTNGP10.phx.gbl...
>|||strSQLLoginName = L"abc;xyz"
strSQLLoginPassword = L"abc"
HRESULT hrConnect = spServer->Connect( rkstrCurrentServerName.c_str(),
strSQLLoginName.c_str(), strSQLLoginPassword.c_str() );
This code also gives the same error. Also, if i paste user name as abc;xyz
in Enterprise Manager or Query Analyzer I get the same error.
The same thing works with ADO. I had to just escape the special characters
in the connection string. While can pass the username & password directly to
the ADOConnection->Connect() method. But same is not working on DMO.
Thanks.
- Ajey
"Vikram Vamshi" <vikram.vamshi@.online.eclipsys.com> wrote in message
news:OrYsYoujFHA.3316@.TK2MSFTNGP14.phx.gbl...
> Also try to put quotes around the user name (try both single quotes and
> double quotes, one of them should be able to handle special characters)
> hth
> --
> Vikram Vamshi
> Database Engineer
> Eclipsys Corporation
> "Ajey" <ajey5@.hotmail.com> wrote in message
> news:uZXxuFojFHA.2644@.TK2MSFTNGP09.phx.gbl...
>

DMO SQLServer->Connect failed for user name with special characters

Hi,
If I give a user name or password having special character (mainly
semi-colon) then I cannot connect to the SQL Server. Following is the error:
Login failed for user 'a`~!@.#$%^&*()_+|-=[]'.
TCP Provider: An existing connection was forcibly closed by the
remote host.
Communication link failure
Invalid connection string attribute
However, this error was coming in my Cpp code. I tried with VB, I
works. Also, I got same error from Enterprise Manager.
Is this a defect or known behavior in DMO?
TIA,
Ajey
Actual user name was a`~!@.#$%^&*()_+|-=[];',./{}:"<>?
"Ajey" <ajey5@.hotmail.com> wrote in message
news:ujnaqXcjFHA.1428@.TK2MSFTNGP10.phx.gbl...
> Hi,
> If I give a user name or password having special character (mainly
> semi-colon) then I cannot connect to the SQL Server. Following is the
> error:
> Login failed for user 'a`~!@.#$%^&*()_+|-=[]'.
> TCP Provider: An existing connection was forcibly closed by the
> remote host.
> Communication link failure
> Invalid connection string attribute
> However, this error was coming in my Cpp code. I tried with VB, I
> works. Also, I got same error from Enterprise Manager.
> Is this a defect or known behavior in DMO?
>
> TIA,
> Ajey
>
|||/ is an escape character in cpp, you have to replace / with // in your
string for it to work properly.
hth
Vikram Vamshi
Database Engineer
Eclipsys Corporation
"Ajey" <ajey5@.hotmail.com> wrote in message
news:OqwRXccjFHA.3316@.TK2MSFTNGP14.phx.gbl...
> Actual user name was a`~!@.#$%^&*()_+|-=[];',./{}:"<>?
> "Ajey" <ajey5@.hotmail.com> wrote in message
> news:ujnaqXcjFHA.1428@.TK2MSFTNGP10.phx.gbl...
>
|||I think it's mainly due to semi-colon. The error message displays the user
names till the character before the semi-colon. Also, same username &
password does not work while registering the sql server using Enterprise
Manager or connecting through Query Analyser.
- Ajey
"Vikram Vamshi" <vikram.vamshi@.online.eclipsys.com> wrote in message
news:uMKZSCkjFHA.3900@.TK2MSFTNGP10.phx.gbl...
>/ is an escape character in cpp, you have to replace / with // in your
>string for it to work properly.
> hth
> --
> Vikram Vamshi
> Database Engineer
> Eclipsys Corporation
> "Ajey" <ajey5@.hotmail.com> wrote in message
> news:OqwRXccjFHA.3316@.TK2MSFTNGP14.phx.gbl...
>
|||Can you post your cpp code that can reproduce the issue?
Vikram Vamshi
Database Engineer
Eclipsys Corporation
"Ajey" <ajey5@.hotmail.com> wrote in message
news:uZXxuFojFHA.2644@.TK2MSFTNGP09.phx.gbl...
>I think it's mainly due to semi-colon. The error message displays the user
>names till the character before the semi-colon. Also, same username &
>password does not work while registering the sql server using Enterprise
>Manager or connecting through Query Analyser.
> - Ajey
> "Vikram Vamshi" <vikram.vamshi@.online.eclipsys.com> wrote in message
> news:uMKZSCkjFHA.3900@.TK2MSFTNGP10.phx.gbl...
>
|||Also try to put quotes around the user name (try both single quotes and
double quotes, one of them should be able to handle special characters)
hth
Vikram Vamshi
Database Engineer
Eclipsys Corporation
"Ajey" <ajey5@.hotmail.com> wrote in message
news:uZXxuFojFHA.2644@.TK2MSFTNGP09.phx.gbl...
>I think it's mainly due to semi-colon. The error message displays the user
>names till the character before the semi-colon. Also, same username &
>password does not work while registering the sql server using Enterprise
>Manager or connecting through Query Analyser.
> - Ajey
> "Vikram Vamshi" <vikram.vamshi@.online.eclipsys.com> wrote in message
> news:uMKZSCkjFHA.3900@.TK2MSFTNGP10.phx.gbl...
>
|||strSQLLoginName = L"abc;xyz"
strSQLLoginPassword = L"abc"
HRESULT hrConnect = spServer->Connect( rkstrCurrentServerName.c_str(),
strSQLLoginName.c_str(), strSQLLoginPassword.c_str() );
This code also gives the same error. Also, if i paste user name as abc;xyz
in Enterprise Manager or Query Analyzer I get the same error.
The same thing works with ADO. I had to just escape the special characters
in the connection string. While can pass the username & password directly to
the ADOConnection->Connect() method. But same is not working on DMO.
Thanks.
- Ajey
"Vikram Vamshi" <vikram.vamshi@.online.eclipsys.com> wrote in message
news:OrYsYoujFHA.3316@.TK2MSFTNGP14.phx.gbl...
> Also try to put quotes around the user name (try both single quotes and
> double quotes, one of them should be able to handle special characters)
> hth
> --
> Vikram Vamshi
> Database Engineer
> Eclipsys Corporation
> "Ajey" <ajey5@.hotmail.com> wrote in message
> news:uZXxuFojFHA.2644@.TK2MSFTNGP09.phx.gbl...
>

Wednesday, March 7, 2012

Distribution Subsystem: agent (null) failed.

Win 2k & SQL 2k SP3a
This error appears in my Application Log. How can I fix/remove/delete
this? How can I determine what dB this is from?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17052
Date:12/23/2005
Time:8:00:11 AM
User:ROUSES.COM\Administrator
Computer:ROUSEONE
Description:
Error: 14151, Severity: 18, State: 1
Replication-Replication Distribution Subsystem: agent (null) failed.
The subscription to publication '(null)' has expired and does not
exist.
Data:
0000: 47 37 00 00 12 00 00 00 G7.....
0008: 09 00 00 00 52 00 4f 00 ...R.O.
0010: 55 00 53 00 45 00 4f 00 U.S.E.O.
0018: 4e 00 45 00 00 00 0d 00 N.E....
0020: 00 00 64 00 69 00 73 00 ..d.i.s.
0028: 74 00 72 00 69 00 62 00 t.r.i.b.
0030: 75 00 74 00 69 00 6f 00 u.t.i.o.
0038: 6e 00 00 00 n...
Run your agents one by one to see if you can manually force this error in
your event log.
Hilary Cotter
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
"LPR-3rd" <lreames@.gmail.com> wrote in message
news:1135354198.113526.29560@.z14g2000cwz.googlegro ups.com...
> Win 2k & SQL 2k SP3a
> This error appears in my Application Log. How can I fix/remove/delete
> this? How can I determine what dB this is from?
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 12/23/2005
> Time: 8:00:11 AM
> User: ROUSES.COM\Administrator
> Computer: ROUSEONE
> Description:
> Error: 14151, Severity: 18, State: 1
> Replication-Replication Distribution Subsystem: agent (null) failed.
> The subscription to publication '(null)' has expired and does not
> exist.
> Data:
> 0000: 47 37 00 00 12 00 00 00 G7.....
> 0008: 09 00 00 00 52 00 4f 00 ...R.O.
> 0010: 55 00 53 00 45 00 4f 00 U.S.E.O.
> 0018: 4e 00 45 00 00 00 0d 00 N.E....
> 0020: 00 00 64 00 69 00 73 00 ..d.i.s.
> 0028: 74 00 72 00 69 00 62 00 t.r.i.b.
> 0030: 75 00 74 00 69 00 6f 00 u.t.i.o.
> 0038: 6e 00 00 00 n...
>

Saturday, February 25, 2012

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 of Transaction Replication publication being marked SUSPECT by recov

Hi experts there,
I have a Publication created for Transactional Replication. All the
while working fine.
Now it failed and I am not able to access to the database at all. It
shows the following error message:
Error 926: Database 'distribution' cannot be opened. It has been
marked SUSPECT by recovery. See the SQLServer error log for more
information.
Tried to detach the database but getting the following error: -
"The database cannot be detached while it is being replicated"
Tried running DBCC CheckDB but cannot run with database still in
suspect mode
Basically I cannot perform backup on it, cannot detach it, cannot even
drop the publication.
Tried also the following method:
1) sp_resetstatus DISTRIBUTION
Prior to updating sysdatabases entry for database 'DISTRIBUTION', mode
= 0 and status = 24 (status suspect_bit = 0).
No row in sysdatabases was updated because mode and status are already
correctly reset. No error and no changes made.
2) DBCC CHECKDB ('DISTRIBUTION', REPAIR_REBUILD) WITH ALL_ERRORMSGS
Server: Msg 926, Level 10, State 1, Line 1
Database 'distribution' cannot be opened. It has been marked SUSPECT
by recovery. See the SQL Server errorlog for more information.
Anybody know what cause all this and how to resolve it? Please
help!!!!!
I need to make the Replication running back soonest possible.
Thanks/TewI have seen this behavior once before. The only way we could get it out of
suspect mode was to directly update the sysdatabases table and set the
status to 32768 (emergency bypass). After recycling SQL Server we were then
able to run Checkdb. You might find corruption in the database. If not you
can set the status back to 0 and see if it will recover normally.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Friday, February 24, 2012

Distribution Agent failed with error

My Snapshot was successful but an error occurs when I try to run the
distribution agent.
Invalid object name 'PA_COLUMN_NAMES1_V'.
(Source: ADMIN1SERVER\ADMINSQL (Data source); Error number: 208)
------
Unable to replicate a view or function because the referenced objects or
columns are not present on the Subscriber.
(Source: AGENT (Agent); Error number: 00000)
Any help here would be appreciated,
Rick Rushing
"Rick Rushing" schrieb:

> My Snapshot was successful but an error occurs when I try to run the
> distribution agent.
> Invalid object name 'PA_COLUMN_NAMES1_V'.
> (Source: ADMIN1SERVER\ADMINSQL (Data source); Error number: 208)
> ------
> Unable to replicate a view or function because the referenced objects or
> columns are not present on the Subscriber.
> (Source: AGENT (Agent); Error number: 00000)
> --
> Any help here would be appreciated,
> Rick Rushing
1. Check if the referenced table is part of the publication (if yes: try two
seperate publications: the first one includes the referenced table and the
second one includes the function).
2. Check the ownership of the objects (error 208 in replications often
appears if the owner of the objects in the publisher is not 'dbo'). The use
of a different owner than 'dbo' for the objects + the use of the rather
inflexible replication wizzards unfortunately is a little buggy
|||The view refers to either a table which isn't part of the publication, or
another view in which case the metadata doesn't reflect the dependencies.
AFAIK this error can't refer to a function or stored procedure, as both use
deferred name resolution, consequently the absence of dependant objects on
the subscriber at synchronization time is not an issue. You could use
logging to find out the objects causing dependancy problem. If it is between
views then you could try to fix it by refreshing the objects, assuming they
are all replicated together in the same publication. If it's a dependency
between the view and table, you could follow Christian's good advice and
make sure the table is also replicated - either the same publication, or
another which initializes before this one.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Distribution agent failed but didn't ?

Hi There

I have the following setup.

Server A transactionally replicates to Server B , using Server C as remote distributor.

Now the distribution agent runs on Server B, under distribution agents in replication monitor the distribution agent is the same job as the job on Server B defined as REPL-Dsitributor, correct ?

Now this morning at 4am under distribution agents on the remote distributor the job was marked as failed (error: no response in 10 minutes), but the "same job" on Server B, was not failed ?

The replication agent failure alert did not fire, neither did the notification failure alert on the job it self ?

What the %#$&#% happened ? This is a production environment so it is very worrying ?

Only according to the distribution agent on the remote distributor did the job fail, but not the job itself on the subscriber ?

Firstly what happened here ?
Secondly how can i make the agent keep retrying ? Once it failed it stayed failed, can i configure it to keep trying ?

Thanx
How can i make this agent keep retrying ?As for your case, distribution agent may not run on B but C (remote distributor) and replmonitor actually monitor agent job on C.

If your subscription is push, distribution agent will run under C. But if your subscription is pull, it will run under B.

About your another question, if agent job can keep retrying if it fails. That's depends, if it fails to access some meta data or subscription database, some access issue, it will retry five times and fail. Other problem cause the agent job fail, it just fail, until your solve the problem and restart it again. Otherwise, it won't run.

Hope it will help you some.

-Yunjing

Distribution agent failed

Hi,
Our production site, I enabled snapshot replication, last night the
distribution agent failed with error message: Detect nonlogged agent
shutdown. I really don't know what that means; can someone help me to solve
this problem?
Regards,
-Chen
Sometimes the binary crashes and doesn't hand an error back to the SQL
Server subsystem.
In this case restart the distribution agent to see if it is a transitory
error.
You might also want to enable logging to see what it gives you - if
anything. Follow this link
http://support.microsoft.com/default...b;en-us;312292
Hilary Cotter
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
"Chen" <Chen@.discussions.microsoft.com> wrote in message
news:26344E32-2FED-4A84-B73C-544ED47023BA@.microsoft.com...
> Hi,
> Our production site, I enabled snapshot replication, last night the
> distribution agent failed with error message: Detect nonlogged agent
> shutdown. I really don't know what that means; can someone help me to
solve
> this problem?
> Regards,
> -Chen
>
|||Thanks! I will try it.
"Hilary Cotter" wrote:

> Sometimes the binary crashes and doesn't hand an error back to the SQL
> Server subsystem.
> In this case restart the distribution agent to see if it is a transitory
> error.
> You might also want to enable logging to see what it gives you - if
> anything. Follow this link
> http://support.microsoft.com/default...b;en-us;312292
> --
> Hilary Cotter
> 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
> "Chen" <Chen@.discussions.microsoft.com> wrote in message
> news:26344E32-2FED-4A84-B73C-544ED47023BA@.microsoft.com...
> solve
>
>

Distribution Agent Error: Syntax error or access violation

I am getting this error in the distribution agent that I setup for
transactional replication. The last command which failed is like "CALL
sp_MSins_CompanyName$Trans_ Sales Entry ("
The table name is lengthy and contains spaces too. I believe this is because
of the spaces in the stored procedure name which is causing the syntax
error.
The problem is, I cant rename the tables to ommit the spaces. Isnt there any
way to rename the stored procedures and relink them with the new name so
that the new renamed procedure should be called rather than system keep on
looking for the procedure with the original name?
If there any solution in SQL for this issue that would be great otherwise I
must have to do some workaround if possible.
Muhammad
When you create your publication you can specify the name of the stored
procedure you wish to use. SQL Server will autogenerate that stored
procedure with the name.
Hilary Cotter
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
"Muhammad Shahzad Saleem" <msaleem@.simplywireless.com> wrote in message
news:uJ9xOIuHHHA.1044@.TK2MSFTNGP02.phx.gbl...
>I am getting this error in the distribution agent that I setup for
>transactional replication. The last command which failed is like "CALL
>sp_MSins_CompanyName$Trans_ Sales Entry ("
> The table name is lengthy and contains spaces too. I believe this is
> because of the spaces in the stored procedure name which is causing the
> syntax error.
> The problem is, I cant rename the tables to ommit the spaces. Isnt there
> any way to rename the stored procedures and relink them with the new name
> so that the new renamed procedure should be called rather than system keep
> on looking for the procedure with the original name?
> If there any solution in SQL for this issue that would be great otherwise
> I must have to do some workaround if possible.
> Muhammad
>

Distribution agent cannot find sp_MSupd_users

I created a Publication and Subscription. Once LogReader detected
transactions for replication. Distribution Agent status failed with error
"Cound not find stored procedure 'sp_MSupd_users'". I cannot find any KB on
this error, any suggestion?
Indeed, "users" is my table name
|||It seems it is caused by Command replacement on article defaults, when will
we use command replacement then?
|||Are you doing a nosync initialization? If so, you'll need to use
sp_scriptpublicationcustomprocs (please see
http://www.replicationanswers.com/No...alizations.asp).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Friday, February 17, 2012

distributed transaction on win 2003 server failed

Hi Guys,
I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
win2k working fine.
but the same transaction not working in win2k3.
i am getting the following error.
Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
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. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
NETWORK ACCESS.
MY CODE IS LIKE THIS.
CREATE PROCEDURE P2( @.NO INT)
AS
BEGIN DISTRIBUTED TRAN
INSERT INTO TESTB VALUES(1,'GH')
EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
COMMIT TRAN
pls advice me
On a Windows 2003 cluster you have to manually create a MSDTC cluster
instance.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"bijupg" <bijupg@.hotmail.com> wrote in message
news:0dbe01c503b2$665adce0$a601280a@.phx.gbl...
> Hi Guys,
> I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
> win2k working fine.
> but the same transaction not working in win2k3.
> i am getting the following error.
> Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
> 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. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
> NETWORK ACCESS.
> MY CODE IS LIKE THIS.
> CREATE PROCEDURE P2( @.NO INT)
> AS
> BEGIN DISTRIBUTED TRAN
> INSERT INTO TESTB VALUES(1,'GH')
> EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
> COMMIT TRAN
> pls advice me

Distributed transaction failed.

In my application I try to select data from linked table.
Then i do this i catch the exception. How to correct this problem? and
Why this problem is occured?
Stack trace:
Caused by: java.sql.SQLException: [Microsoft][SQLServer JDBC
Driver][SQLServer]The operation could not be performed because the OLE
DB provider 'MSDASQL' was unable to begin a distributed transaction.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown
Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
Source)
at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
Source)
at
com.microsoft.jdbc.sqlserver.tds.TDSCursorRequest.openCursor(Unknown
Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplStatement.execute(Unknown
Source)
at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown Source)
at com.microsoft.jdbc.base.BaseStatement.executeQueryInternal(Unknown
Source)
at com.microsoft.jdbc.base.BasePreparedStatement.executeQuery(Unknown
Source)
Thankshi,
please make sure that the "microsoft distributed transaction coordinator"
MSDTC is running
thanks,
Jose de Jesus Jr. Mcp,Mcdba
Data Architect
Sykes Asia (Manila philippines)
MCP #2324787
"dima.kroshkin@.gmail.com" wrote:

> In my application I try to select data from linked table.
> Then i do this i catch the exception. How to correct this problem? and
> Why this problem is occured?
>
> Stack trace:
> Caused by: java.sql.SQLException: [Microsoft][SQLServer JDBC
> Driver][SQLServer]The operation could not be performed because the OLE
> DB provider 'MSDASQL' was unable to begin a distributed transaction.
> at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown
> Source)
> at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown
> Source)
> at
> com.microsoft.jdbc.sqlserver.tds.TDSCursorRequest.openCursor(Unknown
> Source)
> at com.microsoft.jdbc.sqlserver.SQLServerImplStatement.execute(Unknown
> Source)
> at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown Source)
> at com.microsoft.jdbc.base.BaseStatement.executeQueryInternal(Unknown
> Source)
> at com.microsoft.jdbc.base.BasePreparedStatement.executeQuery(Unknown
> Source)
>
> Thanks
>|||Sorry, I dispose information that in SQL Query Analizer the query which
cause conflict execute successfully, but i don't know which rights user
had.
May be this error occurs because incorrect settings for OLE DB provider?

distributed transaction failed on win 2003

Hi Guys,
I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
win2k working fine.
but the same transaction not working in win2k3.
i am getting the following error.
Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
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. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
NETWORK ACCESS.
MY CODE IS LIKE THIS.
CREATE PROCEDURE P2( @.NO INT)
AS
BEGIN DISTRIBUTED TRAN
INSERT INTO TESTB VALUES(1,'GH')
EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
COMMIT TRAN
pls advice mecontrol panel, addr emove perograms, add/remove win components, application
server, enable network COM+ access
"bijupg" wrote:
> Hi Guys,
> I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
> win2k working fine.
> but the same transaction not working in win2k3.
> i am getting the following error.
> Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
> 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. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
> NETWORK ACCESS.
> MY CODE IS LIKE THIS.
> CREATE PROCEDURE P2( @.NO INT)
> AS
> BEGIN DISTRIBUTED TRAN
> INSERT INTO TESTB VALUES(1,'GH')
> EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
> COMMIT TRAN
> pls advice me
>|||check "Allow other SQL Servers to connect remotely to this SQL Server using
RPC" and "Enforce distributed transactions"
"Aleksandar Grbic" wrote:
> control panel, addr emove perograms, add/remove win components, application
> server, enable network COM+ access
> "bijupg" wrote:
> > Hi Guys,
> >
> > I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
> > win2k working fine.
> > but the same transaction not working in win2k3.
> >
> > i am getting the following error.
> >
> > Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
> > 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. ]
> > OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> > ITransactionJoin::JoinTransaction returned 0x8004d00a].
> >
> > NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
> > NETWORK ACCESS.
> >
> > MY CODE IS LIKE THIS.
> > CREATE PROCEDURE P2( @.NO INT)
> > AS
> > BEGIN DISTRIBUTED TRAN
> > INSERT INTO TESTB VALUES(1,'GH')
> > EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
> > COMMIT TRAN
> >
> > pls advice me
> >|||even after this not working.
>--Original Message--
>check "Allow other SQL Servers to connect remotely to
this SQL Server using
>RPC" and "Enforce distributed transactions"
>"Aleksandar Grbic" wrote:
>> control panel, addr emove perograms, add/remove win
components, application
>> server, enable network COM+ access
>> "bijupg" wrote:
>> > Hi Guys,
>> >
>> > I AM USING DISTRIBUTED TRANSACTION WITH sql server
2000 on
>> > win2k working fine.
>> > but the same transaction not working in win2k3.
>> >
>> > i am getting the following error.
>> >
>> > Server: Msg 7391, Level 16, State 1, Procedure P2,
Line 5
>> > 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. ]
>> > OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
>> > ITransactionJoin::JoinTransaction returned
0x8004d00a].
>> >
>> > NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED
FOR
>> > NETWORK ACCESS.
>> >
>> > MY CODE IS LIKE THIS.
>> > CREATE PROCEDURE P2( @.NO INT)
>> > AS
>> > BEGIN DISTRIBUTED TRAN
>> > INSERT INTO TESTB VALUES(1,'GH')
>> > EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
>> > COMMIT TRAN
>> >
>> > pls advice me
>> >
>.
>

distributed transaction failed on win 2003

Hi Guys,
I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
win2k working fine.
but the same transaction not working in win2k3.
i am getting the following error.
Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
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. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
NETWORK ACCESS.
MY CODE IS LIKE THIS.
CREATE PROCEDURE P2( @.NO INT)
AS
BEGIN DISTRIBUTED TRAN
INSERT INTO TESTB VALUES(1,'GH')
EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
COMMIT TRAN
pls advice me
control panel, addr emove perograms, add/remove win components, application
server, enable network COM+ access
"bijupg" wrote:

> Hi Guys,
> I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
> win2k working fine.
> but the same transaction not working in win2k3.
> i am getting the following error.
> Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
> 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. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
> NETWORK ACCESS.
> MY CODE IS LIKE THIS.
> CREATE PROCEDURE P2( @.NO INT)
> AS
> BEGIN DISTRIBUTED TRAN
> INSERT INTO TESTB VALUES(1,'GH')
> EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
> COMMIT TRAN
> pls advice me
>
|||check "Allow other SQL Servers to connect remotely to this SQL Server using
RPC" and "Enforce distributed transactions"
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> control panel, addr emove perograms, add/remove win components, application
> server, enable network COM+ access
> "bijupg" wrote:
|||even after this not working.
>--Original Message--
>check "Allow other SQL Servers to connect remotely to
this SQL Server using[vbcol=seagreen]
>RPC" and "Enforce distributed transactions"
>"Aleksandar Grbic" wrote:
components, application[vbcol=seagreen]
2000 on[vbcol=seagreen]
Line 5[vbcol=seagreen]
DB[vbcol=seagreen]
cannot[vbcol=seagreen]
0x8004d00a].[vbcol=seagreen]
FOR
>.
>

distributed transaction failed on win 2003

Hi Guys,
I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
win2k working fine.
but the same transaction not working in win2k3.
i am getting the following error.
Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
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. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
NETWORK ACCESS.
MY CODE IS LIKE THIS.
CREATE PROCEDURE P2( @.NO INT)
AS
BEGIN DISTRIBUTED TRAN
INSERT INTO TESTB VALUES(1,'GH')
EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
COMMIT TRAN
pls advice mecontrol panel, addr emove perograms, add/remove win components, application
server, enable network COM+ access
"bijupg" wrote:

> Hi Guys,
> I AM USING DISTRIBUTED TRANSACTION WITH sql server 2000 on
> win2k working fine.
> but the same transaction not working in win2k3.
> i am getting the following error.
> Server: Msg 7391, Level 16, State 1, Procedure P2, Line 5
> 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. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> NOTE: MSDTC IS RUNNING ON BOTH SERVERS AND ENABLED FOR
> NETWORK ACCESS.
> MY CODE IS LIKE THIS.
> CREATE PROCEDURE P2( @.NO INT)
> AS
> BEGIN DISTRIBUTED TRAN
> INSERT INTO TESTB VALUES(1,'GH')
> EXEC SHAFEEQVIRTUAL.PUBS.DBO.P1 @.NO
> COMMIT TRAN
> pls advice me
>|||check "Allow other SQL Servers to connect remotely to this SQL Server using
RPC" and "Enforce distributed transactions"
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> control panel, addr emove perograms, add/remove win components, applicatio
n
> server, enable network COM+ access
> "bijupg" wrote:
>|||even after this not working.
>--Original Message--
>check "Allow other SQL Servers to connect remotely to
this SQL Server using
>RPC" and "Enforce distributed transactions"
>"Aleksandar Grbic" wrote:
>
components, application[vbcol=seagreen]
2000 on[vbcol=seagreen]
Line 5[vbcol=seagreen]
DB[vbcol=seagreen]
cannot[vbcol=seagreen]
0x8004d00a].[vbcol=seagreen]
FOR[vbcol=seagreen]
>.
>