Error in Upgrading to MS SQL 2005

i have Nw2004 installed wiht MS SQL 2000 as database.
Iam in the process of upgrading this server to NW2004s.
As a pre-requisite i upgraded the MS SQL 2000 to MS SQL 2005 Server
But after upgradation of MS SQL only(NW2004 is there) when i start the SAP Instance the SAP Instance is starting.
but when i login to SAP and run any transactions it is giving a message
START_CALL_SICK.
Please let me know whether i can run MS SQL 2005 server with NW2004

hello Balaji,
You can ignore this error. Basically just restart the system. I would say reboot the machine. restart database and then SAP. However before that execute the transaction SICK and look for any errors.If there are any error then you need to solve them. May be you can paste them here. MS SQL 2005 is supported with Netwaeaver 04.
Check this:
https://websmp104.sap-ag.de/platforms
Regards.
Ruchit.
Message was edited by:
Ruchit Khushu

Similar Messages

SQL Upgrade 2000 to SQL 2005

We are upgrading to new server and installing SQL 2005. Using Crystal Server 10. Where can I find a step by step? Can I just backup Business Objects Database, install the app on the new server, restore the database to SQL 2005?
Thanks,
SS

Hi Samuel
You can refer the below link for more information on SQL Server 2005 upgrade.
[http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlupgrd.mspx#top]
Regards
Girish.

SSRS 2012 rendering issue/Enabling Anonymous access - Upgraded SSRS from SQL 2005 to SQL 2012.

Hi,
I just recently upgraded SQL 2005 SSRS to SQL 2012 SSRS. Everything is working great other than small issue.
Sounds like some authentication issue. SQL 2005 SSRS - IIS, we enabled anonymous access and we never had this problem. SQL 2012 SSRS /WIN 2008 R2 - I am not sure how to enable anonymous access.
If anyone can help me on this? I really appreciate your help.
Thanks,
Vel
Vel Thavasi

Hi Vel,
According your description, you want to know how the enable anonymous access to SSRS 2012. Right?
In SSRS 2008 or later version, we are not using IIS any more. If we want to configure the authentication, we need to configure in RSReportServer.config. This file locate at:
<drive>:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer
However, in SSRS 2012, Anonymous authentication is not supported on report server. Please see:
Authentication with the Report Server
In this scenario, we need to custom an authentication type to achieve the "Anonymous" goal. Please refer to the link:
Configure Custom or Forms Authentication on the Report Server
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Upgrade Process from SQL 2005 to SQL 2012

Hi All,
I have gone thru multiple threads and would like to understand some steps in detail for me to upgrade SQL 2005 to SQL 2012.
Below is my understanding and questions around it, I would be setting up a new environment with OS 2007/2008 with SQL 2012:
Environment Readiness - Ensure new environment is ready with Win 2007/2008 with SQL 2012 Server
Run Upgrade Advisor on the new environment and point to SQL 2005 instance
Find the breaking/discontinued changes to be done before or After Upgrade
<Question>: Over here I would like to know what should be our approach to make the required changes
<Question>: Obviously I should not be making changes directly on the Production SQL 2005 server, then in that case should I take a backup/restore on the new SQL Server 2012 and then make the required changes to the database objects
like (Table schema(changing column names/datatypes etc.), Stored Procedure, Functions & Views)
<Question>: When I do a backup/restore I would also get the data along with it, so is this a recommended approach or should we only run/use the table schema creation scripts, fix the issues identified by UA and then do an Table to Table import,
any thoughts on this ?
<Question>: If I have to do a table to table Import then I should ensure there's a downtime during the Import or would I have any other better approach
So, basically my questions are around the approach of fixing the issues identified by UA and moving the database to SQL Server 2012 environment, I have around 300 databased to me upgraded.
Please do let me know what should be a good/proven approach ? Pl. do let me know if you would need any more details from me.
---Umesh

Thanks all for the replies.
I am trying summarize what I have understood here:
Document SQL Server 2005 environment details, Is there any tool which could give us all relevant details
I would take the backup from the SQL Server 2005 Production environment and then restore the same in a test environment which again has SQL Server 2005 and Run Upgrade Advisor on that
Probbaly run SQL Profiler as well to find out the deprecated changes to be done
I should fix all the breaking, discontinued changes on the Test system identified by UA
I should fix all the deprecated changes on the Test system identified by SQL Profiler
Steps 3 & 4 should give me the changed scripts for all database objects (i.e. Table Schema, Stored Procedures, Functions & Views)
<Question> Perform test, I understand this acitivity test can be captured by having SQL profiler running in the background on the SQL Server 2005 production environment where we can identify some days in a week or a month where maximum activity is
expected to ensure we cover most the scenarios, let me know is this approach looks fine or is there a better approach
Now, with regards to acutal upgrade I need to identify a time window where in less activity is done during which I could have a downtime for the actual SQL Server 2005 production environment
Post downtine, I should do a BackUp for all databases from SQL Server 2005 production environment
Test on environment readiness of SQL Server 2012 can be compared against the documentation done as part of the first Step
<Question> Ideally I should a restore first in the new environment which has SQL Server 2012
<Question> Then run the Scripted changes where we fixed all the breaking, discontinued & deprecated changes
<Question> Does above sequence of Step 9 & 10 make sense or is there a better approach of doing it
<Question> Post Upgrade and running of changed scripts, I should run the Upgrade Advisor again and see if everything looks fine
<Question> Perform test again which we ran on SQL Server 2005 Test environment
<Question> These steps should complete the Upgrade process.
Please do let me know if the above sequence look ok to all of you and does it really work in a practical scenario, do let me know your feedback or any change in sequence/process or any other tools that can be used here.
Thanks Again ...

Error in Connecting to MS SQL 2005 via JDBC Driver

Here's the setup
CF MX7 resides on a centOS wid Apache 2.0 webserver box.
I need to established a datasource connection between the
Coldfusion server and a MSSQL 2005 Express+SP1 database sitting on
a remote XP wid SP2 setup.
I've also downloaded and installed on the /lib folder of the
CFMX7 server the corresponding JDBC drivers (versions 1.1 and 1.0)
for the MS SQL server.
The thing is, this problem always occurs:
Connection verification failed for data source:
datasourcename
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
JDBC]Error establishing socket.
The root cause was that: java.sql.SQLException:
[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing
socket.
The datasource connection info is as follows:
CF Datasource Name: datasourcename_JDBCdriver
JDBC URL:
jdbc:microsoft:sqlserver://192.168.0.47:1433;DatabaseName=nameofdatabase
Driver Class: com.microsoft.sqlserver.jdbc.SQLServerDriver
Driver Name: mssql2005
Username: sa
Password: userdefinedpassword
I've already tried these settings:
* Enabled mix mode of authentication under the SQL server
* Affix a /MSSQLSERVER instance name on the jdbc url setting
"jdbc:microsoft:sqlserver://192.168.0.47\MSSQLSERVER:1433;DatabaseName=nameofdatabase"
but a different error had occured:
The root cause was that: java.sql.SQLException:
[Microsoft][SQLServer 2000 Driver for JDBC]The requested instance
is either invalid or not running.
so i remove it since its only an optional setting
* Configured the SQL 2005 Express, under the SQL Server
Configuration Manager, to listen to protocol TCP/IP under port 1433
(this is the ONLY ENABLE protocol)
I've checked using Telnet and netstat and the SQL service is
normally listening to the said port.
* Disabled windows firewall under XP (came with SP2)
and even tried using other JDBC drivers such as:
* macromedia drivers
* jtds driver
but to no avail.
Is the problem still within the MS SQL 2005 Express wid
XP+SP2 box or a connecting issue on the Cf server under the
centOS/Apache machine?
A little help would do wonders just about now.

I had the same problem, but do not have express version. In
the configuration manger, I viewed the properties of the enabled
tcp/ip protocol. On the IP addresses tab, I found that though the
IPs were enabled, the drop down beside active was no. I changed all
to yes, applied it and restarted my instance. Then in the cf
datasource I left the port blank and everything worked.

Error export from my database sql 2005 with Windows 2003 abap+java

Hi all
I'm trying to create an Export from my database sql 2005 with Windows 2003, but SAPINST starts with an error. ABAP+JAVA stack
While running the export preparation, I am getting the following error;
INFO 2010-09-08 12:12:43
Output of C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath D:\usr\sap\BID\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jce.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jsse.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_smime.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_ssl.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/antlr.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/exception.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/jddi.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/logging.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/offlineconfiguration.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/opensqlsta.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SDMutil.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SLUtil.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\base.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\util.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\sqlserver.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\spy.jar -export -type=keydb "-expfile=C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/usages_data.xml" -log=UTL_load_usages.log -sid=BID -dsn=jdbc/pool/BID -ssprops=D:/usr/sap/BID/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/BID/SYS/global/security/data/SecStore.key is written to the logfile C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/UTL.java.log.
WARNING 2010-09-08 12:12:46
Execution of the command "C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath D:\usr\sap\BID\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jce.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jsse.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_smime.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_ssl.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/antlr.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/exception.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/jddi.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/logging.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/offlineconfiguration.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/opensqlsta.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SDMutil.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SLUtil.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\base.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\util.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\sqlserver.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\spy.jar -export -type=keydb "-expfile=C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/usages_data.xml" -log=UTL_load_usages.log -sid=BID -dsn=jdbc/pool/BID -ssprops=D:/usr/sap/BID/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/BID/SYS/global/security/data/SecStore.key" finished with return code 64. Output:
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)
ERROR 2010-09-08 12:12:46
CJS-30071 Execution of UTL tool 'C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath D:\usr\sap\BID\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jce.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_jsse.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_smime.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/iaik_ssl.jar;
JRBIWD/sapmnt/BID/SYS/global/security/lib/tools/w3c_http.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/antlr.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/exception.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/jddi.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/logging.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/offlineconfiguration.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/opensqlsta.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SDMutil.jar;D:/usr/sap/BID/SYS/global/sltools/sharedlib/SLUtil.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\base.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\util.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\sqlserver.jar;D:\usr\sap\BID\DVEBMGS01\exe\mssjdbc\spy.jar -export -type=keydb "-expfile=C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/usages_data.xml" -log=UTL_load_usages.log -sid=BID -dsn=jdbc/pool/BID -ssprops=D:/usr/sap/BID/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/BID/SYS/global/security/data/SecStore.key' aborts due to database connection error with return code 64. DIAGNOSIS: The connection parameters are wrong or the database server is shutdown. SOLUTION: Check 'UTL_load_usages.log' and 'C:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/CENTRAL/AS/PREEXP/UTL.java.log' for more information.
ERROR 2010-09-08 12:12:46
FCO-00011 The step getUsageTypes with step key |NW_Prepare_Export|ind|ind|ind|ind|0|0|NW_Java_Prepare_Export_Dialog|ind|ind|ind|ind|5|0|getUsageTypes was executed with status ERROR .
Could anyone please help me out on this, if possible?
Thanks
JM

