SQL 2005 Replication

Hi Experts,
I've installed SAP B1 2007 B PL-04 .
But the problem is ---Everyday I need to take a backUp. Can u tell me regarding the replication or any other way
that will keep an automatic BackUp?
Rgds
Subrata

Hi Subrata,
For the quickest and most cost efficient way of replication in SQL 2000/ SQL 2005 you should consider Log shipping / Asynchronous replication.
The overview of log shipping is as follows :
1) A primary server which holds the main db for sap business one and a secondary server holding the backup db.
2) At initialization, the primary sever via log shipping sends an instance of the db to be restored to the secondary server. Thereafter you configure the log shipping for various times to transfer logs from primary to secondary. The logs are then applied accordingly to the secondary server via sql scheduled job.
3) If the primary fails, you can simply switch to the secondary server and the data loss which you possibly face is the time duration you set for the log shipping. For example if you set the system to transfer logs every 20 minutes between the primary server and secondary and assuming the primary fails at 1.00pm, you can then switch to the secondary server which will be replicated upto 12.40pm with the latest logs applied to it. Offcourse the time slot of 20 minutes can be configured according to your requirements and since the two servers can be in one lan or wan, it is flexible in design.
One thing you must note is that the seconday server is a warm server and will not automatically be available after the primary has failed. Otherwise it would similar to clustering. The administrator must check logs to ensure the process is running smoothly and if primary fails, it is a simple manual sql command to get the secondary sap business one database live. Your can then direct the SAP business one clients to choose the secondary server and continue working while you deal with the primary.
You can find more notes with the following link :
http://msdn.microsoft.com/en-us/library/ms190016(SQL.90).aspx
Best of luck and I hope this solution will resolve your query.
Kind regards,
Indraj.

Similar Messages

SQL 2005 Replication with Oracle 11g

Hello Everyone,
Thanks in advance for looking at this. I am setting up replication from SQL Server 2005 with an Oracle 11g source. I've installed the Oracle 11g client and set up the service name on the SQL Server. I can successfully test the connection from
SQL to Oracle via the Oracle Net Manager as well as SQLPLUS.
When I try to add the Oracle Publisher to SQL, I can't get past the SQL Error 21627.
"Unable to connect to Oracle database server 'Name' using the Microsoft OLEDB provider MSDAORA."
Any ideas on what I am missing?
Thanks,
Eric

Thanks for the input Hilary. The oracleadmin.sql was ran on against the oracle instance long ago and since then we have been able to replicate. The previously successful replication was from a server that is no longer with us. I'm trying to get this
working again on a new server. Am I correct to assume that the script does not need to be ran again?
For the others, I'm working on the link server setup, but must be doing something wrong as I keep getting this:
TITLE: Microsoft SQL Server Management Studio
"The test connection to the linked server failed."
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server "NAME".
OLE DB provider "OraOLEDB.Oracle" for linked server "NAME" returned message "". (Microsoft SQL Server, Error: 7303)
I definitely appreciate the help everyone.

Sql server replication from SQL SERVER VERSION(7.0) to SQL SERVER 2005

Hi All,
We are trying to create a replication between Sql server 7.0 data to SQL server 2005 data . We tried to create a local subscription in Sql server ,when tried to connect to publisher running in Sql server 7.0 it is showing an error message
like "This Sql server vresion(7.0) is not supported" .
Could any one please help us with this issue ?
Thanks
Sandy

Hi CRM_Learner,
SQL Server version 7.0 Service Pack 4 (SP4) is the earliest version that can participate in a replication topology with SQL Server 2005. We need to verify the version of SQL Server. If you configure transactional replication with updating subscribers,
for a SQL Server 7.0 Publisher, only SQL Server 7.0 Subscribers are supported. SQL Server 7.0, 2000 was out of support in the SQL Server Forums. I suggest you install SQL Server 2005 or later version to configure the SQL Server replication.
For more information, there is a detail about using multiple Versions of SQL Server in a replication topology.
http://technet.microsoft.com/en-us/library/ms143241(v=sql.90).aspx
Regards,
Sofiya Li
If you have any feedback on our support, please click here.
Sofiya Li
TechNet Community Support

