Error while connection: idea

Showing posts with label idea. Show all posts

Monday, March 26, 2012

Error: 70000, Severity: 10, State: 1

do you have any idea about "Error: 70000" ?

By any chance you are hitting this during setup? If so, then most likely the reason is that MS .Net Framework 2.0 is not installed.

If this is not the case, please, let us know and copy the error and a brief description of what were you doing when it happened.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

|||

thank a lot for response.

MS .Net is installed: v1.0.3705 , v1.1.4322, v2.0.50727

we have installed Windows 2000 Server SP4 with application useing DB. for our solution was enough MSDE.

there was 1.time MSDE2000, then we updated to MS SQL2000 Personal and now we made upgrade (because of increase of users and performance) to MS SQL Server 2000 Standard (ver: 2000.8.00.2039)

after this upgrade, we can see this error message. SQL server and application is running correct without any problems.

any other idea ?

SQL server log>

Date Source Message
2007-06-27 14:52:18.60 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) ...
2007-06-27 14:52:18.70 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQ
2007-06-27 14:52:18.70 server Server Process ID is 984.
2007-06-27 14:52:18.70 server All rights reserved.
2007-06-27 14:52:18.70 server Copyright (C) 1988-2002 Microsoft Corporation.
2007-06-27 14:52:18.79 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2007-06-27 14:52:19.87 server SQL Server configured for thread mode processing.
2007-06-27 14:52:19.92 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2007-06-27 14:52:20.73 server Attempting to initialize Distributed Transaction Coordinator.
2007-06-27 14:52:23.62 server Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b
2007-06-27 14:52:23.73 spid4 Starting up database 'master'.
2007-06-27 14:52:25.01 spid5 Starting up database 'model'.
2007-06-27 14:52:25.01 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-06-27 14:52:25.06 spid4 Server name is 'TELEVANTAGE'.
2007-06-27 14:52:25.09 spid8 Starting up database 'TVDB'.
2007-06-27 14:52:25.09 spid9 Starting up database 'msdb'.
2007-06-27 14:52:25.39 server SQL server listening on 127.0.0.1: 1433.
2007-06-27 14:52:25.39 server SQL server listening on 172.16.3.8: 1433.
2007-06-27 14:52:25.56 spid5 Clearing tempdb database.
2007-06-27 14:52:25.81 server SQL Server is ready for client connections
2007-06-27 14:52:25.81 server SQL server listening on TCP, Shared Memory, Named Pipes.
2007-06-27 14:52:26.32 spid8 97 transactions rolled forward in database 'TVDB' (5).
2007-06-27 14:52:26.85 spid8 1 transactions rolled back in database 'TVDB' (5).
2007-06-27 14:52:26.90 spid8 Recovery is checkpointing database 'TVDB' (5)
2007-06-27 14:52:28.18 spid5 Starting up database 'tempdb'.
2007-06-27 14:52:35.73 spid51 Using 'odsole70.dll' version '2000.80.2039' to execute extended stored procedur
2007-06-27 14:52:44.32 spid4 SQL global counter collection task is created.
2007-06-27 14:52:44.32 spid4 Recovery complete.
2007-06-27 14:53:11.98 spid54 DBCC TRACEON 3604, server process ID (SPID) 54.
2007-06-27 14:53:19.51 spid56 Using 'xplog70.dll' version '2000.80.2039' to execute extended stored procedure
2007-06-27 14:53:22.48 spid58 Using 'xpsqlbot.dll' version '2000.80.2039' to execute extended stored procedur
2007-06-27 14:53:27.20 spid56 Configuration option 'max server memory (MB)' changed from 1019 to 1019. Run th
2007-06-27 14:53:27.20 spid56 Error: 15457, Severity: 0, State: 1
2007-06-27 14:53:27.32 spid56 Configuration option 'min server memory (MB)' changed from 509 to 509. Run the
2007-06-27 14:53:27.32 spid56 Error: 15457, Severity: 0, State: 1
2007-06-27 14:53:27.45 spid56 Configuration option 'min memory per query (KB)' changed from 512 to 512. Run t
2007-06-27 14:53:27.45 spid56 Error: 15457, Severity: 0, State: 1
2007-06-27 14:54:06.17 spid64 Using 'xpstar.dll' version '2000.80.2039' to execute extended stored procedure
2007-06-27 14:57:09.43 spid59 Configuration option 'show advanced options' changed from 1 to 1. Run the RECON
2007-06-27 14:57:09.43 spid59 Error: 15457, Severity: 0, State: 1
2007-06-27 14:59:46.71 spid615 Configuration option 'show advanced options' changed from 1 to 1. Run the RECON
2007-06-27 14:59:46.71 spid615 Error: 15457, Severity: 0, State: 1
2007-06-27 15:11:00.39 spid653 Input buffer for processes 651: exec sp_dbcmptlevel 'TVDB', 70.
2007-06-27 15:11:00.39 spid653 Error: 70000, Severity: 10, State: 1
2007-06-27 15:11:00.39 spid653 .
2007-06-27 15:11:00.39 spid653 Error: 70000, Severity: 10, State: 1
2007-06-27 15:11:00.62 spid653 Above process will be removed if still blocking on next check.
2007-06-27 15:11:00.62 spid653 Error: 70000, Severity: 10, State: 1
2007-06-27 16:08:00.60 spid619 Blocking process 636 using Permissions table with lock type 6 owned by TVCLIENT
2007-06-27 16:08:00.60 spid619 Error: 70000, Severity: 10, State: 1
2007-06-27 16:08:00.68 spid619 Input buffer for processes 636: exec sp_getFolder 1944, 5115.
2007-06-27 16:08:00.68 spid619 Error: 70000, Severity: 10, State: 1
2007-06-27 16:08:00.75 spid619 Above process will be removed if still blocking on next check.
2007-06-27 16:08:00.75 spid619 Error: 70000, Severity: 10, State: 1
2007-06-27 16:08:00.85 spid619 .
2007-06-27 16:08:00.85 spid619 Error: 70000, Severity: 10, State: 1
2007-06-27 16:08:00.89 spid619 Input buffer for processes 663: exec sp_getFolder 1920, 5115.
2007-06-27 16:08:00.89 spid619 Error: 70000, Severity: 10, State: 1
2007-06-27 16:08:00.92 spid619 Above process will be removed if still blocking on next check.
2007-06-27 16:08:00.92 spid619 Error: 70000, Severity: 10, State: 1
2007-06-27 21:26:00.37 spid622 Above process will be removed if still blocking on next check.
2007-06-27 21:26:00.37 spid622 Error: 70000, Severity: 10, State: 1
2007-06-27 21:26:00.37 spid622 Input buffer for processes 613: exec sp_addPartyLog 713908, 33, '', 'Unknown',
2007-06-27 21:26:00.37 spid622 Error: 70000, Severity: 10, State: 1
2007-06-27 21:26:00.37 spid622 .

