SQL Server 2005 - Possible Replication Related Error

hey all,
I was setting up a replication job on a server. I was setting up the publisher end. I used the wizard to create a scheduled job to do a snapshot of one of our databases.
I completed the wizard and clicked Finish. The progress window appeared and it appeared to get hung on step one of the process (Adding articles). I killed the job via Task Manager. This was at 2:11 pm.
At about 3:30 pm, the server started to become very slow. I brought up Performance Monitor and the Pages/sec was maxed out. CPU usage was at 11%. Memory consumption was at about 50% of total memory.
The issue did not clear up and we had to bring the server down and restart it to clear up the issue. This was at 4:00pm.
Looking at the error logs, there is a warning for stopping the replication publisher job and removing it. Then there is an error message regarding a "deactivated schedule 41". Then errors from bringing the server down.
I'm wondering if it is possible for the replication publisher job that I killed to have kept running in the background gobbling up resources. I've done a search of the internet and several forums and I've found nothing conclusive.
screen shot of the error logs but I can't insert it yet until my account is verified.

It is probable that there is an open transaction you will need to kill. Issue a call to dbcc opentran in your publication database and evaluate any open spids to see if you can kill them.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Similar Messages

SQL Server 2005 and JDBC-relation

Hi, i use a SQL-Server 2005 database for my Java App (with Hibernate) and i configure the DB with SQL Server Management Studio Express. I have created several tables with foreign key-relationships, but i have now the question, whether i can define new relationships (many-to-one, etc.) in my hibernate-files (*.hbm.xml, etc,) and use them in my classes WITHOUT defining them with the SQL Server Management Studio Express??
Thanks
H.

hansmaus wrote:
Hi, i use a SQL-Server 2005 database for my Java App (with Hibernate) and i configure the DB with SQL Server Management Studio Express. I have created several tables with foreign key-relationships, but i have now the question, whether i can define new relationships (many-to-one, etc.) in my hibernate-files (*.hbm.xml, etc,) and use them in my classes WITHOUT defining them with the SQL Server Management Studio Express??
Thanks
H.If you have the Java objects and the mapping (either in .hbm.xml or annotations) you can use the <property name="hbm2ddl.auto">create</property> in your hibernate.cfg.xml to have Hibernate generate the schema for you.
But, as jschell implies, one way or the other you have to end up with tables.
%

SQL Server 2005 installation after VS 2005 installation

I saw in another thread that someone had trouble installing SQL Server 2005 after installing Visual Studio 2005. The answer alluded to the fact that the default/standard installation of VS 2005 results in the installation of SQL Server Express at the same time.
I installed Visual Studio 2005 Professional on my PC already, and am about to install SQL Server 2005 Developer edition. Is there any way to know now (before installing SQL Server) that something will cause an installation issue? I would like to do whatever I can to prevent problems in advance, so is there anything I can / should to before installing SQL Server?

I did not mention in my previous post that after much reading in help forums and treading on proverbial eggshells (hoping I was doing things correctly to ensure good installation of purchased products thereafter), I recently uninstalled/removed several beta versions of Visual Studio and SQL Server from my personal/home PC (O/S: Windows XP Media Center Edition Version 5.1, build 2600, SP2). I have already jumped over the "uninstall wall" several times to get to this point. That is why I am proceeding with caution, to avoid any more torture; I would prefer to do the right thing (even though I've apparently already started down the wrong path) to avoid any more headaches.
I was unsure at first, but went in search of logs and registry entries to see if SQL Express was installed, and am now fairly sure it was, because of 4 items I found:
1)   In C:\Program Files\Microsoft Visual Studio 8\Microsoft Visual Studio 2005 Professional Edition - ENU\Logs\dd_vsinstall80.txt:
[04/29/08,13:10:53] Microsoft SQL Server 2005 Express Edition x86: e:\setup\..\wcu\sse\SQLEXPR32.EXE exited with return value 0
[04/29/08,13:10:53] InstallReturnValue: GFN_MID SSE x86, 0x0
[04/29/08,13:10:53] Microsoft SQL Server 2005 Express Edition x86: Error code 0 for this component means "The operation completed successfully."
2) In: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\
SQLSetup0006_D8GKLNB1_SQL.log:
MSI (s) (34:88) [13:10:15:218]: Product: Microsoft SQL Server 2005 Express Edition -- Installation completed successfully.
3) Add/Remove Programs shows “Microsoft SQL Server 2005” is on my machine (although “Express” is not part of the name). Also listed are: Microsoft SQL Server Native Client, Microsoft SQL Server Setup Support Files (English), Microsoft SQL Server VSS Writer, MSXML 6.0 parser
4) Searching for InstallDate in regedit: HKLM|Software\Microsoft\Windows\CurrentVersion\Intaller\UserData\5-1-5-18\Products\7DDFFFA258DE09A4C
DisplayName                Microsoft SQL Server 2005 Express Edition
            InstallDate                    same date as Visual Studio 2005 installation
            InstallSource                 l:\f58e49f47a1d350886021c2b2dd1\Setup\