SQL 2005 to SQL 2012 Replication for SSRS

I recently successfully implemented one-way log shipping from a production SQL 2005 database to a new SQL 2012 database in the hopes that I can use the 2012 database to run SSRS 2012 on it.
Unfortunately, the 2012 database is kept offline since log shipping between two DIFFERENT SQL versions can only be done in a NO RECOVERY mode. (Standby mode is NOT available which would make the SQL 2012 read only and therefore workable for SSRS
2012.)
Does anyone have any suggestions on if there is another method on how to achieve this?

Yes, You can try replication. I hope you've latest service pack upgrade for SQL 2005.
http://msdn.microsoft.com/en-us/library/ms143699.aspx
BOL:-
A Subscriber to a transactional publication can be any version within two versions of the Publisher version. For example: a SQL Server 2005 Publisher can have Subscribers running SQL Server 2005, SQL Server 2008 (including SQL Server 2008 R2), or SQL Server
2012; and a SQL Server 2012 Publisher can have Subscribers running SQL Server 2005, SQL Server 2008 (including SQL Server 2008 R2), or SQL Server 2012.
-Prashanth
-Prashanth

Xp_logininfo "Installation problem on windows 2003 with Sql 2005"

Hi every one
I am facing a problem during the installation of Solution Manager 4.0 on Windows 2003 server with Ms Sql 2005, I received the following error
Msg 15404, Level 16, State 19, Procedure xp_logininfo, Line 60.
Its some how look likes that the user "SID"ADM
Can any one give me a clue
thanks
Kind Regards
Sohail

Hi All,
This would solve your problem
First of all this error is <b>MSSQL error</b>.
When you perform an action on an instance of SQL Server that requires SQL Server to resolve the credentials of a Microsoft Windows NT domain user account, you may receive an error message that is similar
Server: Msg 8198, Level 16, State XX, Procedure <Stored Procedure Name>, Line <line Number>
Could not obtain information about Windows NT group/user '<Domain\Account Name>'.
To resolve the credentials of a Windows NT domain user account, SQL Server uses the xp_logininfo system stored procedure. Here is a list of the common scenarios where you may notice that the xp_logininfo system stored procedure fails and causes the 8198 error.
When you use an xp_sendmail extended stored procedure.
When you set up replication.
When you run a SQL Server Agent job.
SQL Server may run the xp_logininfo system stored procedure to retrieve information about the Windows domains and the user accounts, even if the user does not do so explicitly. Therefore, if you receive an 8198 error message and the error message mentions the xp_logininfo system stored procedure as the procedure, you must use <b>SQL Profiler</b> to trace and to troubleshoot the exact point of failure.
You can go through this link for more info...
http://support.microsoft.com/?kbid=834124
Feel Free to Revert back...
--Thanks and Regards,
Ragu
ERP,
Suzlon Energy Limted, Pune
Extn: 2638
+919370675797
I have no limits for others sky is only a reason

SQL Azure Replication

My company is planning to move some of our applications to the cloud using Azure platform. We are also planning to use SQL Azure as our production database. My immediate concern is how do we replicate the production data (SQL Azure) to our reporting server
(currently SQL Server 2005 Standard, will be SQL Server 2008 Enterprise within 3 months), since we only keep a minimum amount of data on the production server but we keep everything on our reporting server? Our current setup uses SQL Server replication for
this purpose.
Also, I have seen this article on the internet and would like to get answers on the issues raised, for example backup/restore, reporting/analysis services, and of course replication.
Thanks.
AMF

Hi AMF,
SQL Azure Data Sync CTP2 seems like it would provide the data synchronization you need between SQL Server and SQL Azure.
http://www.microsoft.com/en-us/SQLAzure/datasync.aspx
Feel free to email me directly (Liam.Cavanagh AT microsoft.com) if I can be of help here.
Liam
Sr. Program Manager, SQL Azure and Sync Framework - http://msdn.microsoft.com/sync/