|||Error 70000 should be a custom one, you should contact the person which implemented it. If you are not sure about it run the profiler to see where the error message comes from.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Any updates on that ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

sorry for no response. I have no new messages.. it's probably any internal message in our application what we are using, but developer of this appliaction didn't tell us more info about. there is no problem with functionality... so we are ignoring this message.

thanks

Error: 70000, Severity: 10, State: 1

do you have any idea about "Error: 70000" ?

By any chance you are hitting this during setup? If so, then most likely the reason is that MS .Net Framework 2.0 is not installed.

If this is not the case, please, let us know and copy the error and a brief description of what were you doing when it happened.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

|||

thank a lot for response.

MS .Net is installed: v1.0.3705 , v1.1.4322, v2.0.50727

we have installed Windows 2000 Server SP4 with application useing DB. for our solution was enough MSDE.

there was 1.time MSDE2000, then we updated to MS SQL2000 Personal and now we made upgrade (because of increase of users and performance) to MS SQL Server 2000 Standard (ver: 2000.8.00.2039)

after this upgrade, we can see this error message. SQL server and application is running correct without any problems.

any other idea ?

SQL server log>

|||Error 70000 should be a custom one, you should contact the person which implemented it. If you are not sure about it run the profiler to see where the error message comes from.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Any updates on that ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