So now I would like to know what the best course of action is to remedy this with the least amount of aggravation.  Is it possible to just use A/R programs to uninstall the components of SQL Server 2005 (Express) that interfere with installation of SQL Server 2005 Developer edition? Would those be the workstation components?

Reading BLOB from SQL Server 2005 using DB Link from Oracle 10g

Hi All,
I am trying to read a table's data from SQL Server 2005 using ODBC DB Link created in Oracle 10g (10.2.0.3/4) database. I am not using oracle gateway.
I am able read all data except for the BLOB data from SQL server 2005. It gives error given below when I try to execute query SELECT * from T_TRANSACTION_DATA@sdeslink inside a stored procedure:
ORA-22992: cannot use LOB locators selected from remote tables
Kindly help how to read BLOB from SQL server 2005 inside Oracle 10g.
Best Regards!
Irfan

Irfan,
If you can read the blob data using 10.2 HSODBC then there should be no problem using the 11g gateway.
I recommend you download the latest version which is 11.2.0.3 available from My oracle Support as -
Patch 10404530: 11.2.0.3.0 PATCH SET FOR ORACLE DATABASE SERVER
This is a full version and does not need a previous version to have bene installed. When installing it needs to be in a completlely separate ORACLE_HOME from the existing 11.2 install.
For the Ora-22992 problem have a look at this note in My Oracle Support -
Ora-22992 has a workaround in 10gR2 (Doc ID 436707.1)
Regards,
Mike

Replication Error in Goldengate SQL Server 2005 to Oracle.

Dear All
SQL Server 2005 is my source database and oracle is my destination database when i run my param file at source side following error occur.Kindly suggest the solution.
ERROR OGG-00146 VAM function VAMInitialize returned unexpected result:
error 600 - VAM Client Report <MSSqlVam: (1) At least one option of type MANAGESECONDARYTRUNCATIONPOINT
needs to be specified for TRANLOGOPTIONS (DSOPTIONS)>.

The GoldenGate forum is over here:
GoldenGate
(question is somewhat old, but unanswered)
SQL Server setup - you have to choose one of two options for the truncation point and the transaction log:
If the Extract process is running against a SQL Server 2005 source, use the TRANLOGOPTIONS
parameter to control whether Extract or SQL Server maintains the secondary truncation
point. This is a required parameter and must contain one of the following options:
SQL Server replication maintains the truncation point
Use TRANLOGOPTIONS with the NOMANAGESECONDARYTRUNCATIONPOINT option if Extract and
SQL Server 2005 replication or a third-party replication program will be running at the
same time for the same database.
Oracle GoldenGate maintains the truncation point
Use TRANLOGOPTIONS with the MANAGESECONDARYTRUNCATIONPOINT option if Extract and SQL
Server 2005 replication or a third-party replication program will not be running at the
same time for the same database.
See page 29 in the SQL Server setup and installation guide

Error when upgrading from SQL Server 2005 to SQL Server 2014