SQL 2005 cluster rejects SQL logins when in failed over state

When SQL 2005 SP4 on Windows 2003 server cluster is failed over from Server_A to Server_B, it rejects all SQL Server logins. domain logins are OK. The message is "user is not associated with a trusted server connection", then the IP of the
client. This is error 18452. Anyone know how to fix this? They should work fine from both servers. We think this started just after installing SP4.
DaveK

Hello,
The connection string is good, you're definitely using sql auth.
LoginMode on Server_B is REG_DWORD 0x00000001 (1) LoginMode on Server_A is REG_DWORD 0x00000002 (2) Looks like you are on to something. I will schedule another test failover. I assume a 2 is mixed mode? If so, why would SQL allow two different modes
on each side of a cluster?
You definitely have a registry replication issue, or at the very least a registry that isn't in sync with the cluster. This could happen for various reasons, none of which we'll probably find out about now, but never the less...
A good test would be to set it to windows only on Node A, wait a minute and then set it to Windows Auth and see if that replicates the registry setting across nodes correctly - this is actually the windows level and doesn't have anything to do with SQL Server.
SQL Server reads this value from the registry and it is not stored inside any databases (read, nothing stored in the master database) as such it's a per machine setting. Since it's not set correctly on Node B, when SQL server starts up it correctly reads
that registry key and acts on it as it should. The culprit isn't SQL Server, it's Windows Clustering.
Hopefully this makes a little more sense now. You can actually just edit the registry setting to match Node A and fail over to B, everything should work correctly. It doesn't help you with a root cause analysis which definitely needs to be done as who knows
what else may not be correctly in sync.
Sean Gallardy | Blog |
Twitter

Disaster recovery in SQL 2005 - which one is better ?

Hi All,
i am in a slight confusion of implementing a DR solution for one of my banking client. They have a citrix application which depends on a sql server. they cannot have a down time more than 15 mins for that application...They want the DR database to come up in less than 15 mins and i am in a slight confusion which DR solution to go with...
I had ruled out Clustering as the client is not willing to bear the cost of it. I also ruled out database mirroring as we failed to get the required performance benchmark with synchronous mirroring with RTT of 167 ms
I am in confusion whether to go with log shipping or replication. if i am going with replication which should i go for.
Could anybody please help me to get a better solution ?
My environment is Windows 2003+ SQL 2005 Standard edition
Regards
Nimesh

Hi All,
i am in a slight confusion of implementing a DR solution for one of my banking client. They have a citrix application which depends on a sql server. they cannot have a down time more than 15 mins for that application...They want the DR database to come up in less than 15 mins and i am in a slight confusion which DR solution to go with...
I had ruled out Clustering as the client is not willing to bear the cost of it. I also ruled out database mirroring as we failed to get the required performance benchmark with synchronous mirroring with RTT of 167 ms
I am in confusion whether to go with log shipping or replication. if i am going with replication which should i go for.
Could anybody please help me to get a better solution ?
My environment is Windows 2003+ SQL 2005 Standard edition
Regards
Nimesh
Hmm , log shipping restores log backups on standby on a regular schedule and if primary server failed then there maybe a loss of data from the last time a log backup happend , does your application tolerate that ?
Also bringing the standby server online needs manual intervention and this can vary so not sure if you can handle in 15 minutes. You may need to copy left over log backups and restore them manually.
Replication supposed to deliver data in near real-time to subscribers if configured as continuous distribution but in you case you will have to publish all tables so that subscriber gets everything as publisher (production).
Transactional replication provides the lowest latency and is usually used for high availability. however , if DB Mirroring failed your benchmark then you need to test replication as well as tables will be scanned for transactions marked for replication and may present an activity.
Also , better to use remote distributor in that case , a cost you should consider. Very important too is that replication maintenance is way more complicated than Db mirroring or Log shipping
You can read also here an overview and then maybe feedback more about your situation
http://msdn.microsoft.com/en-us/library/ms151244%28SQL.90%29.aspx
HTH
Please mark as answer if you think this answers your questions