thanks

Error: 70000, Severity: 10, State: 1

do you have any idea about "Error: 70000" ?

By any chance you are hitting this during setup? If so, then most likely the reason is that MS .Net Framework 2.0 is not installed.

If this is not the case, please, let us know and copy the error and a brief description of what were you doing when it happened.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

|||

thank a lot for response.

MS .Net is installed: v1.0.3705 , v1.1.4322, v2.0.50727

we have installed Windows 2000 Server SP4 with application useing DB. for our solution was enough MSDE.

there was 1.time MSDE2000, then we updated to MS SQL2000 Personal and now we made upgrade (because of increase of users and performance) to MS SQL Server 2000 Standard (ver: 2000.8.00.2039)

after this upgrade, we can see this error message. SQL server and application is running correct without any problems.

any other idea ?

SQL server log>

|||Error 70000 should be a custom one, you should contact the person which implemented it. If you are not sure about it run the profiler to see where the error message comes from.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Any updates on that ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

thanks

Thursday, March 22, 2012

Error: 3314 serverity: 21, state: 4

I have this error, and it auto recovery after 1 minutes.. any idea? and it
involved more then one db.
Error while undoing logged operation in database 'hash'. Error at log record
i (20969:622890:4)..
Error : 9901,Severity: 21, state 1
the log file for database 'hash' is not available
Database hash cannot be open, it has been marked suspect for recovery, see
the sql server errorlog for more information.
starting up database 'hash'soonyu wrote:
> I have this error, and it auto recovery after 1 minutes.. any idea? and it
> involved more then one db.
> Error while undoing logged operation in database 'hash'. Error at log record
> i (20969:622890:4)..
> Error : 9901,Severity: 21, state 1
> the log file for database 'hash' is not available
> Database hash cannot be open, it has been marked suspect for recovery, see
> the sql server errorlog for more information.
> starting up database 'hash'
>
Is this a new installation, or one that has been running for a while?
Do you have any "bad block" events in your Windows Event Log around this
same time? My initial guess would be some sort of drive failure.|||This run for quite sometime.. more then year..
just notices this happen and twice already for this month..
first time, 2 db and auto recovery within one minutes..
second time, 1 db and auto recovery within one minutes as well..
Can't find any error.. and this is problem..
anybody have this kind of experience..
developer start mention about db problem..
soonyu.
"Tracy McKibben" wrote:
> soonyu wrote:
> > I have this error, and it auto recovery after 1 minutes.. any idea? and it
> > involved more then one db.
> >
> > Error while undoing logged operation in database 'hash'. Error at log record
> > i (20969:622890:4)..
> > Error : 9901,Severity: 21, state 1
> > the log file for database 'hash' is not available
> > Database hash cannot be open, it has been marked suspect for recovery, see
> > the sql server errorlog for more information.
> > starting up database 'hash'
> >
> Is this a new installation, or one that has been running for a while?
> Do you have any "bad block" events in your Windows Event Log around this
> same time? My initial guess would be some sort of drive failure.
>|||Perhaps you have auto-close turned on and some other process (like anti-virus) is opening the file?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:D1518541-C8C6-4D76-AF2A-8ACDA41CF1A3@.microsoft.com...
>I have this error, and it auto recovery after 1 minutes.. any idea? and it
> involved more then one db.
> Error while undoing logged operation in database 'hash'. Error at log record
> i (20969:622890:4)..
> Error : 9901,Severity: 21, state 1
> the log file for database 'hash' is not available
> Database hash cannot be open, it has been marked suspect for recovery, see
> the sql server errorlog for more information.
> starting up database 'hash'
>|||ok .. i will do two thing tommrow
1. check got bad block
2. check auto-close turned on?
3. antivirus scan/open this file?
but do you think auto-close will affected? auto-close you try to mentiion is
from sql enterprise manager->database->option->auto-close?
hopefully is not db corrupt.. but from can't find log and auto recovery, it
not seem db/log corrupt right? If so, the db will go to suspend mode?
--soonyu
"Tibor Karaszi" wrote:
> Perhaps you have auto-close turned on and some other process (like anti-virus) is opening the file?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "soonyu" <soonyu@.discussions.microsoft.com> wrote in message
> news:D1518541-C8C6-4D76-AF2A-8ACDA41CF1A3@.microsoft.com...
> >I have this error, and it auto recovery after 1 minutes.. any idea? and it
> > involved more then one db.
> >
> > Error while undoing logged operation in database 'hash'. Error at log record
> > i (20969:622890:4)..
> > Error : 9901,Severity: 21, state 1
> > the log file for database 'hash' is not available
> > Database hash cannot be open, it has been marked suspect for recovery, see
> > the sql server errorlog for more information.
> > starting up database 'hash'
> >
>|||soonyu wrote:
> ok .. i will do two thing tommrow
> 1. check got bad block
> 2. check auto-close turned on?
> 3. antivirus scan/open this file?
> but do you think auto-close will affected? auto-close you try to mentiion is
> from sql enterprise manager->database->option->auto-close?
>
That is the option she's referring to. Auto-close should never be
enabled on a production DB.
You also need to tell your antivirus software to exclude MDF, LDF, BAK,
and TRN files at minimum.