Hello everyone,
Could you help me, i have an error when i try to upgrade my SQL Server 2005 Enterprise Edition to SQL Server 2014 Enterprise Edition,
All of prerequisits are available and i dont have a problem,
before the end of migration process, i have this error: The group name could not be found (0x84BB0001)
File log:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this
command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,FULLTEXT,REPLICATION. Then, run SQL Server Setup again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84BB0001
Error description: The group name could not be found.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x0AD059E6%400x3FAAA006&EvtType=0x0AD059E6%400x3FAAA006
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this
command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,FULLTEXT,REPLICATION. Then, run SQL Server Setup again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84BB0001
Error description: The group name could not be found.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x0AD059E6%400x3FAAA006&EvtType=0x0AD059E6%400x3FAAA006
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this
command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,FULLTEXT,REPLICATION. Then, run SQL Server Setup again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84BB0001
Error description: The group name could not be found.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x0AD059E6%400x3FAAA006&EvtType=0x0AD059E6%400x3FAAA006
Best regards,
Guiga Hafedh

There are more detailed logs for the various components. The one of interesting is the one for the engine or possibly the one for full-text.
These logs are extremely verbose, and the errors are rarely crystal clear, but at least give them a try. If you have problems, find a place to upload them (Dropbox, Skrydrive etc), so that we can look.
The closest at hand is that "group" that cannot be found is an AD group.
Erland Sommarskog, SQL Server MVP, [email protected]

Error when calling a XI-webservice from SQL-Server 2005

Hi all,
we have published a webservice with XI 7.0 (using the SOAP-Adapter) and try to call it from a stored procedure within SQL-Server 2005. Upon execution we receive the error
"<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>" and
"<SAP:Stack>Empty HTTP query received; message processing not possible </SAP:Stack>".
We are using the dll MSXML2.ServerXMLHTTP. The webservice is available and can be reached from other tools like SOAP-UI when using the same endpoint-URL. It is also possible to call the service from Visual-Basic using the same code.
Does anyone has any clue about what's causing this error?
Thanks in advance!

It is clear that, PI service is working absolutely fine and the problem is calling it in your SP. I do not think you are calling a web service but actually sending a HTTP request to the server. An HTTP request and a SOAP call are different in terms of protocol. You would need to explore more on how to call web services from SQL SPs.. and the right place to search would be MS SQL Server Forums..!!
VJ

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

Error deploying JDBC driver for SQL Server 2005

Hi all
I'm trying to deploy a JDBC driver for MS SQL Server 2005 (downloaded [here|http://www.microsoft.com/downloads/details.aspx?familyid=C47053EB-3B64-4794-950D-81E1EC91C1BA&displaylang=en]). When I try to deploy it according to the instructions found [here|http://help.sap.com/saphelp_nwce10/helpdata/en/51/735d4217139041e10000000a1550b0/frameset.htm] it fails.
The error in the logs doesn't give any useful information though. It only says Error occurred while deploying component ".\temp\dbpool\MSSQL2005.sda".
Has anyone else deployed a driver for SQL Server 2005, or perhaps have any suggestions of what else I could try?
Thanks
Stuart