Metric collection Error MS SQL 2005 Backup

Hi ,
become on all "german !!! ' ms sql 2005 Server a collection error for the backup. I have install the newest ms sql plug-in .I have Grid Control 10.2.0.5
the german error Message is :
WARN collector: <nmecmc.c> Error exit. Error message: Error Querying:Bei der Konvertierung eines char-Datentyps in einen datetime-Datentyp liegt der datetime-Wert auÃŸerhalb des gÃ¼ltigen Bereichs.
com.microsoft.sqlserver.jdbc.SQLServerException: Bei der Konvertierung eines char-Datentyps in einen datetime-Datentyp liegt der datetime-Wert auÃŸerhalb des gÃ¼ltigen Bereichs.
     at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown Source)
     at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
     at oracle.sysman.mpi.jdbc.microsoft_sqlserver_database.SQLServerJDBCQuery.executeQuery(SQLServerJDBCQuery.java:263)
     at oracle.sysman.mpi.jdbc.microsoft_sqlserver_database.SQLServerJDBCQuery.main(SQLServerJDBCQuery.java:1152)
this mean that he have problems to convert char to datetime . But why ?
On my English Server i habe no Problems with this collection.
And NO , i can't only install English MS SQL Server . This is a Company Policy .
Where the error of the collection ?
Thx

and one more:
Cant find the key : SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Replication\\IsInstalled D:\OracleHomes\agent10g/sysman/admin/scripts/emx/microsoft_sqlserver_database\execmethod_32bit is_remote_login=0 namespace=root\default class=StdRegProv "sSubKeyName=SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Replication" sValueName=IsInstalled method=GetDWORDValue noprint=0 em_result=0 SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\Replication IsInstalled

Browse Data & Parameter flds no longer fully populated after upgd SQL 2005

I upgrade our SQL 2000 Server last weekend to SQL 2005 (sp2).
Now our Crystal reports that access SQL data are not working correctly. Parameter Fields are showing little to no data, where before the upgrade we were seeing many more rows in the list.
Digging further, I looked at the fields used for the dynamic LOV. If I use Browse Data on those fields I am seeing the same lack of data. One "Browse Data" that would typically return 80 items now returns 3 items. In that report the data field is DateTime. In another report, the field is string.
I am also seeing an extra check for User Name and password before getting to the Enter values screen for the parameter.
I am using Crystal Developer 11.0.0.1994. It is happening on multiple PCs. I tried with both the original SQL ODBC Driver and the newer SQL Native Client ODBC driver, with the same result.
I've looked at this for 3 days with no luck. Any ideas?

Full SysAdmin rights.
I use a dedicated ODBC connection and have tried both "SQL Server" odbc driver and "SQL NativeClient" (2005) odbc driver.
If I go to Crystal, to the Field Explorer, to the one of the fields, right-click and "Browse Data..." I get two results (I expect 82 results and have seen that in the past.) If I paste the query from Crystal, Database, "Show SQL Query.." to SQL Server Management Studio, I see the full, correct results.
In one example the field browsed is called "PeriodEndDate" (DateTime). A dynamic Parameter Field was created accessing this field. Here is the security curiosity...refreshing now asks for the user login each time "Prompt for new parameter values" is selected. It used to ask only the first time. The Crystal: Data Explorer" shows the current connection logged in ok.
The two issues may or may not be related. Certainly if #1 were fixed, dynamic parameters would return the correct results. Even if it asked for the password each time.
1.) "Browse Data" returning a smaller result than normal.
2.) "Parameter Prompt" asks for Server Name, Database Name, User Name, and Password on
each refresh selecting "Prompt for new parameter values".

Dsml and SQL 2005 reporting services?

I usually post over in the IDM forum so be nice to the newbie here :)
I have a Sun Directory server that I've enabled DSML on. On that side everything is good. However, ideally I want to pull this data into a MS SQL 2005 reporting services report. They have support for XML and web services, but the DSML front end doesn't accept GET requests and I don't know how to send the request as post in reporting services.
Has anyone else be able to get something like this working?
Thanks!