Error: 3314 serverity: 21, state: 4

soonyu wrote:
> I have this error, and it auto recovery after 1 minutes.. any idea? and i
t
> involved more then one db.
> Error while undoing logged operation in database 'hash'. Error at log reco
rd
> i (20969:622890:4)..
> Error : 9901,Severity: 21, state 1
> the log file for database 'hash' is not available
> Database hash cannot be open, it has been marked suspect for recovery, see
> the sql server errorlog for more information.
> starting up database 'hash'
>
Is this a new installation, or one that has been running for a while?
Do you have any "bad block" events in your Windows Event Log around this
same time? My initial guess would be some sort of drive failure.I have this error, and it auto recovery after 1 minutes.. any idea? and it
involved more then one db.
Error while undoing logged operation in database 'hash'. Error at log record
i (20969:622890:4)..
Error : 9901,Severity: 21, state 1
the log file for database 'hash' is not available
Database hash cannot be open, it has been marked suspect for recovery, see
the sql server errorlog for more information.
starting up database 'hash'|||soonyu wrote:
> I have this error, and it auto recovery after 1 minutes.. any idea? and i
t
> involved more then one db.
> Error while undoing logged operation in database 'hash'. Error at log reco
rd
> i (20969:622890:4)..
> Error : 9901,Severity: 21, state 1
> the log file for database 'hash' is not available
> Database hash cannot be open, it has been marked suspect for recovery, see
> the sql server errorlog for more information.
> starting up database 'hash'
>
Is this a new installation, or one that has been running for a while?
Do you have any "bad block" events in your Windows Event Log around this
same time? My initial guess would be some sort of drive failure.|||This run for quite sometime.. more then year..
just notices this happen and twice already for this month..
first time, 2 db and auto recovery within one minutes..
second time, 1 db and auto recovery within one minutes as well..
Can't find any error.. and this is problem..
anybody have this kind of experience..
developer start mention about db problem..
soonyu.
"Tracy McKibben" wrote:

> soonyu wrote:
> Is this a new installation, or one that has been running for a while?
> Do you have any "bad block" events in your Windows Event Log around this
> same time? My initial guess would be some sort of drive failure.
>|||Perhaps you have auto-close turned on and some other process (like anti-viru
s) is opening the file?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:D1518541-C8C6-4D76-AF2A-8ACDA41CF1A3@.microsoft.com...
>I have this error, and it auto recovery after 1 minutes.. any idea? and it
> involved more then one db.
> Error while undoing logged operation in database 'hash'. Error at log reco
rd
> i (20969:622890:4)..
> Error : 9901,Severity: 21, state 1
> the log file for database 'hash' is not available
> Database hash cannot be open, it has been marked suspect for recovery, see
> the sql server errorlog for more information.
> starting up database 'hash'
>|||ok .. i will do two thing tommrow
1. check got bad block
2. check auto-close turned on?
3. antivirus scan/open this file?
but do you think auto-close will affected? auto-close you try to mentiion is
from sql enterprise manager->database->option->auto-close?
hopefully is not db corrupt.. but from can't find log and auto recovery, it
not seem db/log corrupt right? If so, the db will go to suspend mode?
--soonyu
"Tibor Karaszi" wrote:

> Perhaps you have auto-close turned on and some other process (like anti-vi
rus) is opening the file?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "soonyu" <soonyu@.discussions.microsoft.com> wrote in message
> news:D1518541-C8C6-4D76-AF2A-8ACDA41CF1A3@.microsoft.com...
>|||soonyu wrote:
> ok .. i will do two thing tommrow
> 1. check got bad block
> 2. check auto-close turned on?
> 3. antivirus scan/open this file?
> but do you think auto-close will affected? auto-close you try to mentiion
is
> from sql enterprise manager->database->option->auto-close?
>
That is the option she's referring to. Auto-close should never be
enabled on a production DB.
You also need to tell your antivirus software to exclude MDF, LDF, BAK,
and TRN files at minimum.|||This run for quite sometime.. more then year..
just notices this happen and twice already for this month..
first time, 2 db and auto recovery within one minutes..
second time, 1 db and auto recovery within one minutes as well..
Can't find any error.. and this is problem..
anybody have this kind of experience..
developer start mention about db problem..
soonyu.
"Tracy McKibben" wrote:

> soonyu wrote:
> Is this a new installation, or one that has been running for a while?
> Do you have any "bad block" events in your Windows Event Log around this
> same time? My initial guess would be some sort of drive failure.
>|||Perhaps you have auto-close turned on and some other process (like anti-viru
s) is opening the file?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:D1518541-C8C6-4D76-AF2A-8ACDA41CF1A3@.microsoft.com...
>I have this error, and it auto recovery after 1 minutes.. any idea? and it
> involved more then one db.
> Error while undoing logged operation in database 'hash'. Error at log reco
rd
> i (20969:622890:4)..
> Error : 9901,Severity: 21, state 1
> the log file for database 'hash' is not available
> Database hash cannot be open, it has been marked suspect for recovery, see
> the sql server errorlog for more information.
> starting up database 'hash'
>|||ok .. i will do two thing tommrow
1. check got bad block
2. check auto-close turned on?
3. antivirus scan/open this file?
but do you think auto-close will affected? auto-close you try to mentiion is
from sql enterprise manager->database->option->auto-close?
hopefully is not db corrupt.. but from can't find log and auto recovery, it
not seem db/log corrupt right? If so, the db will go to suspend mode?
--soonyu
"Tibor Karaszi" wrote:

> Perhaps you have auto-close turned on and some other process (like anti-vi
rus) is opening the file?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "soonyu" <soonyu@.discussions.microsoft.com> wrote in message
> news:D1518541-C8C6-4D76-AF2A-8ACDA41CF1A3@.microsoft.com...
>

Monday, March 19, 2012

Error: 16954, Severity: 10, State: 1