Hi,
please ensure that you use a SAP supported JDK as below:
716604 for the Sun JDK (Windows, Linux, Solaris)
709140 Recommended JDK and VM Settings for the WebAS630/640/7.0
And the re try the export pls.
Regards,
Snow

Connect Non-SAP Oracle db (32bit) in sql 2005 (64 bit) using linked server

Hi,
I am connecting Oracle 10g database from SQL 2005 using linked server, in which i get the error
"Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server "L2ORACLE".
OLE DB provider "MSDAORA" for linked server "L2ORACLE" returned message "Oracle client and networking components
were not found. " (Microsoft SQL Server, Error: 7303)
SAP Server with sql 2005 db is in 64 bit server / Windows 2003
Non-SAP Oracle 10g is in 32 bit windows 2003 server.
i have installed Oracle 64 bit client in the SAP Server and also copied the 64 bit version of dboraslib.dll to the DIR_LIBRARY path. I am able to view the oracle tables in the oracle client.
But, when i create the linked server, it gives the above error.
If i install 32 bit version of Oracle client in the SAP Server, i am able to create the linked server in the db level, but, it says "Work Process restarted, session terminated" message in the Z program in SAP.
The same works in the test environment where both are 32 bit servers. problem is when SAP server is in 64 bit and non sap is in 32 bit.
Please suggest.
Thanks and Regards,
Nagu

"Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server "L2ORACLE".
OLE DB provider "MSDAORA" for linked server "L2ORACLE" returned message "Oracle client and networking components
were not found. " (Microsoft SQL Server, Error: 7303)
check the workprocess traces for errors (and/or SM21). It seems that the system is "not aware" that an Oracle client is installed.
64bit programs can´t load 32bit libraries/DLLs that´s why the workprocess dumps when you use the 32bit client.
Markus

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]

SQL 2005 SAP R/3 4.6C - DBSL error RC=99 on import of Basis 4.6C SP 39

Hi,
I have just built a R/3 4.6C system on SQL 2005 with 4.6D_EXT kernel. The build was done using R3load to export from the 4.6C/SQL 2000/32bit system and import to 4.6C/SQL 2005/64bit system. The source 4.6C system only had Basis support package 37 applied, and I am trying to apply Basis 4.6C 38-57 on the 4.6C/SQL 2005/64bit system (in preparation for an ECC6 upgrade) and I get the following error:
EXEC SQL: SELECT ID,OBJECT,LANGU,TYP,VERSION FROM DOKIL WHERE (LANGU IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,
[developertra,00000] ExecuteAndFlush return code: 0x80040e10 Stmt: [CREATE PROCEDURE ##Y8IBASAPDEIBD00000025600000000006164133 @P
 99972 0.099972
[developertra,00000] MapHr:80040E10 DB_E_PARAMNOTOPTIONAL 43 0.100015
[developertra,00000] HandleOledbError [ExecuteAndFlush,line 33423]: Error/Message: (err 0, sev 0), No value given for one or more
 96 0.100111
[developertra,00000] DbSlPrepare - Error 99 (dbcode -2147217904) on proc. creation
56 0.100167
[developertra,00000] DbSlPrepare - <CREATE PROCEDURE ##Y8IBASAPDEIBD00000025600000000006164133 @P000 varchar(3072) = ' ', @P001 v
 105 0.100272
[developertra,00000] 1 times error (0,0) in sequence 30 0.100302
[developertra,00000] dbdsmss: DBSL99 SQL0 27 0.100329
[developertra,00000] No value given for one or more required parameters.
62 0.100391
[dbds ,00589] ***LOG BY2=>sql error 0 performing FET
66 0.100457
[dbds ,00589] ***LOG BY0=>No value given for one or more required parameters.
I have checked the collation setting in SQL 2005 and it is:
select serverproperty('collation')
SQL_Latin1_General_CP850_BIN2
There are 97000 odd entries in DOKIL, so I don't think that is the problem.
Would appreciate any assistance.
Kind regards,
Sheryl.

Hi ,
Instead of doing the build with export import, you can try to do the same with backup restore,,
But remember your sql2000 should be on bin2... then you can take backup and restore.
Since it is from 2000 to 2005 the restore would happen and it will work fine.
Try this and check out, since the error you have pasted is not clearly giving any picture...
Regards,
Ravi.

SQL 2005 Upgrade complete! - Post installation tasks questions!

Hi All
I have managed to upgrade our DEV and TST ECC6 systems to SQL2005 (from SQL2000) and so far all seems ok however I have a a few questions and checks I would like some help with. I have included my post installation tasks at the bottom of this post, so you know what I have done.
I have noticed that when I run SGEN I get a short dump LOAD_VERSION_LOST which I am not sure what this means.
If there is anything else I need to do or should do please let me know.
Thanks
Phil
Post Installation Tasks
SQL Queries
exec sp_configure 'show advanced options', 1
reconfigure with override
exec sp_configure 'max degree of parallelism', 1
reconfigure with override
exec sp_configure 'xp_cmdshell', 1
reconfigure with override
alter database <SID> set page_verify checksum
go
alter database <SID> set auto_create_statistics on
go
alter database <SID> set auto_update_statistics on
go
alter database <SID> set auto_update_statistics_async on
go
dbcc updateusage ('<SID>')
go
exec sp_updatestats
go
SAP Tasks
Check SM21/SM50/DB02/ST04/ST22/SICK for any unusual error messages.

Hello,
I want run the below script on SQL 2005, can anyone tell me how I run it in SQL 2005?
exec sp_configure 'xp_cmdshell', 1
reconfigure with override
I need to enable xp_cmdshell in sql 2005
Reg,
SAT

Report error after update to SQL 2005

We revently updated our database server from SQL 2000 to SQL 2005. After the update we have a report getting the following error.
Failed to retrieve data from the database.
Details: 22018:[Microsoft][ODBC SQL Server Driver][SQL Server]Conversion failed when converting the varchar value '96.48' to data type int. [Database Vendor Code: 245]
The report contains 2 views with one join and worked fine previously. The field referenced by the error will display fine as long as there are no fields from the other view on the report. As soon as I add a field from the second view, no data is displayed. I have not created any conversion to integer within the Crystal report for any field. Any help getting this to work again would be greatly appreciated.

Hi,
What steps did you perform before upgrading? dont update. Try to back-up all your database and restore to SQL Server 2005 manually lets see if it have problems, seems to me a conflict datatypes.
Regards,
Clint

MS SQL 2005 Warning when upgrading 2005A SP01 PL10 to PL34

When attempting the above upgrade I get the following warning during the Upgrade of the Common db.
"Changing any part of an object name could break scripts and stored procedures".
We have version 9.00.1399.06 of SQL 2005. I think this is SP00.
SAP Support advised me to uninstall and re-install SBO bt I got the same error again.
I am considering upgrading SQL 2005 to SP01 or SP02 to try to resolve this issue.
Is SP02 supported for SBO?

Hello,
Based on latest sizing guide file, recommended database servers are :
1. Microsoft SQL Server 2005 Standard or Enterprise Edition
(As of SAP Business One 2005 SP 01 Release and only on Windows 2003 Server operating system.)
2. Microsoft SQL Server 2000 SP4 Standard or Enterprise Edition
3. IBM DB2 Universal Database 8.2.2 FP5 Express Edition
4. Sybase Adaptive Server Enterprise 12.5.3 GA
if you need the file, you could download it from this link :
https://websmp108.sap-ag.de/smb/sbo/documentation
Rgds,
JM
http://groups.yahoo.com/group/SBO_Knowledge_Village
[email protected]

Upgrade from 11.1.1.3 to 11.1.2.2 in single environment OS 2003 SQL 2005

We have upgrade from 11.1.1.3 to 11.1.2.2 in single environment OS 2003 SQL 2005
We have Essbase, Planning,HFM,FDM Applications and FR reports.
While configurating Reporting and Analysis we have issue configure Frame work services failed.Remaining all in configuration worked fine .while configuration we have enabled import data for earlier release when ever it is required.
We are able to see only HFM Applications . we are not able to see EPMA Planning Applications and Essbase Applications. When we tried to login through console its showing this message Error: 103: Unexpected Essbase error 1051293 Error: 1051293: Login fails due to invalid login credentials
configure Frame work services failed
we are not able to see EPMA Planning Applications
Essbase Applications when we tried to login through console its showing this message Error: 103: Unexpected Essbase error 1051293 Error: 1051293: Login fails due to invalid login credentials (we are able to login to Essbase easconsole but we are not able to see applications in essbase easconsole)
Naveen

Hi Naveen,
you can check log files for the error msg abt 1st and 3rd options.
C:\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\services
For 2nd option, have you used correct database at the time of EPMA configuration???
Please check in the Database(which have used for EPMA), dbo.DS.Application table contains applications list.
Check out in that table u have applications or not???
At the time configuration, u didn't use correct database for EPMA. so, no applicaions are displayed in the epma.
Cheer,
mady
Please mark the replies as helpful or correct to help others

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

Upgrade R/3 4.7 110 from SQL 2000 to ECC 6.0 /SQL 2005

Dear Experts,
We are currently running R/3 4.7 110 with kernel 640 32 Bit Non Unicode on Windows Server 2000/ MS SQL 2000 Platform. We are planning to Upgrade the same to ECC 6.0 on Windows 2003/ SQL 2005 on New x64 Bit Hardware.
I was earlier planning to Upgrade the OS/DB in first Phase moving the same R/3 4.7 on Windows 2003 Server /MS SQL 2005 and then Upgrade it to ECC 6.0 in second phase. But to my surprise when I checked PAM, I found that R/3 4.7 110 is not at all supported on SQL 2005 ( though R/3 4.6 C is)
Now shall I upgrade it to ECC6.0 First with Windows 2003/SQL 2000 ( Because ECC6.0 is supported with MS SQL 2000)and then move to MS SQL 2005 ?
Thanks
Jitendra Tayal

We had the same issue.
So I checked with SAP.
This was their reply.
'SAP R/3 4.7 Ext 110 is supported on SQL 2005. Please refer to the following notes for further information:'
Note 905634 - Release planning for Microsoft SQL Server 2005
Note 799058 - Setting Up Microsoft SQL Server 2005
Note 899111 - Installing R3 4.7SR1 (47X110) on x64 Windows Platform
Note 151603 - Copying an SQL Server database
So feel free to go ahead.
Thanks.
Carl.

Error in Upgrading to MS SQL 2005

Similar Messages

Maybe you are looking for