No idea about MS SQL, but is your reporting service able to use files on disk? If so I guess your problem is easily solved by using an app to fetch data from directory server to disk. If you're more adventerous, you write a script in perl/python which acts as a proxy and translates GET requests to POST and relays data back in real time. Not sure if these help or not, just my thoughts.

SAP IDES ECC5.0 (SQL 2005 Database) installation Error at Database instan.

At the time IDES ECC 5.0 installation (SQL 2005 database), I was copy all DVD on Hard drive and start setup then at installation of database instance, following Errors are occured. so I cant continue with the installation, if anyone have installation guide/or solve the following error please mail me at [email protected]
from Log file SAPCLUST
Interface access functions from dynamic library dbmssslib.dll loaded.myCluster
(3.5.Imp): 613: error when retrieving table description for physical table AABLG.
myCluster (3.5.Imp): 614: return code received from nametab is 32
myCluster (3.5.Imp): 296: error when retrieving physical nametab for table AABLG.
(CNV) ERROR: code page conversion failed
rc = 2
from sappool.log
Interface access functions from dynamic library dbmssslib.dll loaded.failed to read short nametab of table ARCH_NUM (rc=32)conversion failed for row 0 of table VARKEY = ⁘
(CNV) ERROR: code page conversion failed
So please send me solution/ or any configuration need for SQL 2005 / installation guide thanks

This may be hard disk problem, some file not able to write on HDD.
Regards
Rajnish

SQL 2005 will not connect in SQL 2012 profiler

We have a few SQL 2005 databases that we manage. I went to do a trace on them(recently upgraded to 2012) and it gives me the error, "SQL Server Native Client 11.0 does not support connections to SQL Server 2000 and earlier versions".
According to MSDN it does. https://msdn.microsoft.com/en-us/library/cc280356(v=SQL.110).aspx
"SQL Server Native Client 11.0 supports connections to SQL Server 2005, SQL Server 2008, SQL Server 2008
R2, SQL Server 2012, and Windows Azure SQL Database."
Any clue why it wouldn't let me connect?

Can you specify the following parameter in the "connect to server" dialog when you load the Profiler --> click on "options" button and go to "Additional Connection Parameters" tab and paste the following?
DataTypeCompatibility=80
Satish Kartan www.sqlfood.com

Database connection to MS SQL 2005 (URGENT Help Needed)