Hi there.
I ran a trace over our SQL server and picked this error up.
Does anyone have any idea what could be causing this ?
Error: 16954, Severity: 10, State: 1
Our server is SQL2000 SP3a patched to 8.00.818 running on Win2K server.
Any help would be greatly appreciated.
Thanks
AndyHi
This error is connected with the use or no use of cursors.
The message indicated that a server side cursor was requested
(sp_cursoropen) but no cursor was necessary, as the SQL statement was
executed directly.
The error message can be informational.
Do you get timeout or disconnection after this error or any specific issue
on the Server Side?
HTH
Regards
Sadeesh
--
This posting is provided AS IS with no warranties, and confers no rights.
"Andy Hayes" <andyh@.friday-ad.co.uk> wrote in message
news:OjUrMY8bEHA.1000@.TK2MSFTNGP12.phx.gbl...
> Hi there.
> I ran a trace over our SQL server and picked this error up.
> Does anyone have any idea what could be causing this ?
> Error: 16954, Severity: 10, State: 1
> Our server is SQL2000 SP3a patched to 8.00.818 running on Win2K server.
> Any help would be greatly appreciated.
> Thanks
> Andy
>

Error: 16954, Severity: 10, State: 1

Hi there.
I ran a trace over our SQL server and picked this error up.
Does anyone have any idea what could be causing this ?
Error: 16954, Severity: 10, State: 1
Our server is SQL2000 SP3a patched to 8.00.818 running on Win2K server.
Any help would be greatly appreciated.
Thanks
Andy
Hi
This error is connected with the use or no use of cursors.
The message indicated that a server side cursor was requested
(sp_cursoropen) but no cursor was necessary, as the SQL statement was
executed directly.
The error message can be informational.
Do you get timeout or disconnection after this error or any specific issue
on the Server Side?
HTH
Regards
Sadeesh
This posting is provided AS IS with no warranties, and confers no rights.
"Andy Hayes" <andyh@.friday-ad.co.uk> wrote in message
news:OjUrMY8bEHA.1000@.TK2MSFTNGP12.phx.gbl...
> Hi there.
> I ran a trace over our SQL server and picked this error up.
> Does anyone have any idea what could be causing this ?
> Error: 16954, Severity: 10, State: 1
> Our server is SQL2000 SP3a patched to 8.00.818 running on Win2K server.
> Any help would be greatly appreciated.
> Thanks
> Andy
>

Wednesday, February 15, 2012

Error while creating subscription in transactional replication!

Hi ALL

I am configuring subscription for a reporting server and getting the following error message .

Any body having any idea would be of great help.

TITLE: New Subscription Wizard

Microsoft SQL Server Management Studio is unable to access replication components because replication is not installed on this instance of SQL Server. For information about installing replication, see the topic Installing Replication in SQL Server Books Online.

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=Microsoft.SqlServer.Management.UI.ReplUtilitiesErrorSR&EvtID=ReplicationNotInstalled&LinkId=20476

ADDITIONAL INFORMATION:

SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name, 'CORSTRATASQL01'. (Replication.Utilities)

BUTTONS:

Regards,

Salman Shehbaz.

Hi,
I had similar problems when I want to integrate a publisher into the replication monitor.
I had the problem , when the server is in anothe domain.
So first question is: Is CORSTRATASQL01 in anothe domain then the server you got the error message ?

At last we solve the problem with a reconfiguration of the DNS-suffixes of the TCP/IP properties.

Regards
Wolfgang

Monday, March 26, 2012

Error: 70000, Severity: 10, State: 1

Error: 70000, Severity: 10, State: 1

Error: 70000, Severity: 10, State: 1

Thursday, March 22, 2012

Error: 3314 serverity: 21, state: 4

Error: 3314 serverity: 21, state: 4

Monday, March 19, 2012

Error: 16954, Severity: 10, State: 1

Error: 16954, Severity: 10, State: 1

Error: 16954, Severity: 10, State: 1

Wednesday, February 15, 2012

Error while creating subscription in transactional replication!

Error while connection

Blog Archive

About Me