Hi Vladimir
That's excellent news! Thanks for the effort you've put into this. I'm very impressed with how seriously these issues are dealt with, specifically within the Java EE aspects of SAP.
May I make two suggestions on this topic:
1. Given that NWA has such granular security permissions, please could the security error be shown when it is raised? This would help immediately identify that the problem isn't actually a product error, but rather a missing security permission (and thus save us time and reduce your support calls).
2. Please could the role permissions be clearly documented (perhaps they already are, and I just couldn't find the docs?) so we know what is and isn't included in the role. The name is very misleading, as a "superadmin" is generally understood to have no limitation on their rights - so clear documentation on what is in-/excluded would be most helpful.
On a related topic, I came across another issue like this that may warrant your attention (while you're already looking into NWA security issues). I logged a support query about it (ref: 0120025231 0000753421 2008) in case you can retrieve details there (screenshots, logs, etc.). It's basically a similar security constraint when trying to create a Destination. I'm not sure if this is something you would like to include as standard permissions within the NWA_SUPERADMIN role or not, but I think it's worth consideration.
Thanks again for your help!
Cheers
Stuart

Replication Configuration issue after migrating from SQL Server 2005 to SQL Server 2008 R2

Hi All,
This weekend we have migrated one of our Core system from SQL Server 2005 SP3 to SQL Server 2008 R2 SP2. Migration went successful. However when we are trying to Configure transaction replication we are getting below Error:
Msg 21854, Level 16, State 1, Procedure sp_MSrepl_addarticle, Line 573
Could not add new article to publication 'abc' because of active schema change activities or a snapshot is being generated.
Background:
Database compability Changed from 90 to 100.
A quick Help would be appreciated.
Best Regards - Viral
Thanks - Viral

Is a snapshot being generated? the message seems to indicate one is.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Error when opening BIDS 2005 - SQL Server 2005 - Urgent to solve

Hi,
today I've a problem when I try to launch the BIDS 2005: an error message says that isn't possible to find a component and says to reinstall the application. I cannot any records inside the event viewer that could help me. The SQL Server 2005 build is 9.00.5069.00.
BIDS 2005 is installed on my machine that has Windows 7 64-bit. Moreover I've also SQL Server 2008 R2 and BIDS 2008 R2: I cannot open also this tool for the same error.
Any suggests to me, please?
Thanks

Hi Pscorca,
According to your description, you cannot start Business Intelligence Development Studio (BIDS) in SQL Server 2005 and 2008 with the error "isn't possible to find a component and says to reinstall the application". As per my understanding, the issue
can be caused by some SQL Server files were corrupted. It's hard to give you the root reason that cause this issue based on the limited information.
In your scenario, please drive the BIDS installation folder (C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft SQL Server 2008 R2), try to open BIDS and check if this issue persists or not. Besides, you can try to repair SQL Server
installation using stepup.exe.
Hope this helps.
Regards,
Charlie Liao
TechNet Community Support

Error"Failed to open the connection" - Named Instance of SQL Server 2005

"Failed to open the connection" error, when connecting to the Named Instance of SQL Server 2005
The report is throwing error, when changing the logon information dynamically through C#.
Code
     string reportPath = @"D:\NET\TestReport\TestReport.rpt";
     ReportDocument reportDocument = new ReportDocument();
     reportDocument.Load(reportPath);
     foreach(CrystalDecisions.CrystalReports.Engine.Table table in tables)
          TableLogOnInfo tableLogonInfo = table.LogOnInfo;
          tableLogonInfo.ConnectionInfo.ServerName = @"TestServer\Instance1"; //Connnecting to Named instance of SQL Server 2005
          tableLogonInfo.ConnectionInfo.UserID = "sa";
          tableLogonInfo.ConnectionInfo.Password = "password";
          tableLogonInfo.ConnectionInfo.DatabaseName = "TEST_DB";
          table.ApplyLogOnInfo(tableLogonInfo);
     crystalReportViewer1.ReportSource = reportDocument;
Error Message
     Failed to open the connection.
     Failed to open the connection.
     C:\DOCUME1\PUGALE1\LOCALS~1\Temp\{DF9593A5-5C80-4CBC-ABC3-EC4EF204A7EB}.rpt
The error is occuring only whenever i am connecting to the Named Instance of SQL Server 2005.
Thanks in Advance
Edited by: pugalendran p on Feb 2, 2009 10:32 AM
Edited by: pugalendran p on Feb 2, 2009 10:43 AM

Hi,
Following solution might help you to resolve the issue.
Solution1:
Issue happens because universe connection to the Database is not responding and the Data Source Name is not configured to write SQL Server 2005 database.
Resolution
Created new DSN connection under SYSTEM DSN to SQL Server 2005 Database.
Import the universe from the designer.
Go to File->Parameters.
Edit Connection.
On the Database Middleware Page expand SQl Server 2005->Select SQL Server 2005 driver.
Change the DSN to new DSN connection
Test the connection.
Save the Universe and Export it to the repository.
Solution2:
I am taking Oracle as an example over here.
This can be caused when the SQLNET.ora is located in a remote location using mapped drives.
Resolution
To resolve,
check the registry [HKLM\SOFTWARE\ORACLE] you should see a folder called HOME0
look for any paths that contain a mapped drive partition
Change the mapped drive letter to a UNC path (
server\folder)
Open a command prompt and do a tnsping using the tnsname and verify the location of the SQLNET.ora or TNSNAMES.ora
If the path is not updated to the new path
Reboot the server
Regards,
Sarbhjeet Kaur

Error while installing SQL Server 2005 SP3

I have installed SQL Server 2005 Standand Edition (32-bit) on a standalone server machine running
Windows Server 2003 R2 Standard 64-bit with Service Pack 2. After installing SQL Server, when I tried installing the Service Pack 3 (as per application requirement) through local administrator account, I am repeatedly getting below error in
"C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_SqlSupport.msi.log"
SECUREREPAIR: SecureRepair Failed. Error code: 4ec4E6A3388
MSI (s) (F8:40) [16:49:33:515]:
Error 1260. Windows cannot open this program because it has been prevented by a software restriction policy.
I have checked rights on the folders and also got the anti-virus (symantec) services stopped on the server. Still no success, can anyone help.

I have installed SQL Server 2005 Standand Edition (32-bit) on a standalone server machine running
Windows Server 2003 R2 Standard 64-bit with Service Pack 2. After installing SQL Server, when I tried installing the Service Pack 3 (as per application requirement) through local administrator account, I am repeatedly getting below error in
"C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_SqlSupport.msi.log"
SECUREREPAIR: SecureRepair Failed. Error code: 4ec4E6A3388
MSI (s) (F8:40) [16:49:33:515]:
Error 1260. Windows cannot open this program because it has been prevented by a software restriction policy.
I have checked rights on the folders and also got the anti-virus (symantec) services stopped on the server. Still no success, can anyone help.
Just to add: Have already referred
http://support.microsoft.com/kb/918357

Error 1406 while installing SQL server 2005 on windows 2003 64 bit standard

Hi Gurus,
When I am trying to install SQL SERVER 2005 on Windows Serevr 2005 i get the error code 1406
I tried using the script sql4sap.vbs. and tried to set the named instance.
please suggest
Please find the contents of the Summary.txt
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version      : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Time            : Mon Apr 14 14:51:07 2008
Machine         : UKSAPTEST02
Product         : .NET Framework 2.0
Product Version : 2.0.50727
Install         : Failed
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST02_.NET Framework 2.0.log
Last Action     : InstallFinalize
Error String    :Could not write value to key \Software\Classes\.appref-ms
Error Number    : 1406
UKSAPTEST02 : There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time            : Mon Apr 14 14:52:26 2008
List of log files:
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST02_Core.log
Many thanks
Sreeram
Edited by: sreeram kaki on Apr 14, 2008 6:12 PM

Hi Clas,
Thanks for the valuable suggestions,
I tried to install the database (sql server 2005) using the local admin password on another server which do not have the antivirus installed. I started the installation at 3:15 PM today and the installation is still in progerss
please see the log below from Summary.txt.
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version      : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Time            : Tue Apr 15 15:04:28 2008
Machine         : UKSAPTEST01
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLSupport_1.log
Machine         : UKSAPTEST01
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLNCLI_1.log
Machine         : UKSAPTEST01
Product         : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SqlWriter_1.log
Machine         : UKSAPTEST01
Product         : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_MSXML6_1.log
Machine         : UKSAPTEST01
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLSupport_2.log
Machine         : UKSAPTEST01
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLNCLI_2.log
Machine         : UKSAPTEST01
Product         : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_BOL_1.log
Machine         : UKSAPTEST01
Product         : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_MSXML6_2.log
Also see the last few lines of the log file
SQLSetup0001_UKSAPTEST01_SQL.log
Action start 17:10:43: Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!50) [17:10:43:815]: PROPERTY CHANGE: Deleting Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '1 0 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
Action ended 17:10:43: Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<Func Name='ScheduleActionX'>
<Func Name='SetCAContext'>
MSI (s) (C0!50) [17:10:43:815]: PROPERTY CHANGE: Adding Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its value is '1 1 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
MSI (s) (C0!50) [17:10:43:815]: Doing action: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Action start 17:10:43: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!50) [17:10:43:830]: PROPERTY CHANGE: Deleting Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '1 1 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
Action ended 17:10:43: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<EndFunc Name='Write_sqlGroupMember' Return='0' GetLastError='0'>
PerfTime Stop: Write_sqlGroupMember : Tue Apr 15 17:10:43 2008
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (C0:F0) [17:10:43:830]: Doing action: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
Action ended 17:10:43: Write_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
MSI (s) (C0:50) [17:10:43:830]: Invoking remote custom action. DLL: C:\WINDOWS.0\Installer\MSI1D8.tmp, Entrypoint: Write_sqlUserSecurity
Action start 17:10:43: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
<Func Name='LaunchFunction'>
Function=Write_sqlUserSecurity
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Write_sqlUserSecurity
PerfTime Start: Write_sqlUserSecurity : Tue Apr 15 17:10:43 2008
<Func Name='Write_sqlUserSecurity'>
<Func Name='ScheduleActionX'>
<Func Name='SetCAContext'>
MSI (s) (C0!34) [17:10:43:924]: PROPERTY CHANGE: Adding Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its value is '0 1 0 Setting User Security 50000 SQLServer2005SQLBrowserUser$UKSAPTEST01 SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeChan
MSI (s) (C0!34) [17:10:43:924]: Doing action: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Action start 17:10:43: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!34) [17:10:43:924]: PROPERTY CHANGE: Deleting Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '0 1 0 Setting User Security 50000 SQLServer2005SQLBrowserUser$UKSAPTEST01 SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$
Action ended 17:10:43: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<EndFunc Name='Write_sqlUserSecurity' Return='0' GetLastError='0'>
PerfTime Stop: Write_sqlUserSecurity : Tue Apr 15 17:10:43 2008
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (C0:F0) [17:10:43:940]: Doing action: Write_sqlFileSDDL.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
Action ended 17:10:43: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
MSI (s) (C0:10) [17:10:43:940]: Invoking remote custom action. DLL: C:\WINDOWS.0\Installer\MSI1D9.tmp, Entrypoint: Write_sqlFileSDDL
Action start 17:10:43: Write_sqlFileSDDL.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
<Func Name='LaunchFunction'>
Function=Write_sqlFileSDDL
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Write_sqlFileSDDL
PerfTime Start: Write_sqlFileSDDL : Tue Apr 15 17:10:43 2008
Thanks & Regards,
Sreeram
Edited by: sreeram kaki on Apr 15, 2008 6:45 PM

Error While Installing IDES ECC6 with SQL Server 2005

Dear Experts,
I found an error while installing IDES ECC6 with SQL Server 2005. The error is raising at the stage of 17 of 24 processing the procedure of 195 of 197 (sap_z_set_permissions).
I have tried several times by configuring different type of activites but still i am facing the same problem at the same stage. Please help me in thig regard.
I herewith pasted hereunder log files information
Regards,
B.Sudharsan
ERROR 2008-01-17 18:38:47
FCO-00011 The step ExeProcs with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_MSS|ind|ind|ind|ind|2|0|MssProcs|ind|ind|ind|ind|1|0|ExeProcs was executed with status ERROR .
INFO 2008-01-17 18:40:05
An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_MSS|ind|ind|ind|ind|2|0|MssProcs|ind|ind|ind|ind|1|0|ExeProcs".
ERROR 2008-01-17 18:38:47
MDB-05053 Errors when executing sql command: <p nr="0"/> If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.

Sudarshan,
Occasionally, mid-way through the upgrade, DB permissions to users might change. Check to see, if the users SAP<SID>, OPS$ users have the DBA privilege. Re-assign the role and try continuing with the upgrade.

SQL Server 2005 - Possible Replication Related Error

Similar Messages

Maybe you are looking for