Hi all,
Does anyone know how to connect my adobe form to MS SQL 2005?
I have this code:
try {
     InitialContext initialContext = new InitialContext ();
     DataSource dataSource = (DataSource) initialContext.lookup ("jdbc/MyAlias");
      java.sql.Connection connection = dataSource.getConnection ();
} catch (SQLException e) {
     // handle exception
} catch (NamingException e) {
// handle exception
Other than these, what else do i need to do inorder to get my database connection up?
And after my database connection is up, how do i test to check if my database connection is up or not?
How do i extract the information from the database and put them onto the textfields/dropdownlists on my form?
Thanks In Advance

Hi Mel,
After implementing the codes and modifying them, some of them are underlined, why is this so? =X
Or are u willing to exchange msn so i could send u the screenshot instead?
Thanks In Advance
(Sorry im not that good in this)
(I shall underline the areas which represents the red underline in my web dynpro)
     //Code for database connection.
       InitialContext ctx = new InitialContext();
       DataSource ds = (DataSource)_ctx.lookup("jdbc/JXDataSource");_
       Connection conn = ds.getConnection();
       Statement st = null;
       ResultSet rs = null;
       IPrivateDetailed_Claims_FormView.IFillDataElement dataEle = null;
       st = conn.createStatement();
     //     Execute the appropriate SQL query
       rs = st.executeQuery("SELECT NAME WHERE VENDORCODE='9000116L' ");_
       while (rs.next())       {
     //     Code that will populate your VN based on the data obtained in the ResultSet.
       dataEle = wdContext.createFillDataElement();
       dataEle.setName(_rs.getString(1)_);
      // dataEle.setAge(rs.getInt(2));
      // dataEle.setAddress(rs.getString(3));
       //wdContext.nodeFillData.addElement(dataEle);
       // Close the connections
       rs.close();
       st.close();
                  conn.close();
Edited by: JingXuan Lim on Jan 25, 2008 4:59 AM
Edited by: JingXuan Lim on Jan 25, 2008 5:00 AM

ERP 6.0 on MS SQL 2005 not start

Hello.
System ERP 6.0
OS: Win2003
DB: MS SQL 2005
Try startup SAP System, but dispatcher stopped.
Work process are died...
In wp00 log next:
M Wed Dec 10 15:42:32 2008
M calling db_connect ...
C Thread ID:1860
C Thank You for using the SLOLEDB-interface
C Using dynamic link library 'E:\usr\sap\E01\DVEBMGS00\exe\dbmssslib.dll'
C dbmssslib.dll patch info
C    patchlevel   0
C    patchno      144
C    patchcomment MSSQL: ODBC fastload on separate connection (1131805)
C np:(local) connection used on STG-PTP-R3
C CopyLocalParameters: dbuser is 'e01'
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C Provider Release:9.00.2047.00
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C OpenOledbConnection: line 23715. hr: 0x8000ffff Communication link failure
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 233, sev 0), Communication link failure
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 233, sev 0), Named Pipes Provider: РЎ РѕРu00B1РѕРёСu2026 РєРѕРЅСu2020РѕРІ РєРu00B0РЅРu00B0Рu00BBРu00B0 РѕСu201AСЃСѓСu201AСЃСu201AРІСѓСЋСu201A РїСЂРѕСu2020Рu00B5СЃСЃСu2039.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C OpenOledbConnection: line 23715. hr: 0x8000ffff Communication link failure
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 233, sev 0), Communication link failure
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 233, sev 0), Named Pipes Provider: РЎ РѕРu00B1РѕРёСu2026 РєРѕРЅСu2020РѕРІ РєРu00B0РЅРu00B0Рu00BBРu00B0 РѕСu201AСЃСѓСu201AСЃСu201AРІСѓСЋСu201A РїСЂРѕСu2020Рu00B5СЃСЃСu2039.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C OpenOledbConnection: line 23715. hr: 0x8000ffff Communication link failure
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 233, sev 0), Communication link failure
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 233, sev 0), Named Pipes Provider: РЎ РѕРu00B1РѕРёСu2026 РєРѕРЅСu2020РѕРІ РєРu00B0РЅРu00B0Рu00BBРu00B0 РѕСu201AСЃСѓСu201AСЃСu201AРІСѓСЋСu201A РїСЂРѕСu2020Рu00B5СЃСЃСu2039.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C failed to establish conn. 1
B ***LOG BY2=> sql error -1     performing CON [dbsh#2 @ 1204] [dbsh    1204 ]
B ***LOG BY0=> Communication link failure [dbsh#2 @ 1204] [dbsh    1204 ]
B ***LOG BY2=> sql error -1     performing CON [dblink#5 @ 431] [dblink 0431 ]
B ***LOG BY0=> Communication link failure [dblink#5 @ 431] [dblink 0431 ]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1440]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10468]
What's it mean?
I have a little experience with SQL Server...

Hi,
Is this a new installation, if so is it started all fresh or from upgrade.
If this is not new installation what are the activities executed that has affected the database, i feel no process on other end of pipe which was something related to non-existence of shadow process at database level for the process from SAP.
See also the amount of free space available and what was the LOG file size since this grow enormously in MSS.
Go thru the links
[http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3940600&SiteID=17]
[http://blogs.msdn.com/sql_protocols/archive/2006/07/26/678596.aspx]
have you installed the MSSQL supportpacks provided by SAP along with MSSQL database, i feel problem in database installation, this DB is not tuned in accordance to SAP.
Regards....
Edited by: Sita Rr Uppalapati on Dec 11, 2008 8:31 PM

SQL 2005 Replication

Similar Messages

Maybe you are looking for