CF 9 Enterprise - SQL Server 2008 SLOW

Hello all-
We've been running CF8 standard on a 32 bit Windows Server 2003 box. Everything is fine and dandy.
We are upgrading to CF9 Enterprise on a 64 bit Windows Server 2008 r2 box, but things are not going well.
Both of these servers are connecting to the same database, on the same SQL Server 2008 instance.
I am having some fairly serious slowdowns in our SQL queries on our new CF9 box. Queries that are taking 30 milliseconds on the old server, are taking 250+ milliseconds on the new server. This is happening between different databases, different queries, etc. This new server is just a whole lot slower when connecting to the exact same SQL Server.
I've pinged our database server from both CF servers- no difference. (Both are 0 ms)
The old server is running version 2000.86.3959 of the SQL Server driver (2/17/2007).
The new server is running version 6.01.7600.16385 (7/13/2009)
Any ideas as to what could be causing the slowdown?
Thanks,
Karl
Message was edited by: karlkrist to add sql server driver versions

I've never encountered this problem, I'm not using CF9 or SQL 20008; but here are some things to investigate.
1. Are there any differences in the way your datasources are configured in CF between the two servers. For example, do you have the "Maintain Connections" option enabled on one server's datasource, but not the other?
2. You might try using an alternate JDBC driver to see if this issue is caused by the drivers. Microsoft produces as JDBC driver for SQL server and I think there may be open source options.
Microsoft's JDDB driver:
http://www.microsoft.com/downloads/details.aspx?FamilyID=99b21b65-e98f-4a61-b811-19912601f dc9&displaylang=en

Similar Messages

MS SQL Server 2008 R2 Enterprise Edition on Windows Server 2008 R2 Standard Edition

Hello Team,
Is there any issue/conflicts/limitationn to install MS SQL Server 2008 R2 Enterprise Edition on Windows Server 2008 R2 Standard Edition.
OR their is nothing to worry about it I guess their is memory limitation between both of them. Please suggest
Regards
Naveed Amir

Hi,
Here you can find the officially Hardware and Software Requirements for SQL Server 2008 R2:
http://msdn.microsoft.com/en-us/library/ms143506(v=sql.105).aspx
There should be NO problem as much as I know if the basic limitation fit you (as shanky mentioned).
I had (an clients still have) several servers with Windows Server 2008 R2 Standard & SQL
Server 2008 R2 Enterprise and Standard with no problem (today I have one old developing server with this exact installations work great for several years).
[Personal Site] [Blog] [Facebook]

Attempted to perform an unauthorized operation error while installing SQL Server 2008 R2 Enterprise edition on Windows Server 2012 R2 standard VM server

I've been trying fresh installation of SQL Server 2008 R2 enterprise on Windows Server 2012 R2 standard VM server several times for two weeks, but always get the error "Attempted to perform an unauthorized operation". At first, I attempted
to install all features, but failed several times. So I decided to try install just Database Engine service, and still fail at the SqlBrowserConfigAction_Install_ConfigNonRC_Cpu32, with the error "Attempted to perform an unauthorized operation".
I remote login to server with my admin domain account. This account is in server local Administrators group. I
1. Right-click on setup.exe file | properties | Compatibility tab | select compatibility to Windows 8.Then click OK.
2. Right-click on setup.exe file | Run as Administrator, to start the Installation Center.
I have the document of my installation steps and zip file of the installation logs, if you need to take a look.
Appreciate for any help!
ntth

Hi ntth,
"Attempted to perform an unauthorized operation"
The above error is always related to the Windows account SID mapping. I recommend you login into Windows using another Windows account which has administrative privileges and run SQL Server setup using that Windows account.
Besides, please note that we need to apply SQL Server 2008 R2 Service Pack 2 or a later update when installing SQL Server Windows Server 2012 R2. For more information, please review this
KB article.
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

Install Active Directory Domain Controller on Windows server 2008 enterprise, dont login on Sql Server 2008 R2

I install Active Directory Domain Controller on Windows server 2008 enterprise and dont login on Sql Server 2008 R2. Before install ADDC, I have logon SQL Server 2008r2 Success, After when i install ADDC is don't logon on SQL Server 2008r2 -->not success.
I have uninstalled ADDC but i still can't login on SQL server 2008r2.
please help me. it is very very disaster!
I think is loss account SQL server 2008r2!

Hello,
I stronly recommend you post the detail error message to us while you try to connect to SQL Server instance, it's useful for us to do further investigation.
Microsoft recommends that you do not install SQL Server 2008 R2 on a domain controller, there are some limitations:
You cannot run SQL Server services on a domain controller under a local service account or a network service account.
After SQL Server is installed on a computer, you cannot change the computer from a domain member to a domain controller. You must uninstall SQL Server before you change the host computer to a domain controller.
After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the host computer to a domain member.
SQL Server failover cluster instances are not supported where cluster nodes are domain controllers.
SQL Server Setup cannot create security groups or provision SQL Server service accounts on a read-only domain controller. In this scenario, Setup will fail.
On Windows Server 2003, SQL Server services can run under a domain account or a local system account.
So, I would suggest you try to open up Windows Services list and changed the account for SQL Server service.
Regards,
Elvis Long
TechNet Community Support

Error 18452 "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication" on SQL Server 2008 R2 Enterprise Edition 64-bit SP2 clustered instance

Hi there,
I have a Windows 2008 R2 Enterprise x64 SP2 cluster which has 2 SQL Server 2008 R2 Enterprise Edition x64 SP2
instances.
A domain account "Domain\Login" is administrator on both physcial nodes and "sysadmin" on both SQL Server instances.
Currently both instances are running on same node.
While logging on to SQL Server instance 2 thru "Domain\Login" using "IP2,port2", I get error 18452 "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication". This happened in the past
as well but issue resolved post insatllation of SQL Server 2008R2 SP2. This has re-occurred now. But it connects using 'SQLVirtual2\Instance2' without issue.
Same login with same rights is able to access Instance 1 on both 'SQLVirtual1\Instance1' and "IP1,port1" without any issue.
Please help resolve the issue.
Thanks,
AY

Hello,
I Confirm that I encountred the same problem when the first domain controller was dow !!
During a restarting of the first domain controller, i tried to failover my SQL Server instance to a second node, after that I will be able to authenticate SQL Server Login but Windows Login returns Error 18452 !
When the firts DC restart finishied restarting every thing was Ok !
The Question here : Why the cluster instance does'nt used the second DC ???
Best Regards
J.K

Is it possible to install sql server 2008 standard edition in windows server 2008 enterprise edition?

hi,
Please help me..
is it possible to install sql server 2008 standard edition in windows server 2008 enterprise edition?
will any problem arise?

Hiya,
Yes it it possible. No there will not be any problems.
Short and simple :)

SQL Server 2008 R2 Setup Very Slow

Hi,
We have a multi-node SQL Server 2008 R2 Failover Cluster.
I've noticed that the SQL Server 2008 R2 Setup is extremely slow and that it appears to only be using 1 of the 128 "CPUs" (i.e. in Task Manager).
We use this for creating new cluster groups and alike.
Is this tool only single threaded and is there a way to increase the performance? Our CPUs are 2.something GHz, we have 512GB of RAM and fast local disks.
Thanks

Hello,
What happen if you slipstream the SQL Server 2008 R2 with the latest SQL Server 2008 R2 service pack? Maybe SQL Server setup does better after the slipstream process.
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
http://msdn.microsoft.com/en-us/library/dd638062(v=sql.105).aspx (Slipstream a SQL Server 2008 R2
Update)
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Upgrade SQL Server 2008 R2 enterprise edition to SQL server 2012 slandered edition

Hi everyone,
Need help on below concern.
I have SQL Server 2008 R2 enterprise edition installed. Which contains SSAS cubes, SSIS packages and SSRS Reports.
I need to upgrade it to SQL Server 2012 Standard edition.
How can I achieve this ??
And I don't have much idea in SSIS package migrations.
Please help me to achieve this.
Thanks,
Rohit

Hi,
Please follow side by side approach for upgrade.Get a new windows box and install SQL server 2012 on it
Move databases from SS2008 R2 to SS 2012 by backup restore mechanism.
Move
jobs and logins by Scripting out and running it on SQL SS 2012.See links as well
Please refer to
this link for SSIS package migration
For SSAS please post question in SSAS forum
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Microsoft SQL Server 2008 Express for SAP BusinessObjects Enterprise 4.0

Hi Expert,
I'm going to install SAP BusinessObjects Enterprise 4.0 on my virtualized system (vmware) composed as: windows server 2008 Enterprise Edition R2 + Tomcat. I have some doubts related to the DB version to choose.
Due to the fact that Microsoft SQL Server 2008 Express is bundled with SAP BOE 4.0 I want to use this DB.
However, I saw in the Microsoft Portal that Microsoft SQL Server 2008 Express (http://www.microsoft.com/sqlserver/en/us/product-info/compare.aspx) that:
Number of CPUs     1
Maximum memory utilized     1 GB
Maximum database size     10 GB
These my doubts:
1) Could these characteristics generate performance issues for a production environment?
2) Which is a typical DB size for a production enviroment? could be greater then 10 GB?
3) Can I use Microsoft SQL Server 2008 Express in a virtualized system (vmware)?
Thanks in advance for collabortion
regards
gio'

Hi Gio
Remember that the BOE system database (or repository) only has a few tables in it, with really one main table that stores a reference to each folder, report, user, group, server, etc. on the system. So the table and the database itself do not grow very large. In the past year, we have done over 70 SAP BusinessObjects projects and I can't recall one where the database size would even approach 5GB in total, let alone 10GB.
The reason for this is that the database only stores a reference to the physical objects and content within BOE-- the actual reports, universes, etc. are stored on the file system within the Input and Output file repository folders.
And the memory constraints are not really an issue either with BOE-- the database itself does not come under much strain during the day-to-day operation of the server. If you believe that the memory may be an issue, you can always start with SQL Server 2008 Express and then using the new tools in the 4.0 CMC to monitor the memory usage on the server. If you need to, you can move the system database to another SQL Server edition, or alternately move the database to another one of the supported platforms, including Oracle, DB2, etc.
Hope this helps!
regards
David

Renaming Sql Server 2008 r2 enterprise edition security roles

Hello All,
We got a requirement to rename existing SQL SERVER 2008 R2 ENTERPRISE EDITION security roles.
We are unaware of the impact on the existing users with these roles.
Can anybody advise us if we rename the role name manually,
We have to restart the sql server services to reflect the role name change to the users with these
roles?
Thanks In Advance

Hello All,
We got a requirement to rename existing SQL SERVER 2008 R2 ENTERPRISE EDITION security roles.
We are unaware of the impact on the existing users with these roles.
Can anybody advise us if we rename the role name manually,
We have to restart the sql server services to reflect the role name change to the users with these
roles?
Thanks In Advance
What security roles are you talking about?
built-in server- or database-roles? - those cannot be renamed.
User-defined roles can be renamed at any point in time without any problems unless you write code that specifically accesses them by name yourself.
Andreas Wolter (Blog |
Twitter)
MCSM: Microsoft Certified Solutions Master Data Platform, MCM, MVP
www.SarpedonQualityLab.com |
www.SQL-Server-Master-Class.com

Dump of SQL Server 2008 R2 Enterprise

Hi,
How can I download the Dump of SQL Server 2008 R2 Enterprise Edition? I have the License Details. But I missed the CDs. Could you please help for the Dump collection?
! ! Thank You Very much ! !
Best Regards
+91 9871843884

How can I download the Dump of SQL Server 2008 R2 Enterprise Edition? I have the License Details. But I missed the CDs. Could you please help for the Dump collection?
Hi,
If you have license key with yourself. You can download SQL Server 2008 R2 Evaluation edition. When you are installing SQL Server eval edition on license key page you would have option to select free edition or provide License key for Enterprise edition.
Provide License key and it would be enterprise edition after your installation finishes
PS: if above does not helps please speak to MS personal
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Sql server 2008 standard edition verses enterprise edition

I heard on a call today that microsoft has different logging capture in these two editions. Also because of this difference that at least in the past GG could not support some replication approaches from SQL Server Standard Edition beacuse of this. Can anyone point me to a resource or certification matrix that references standard verses enterprise versions of SQL Server.

From the SQL Server installation guide:
● SQL Server 2000/2005: Enterprise and Standard Edition
● SQL Server 2008: Enterprise (capture or delivery) or Standard Edition (delivery only)
● SQL Server 2008 R2: Enterprise (capture or delivery) or Standard Edition (delivery only)

Downgrade SQL Server 2008 Enterprise to SQL Server2008 Standard Edition

I would like to know from fourm users, what are the necessary steps I would take care for above mentioned activity and also please let me know best suitable option for Production.
SNS

You can't do in-place downgrade. You need to go with backup -> uninstall ent -> install std -> bring it to same patch -> restore databases approach.
You need to make sure that there is not enterprise only feature used else you can't restore database on standard.
Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
Balmukund's answer above is the Microsoft supported route for doing a downgrade of an instance of SQL Server. However, before you do this, you need to query the sys.dm_db_persisted_sku_fearures DMV in each of your user databases to make certain that
you don't have any Enterprise features in use that would block your ability to restore a database onto Standard Edition.
No matter what you are going to have to do an uninstall and reinstall of the SQL Server instance to downgrade the SKU. However, you can save yourself some time and the headache of trying to restore the system databases if you are careful about what
you do. I have done a couple of SKU downgrades in the past and the easiest way to do it, and I am not saying this is the Microsoft supported way but that it works if done correctly, is to:
Take a good backup of all of your databases (system and user).
Run SELECT @@VERSION and note the specific build number of SQL Server that you are currently on.
Shut down your existing instance of SQL Server.
Copy the master, model, and msdb database files (both mdf and ldf), don't move them copy them, from the current location to a new folder that you mark as readonly.
Uninstall SQL Server from the system.
Reboot the server.
Install SQL Server Standard Edition.
Apply the necessary Service Pack and/or Cumulative Updates to bring the instance up to your previous build number.
Shutdown SQL Server.
Copy the master, model, and msdb database files (both mdf and ldf) from the folder you saved them in to the correct location for the new install and remove the readonly flag from the files, and change the file ACL's so that the SQL Service account has Full
Control over the files.
Startup SQL Server and if you did it correctly it will startup and be exactly where you were before you made any changes, with all of your user databaes online and you should be ready to let applications connect and resume operations.
If you screw something up in the above, you still have your backups and you can run setup to rebuild the system databases and then go about following the Microsoft supported path for restoring the system databases and then user databases into the system
to bring it online. Essentially the file copy is no different that what would occur through attach/detach you are just doing it with system databases which is not supported, but it does work. The key is to have your backups from before you do anything
so you have the supported route available if you encounter an issue. The only issue I have ever had doing this set of steps is that I didn't set the file ACL's correctly and the database engine threw Access Denied errors and failed to start until I fixed
the ACL's correctly. This can save you many hours of frustration and downtime trying to restore everything since the database files are already there and it is just some small copy operations to put them where you need them to be.
Balmukund, feel free to beat me over the head for suggesting a non-supported path. :-)
Jonathan Kehayias | Senior Consultant,
SQLSkills.com
SQL Server MVP | Microsoft Certified Master: SQL Server 2008
Feel free to contact me through
My Blog or
Twitter. Become a
SQLskills Insider!
Please click the Mark as Answer button if a post solves your problem!

Error on setup failover cluster with Windows 2008 R2 enterprise and SQL Server 2008 R2 (also with SP1)

Hi!
The setup process fails with this error:
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
I have found some hints by google, but nothing really helpfull.
Has anyone had a simular problem when installing SQL server 2008 R2?
All posts I found are about sql server 2008 (no R2!).
The cluster itself is working (storage, network, msdtc, quorum...).
Any hints?
Andreas
Here is the complete log:
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2067791871
Exit facility code:            1216
Exit error code:               1
Exit message:                  Failed: see details below
Start time:                    2012-04-06 11:23:57
End time:                      2012-04-06 12:01:21
Requested action:              InstallFailoverCluster
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0x625969A3%400x294A9FD9
Cluster properties:
Machine name: OC-SQLCL02ND01
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Machine name: OC-SQLCL02ND02
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Machine Properties:
Machine name:                  OC-SQLCL02ND01
Machine processor count:       32
OS version:                    Windows Server 2008 R2
OS service pack:               Service Pack 1
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  Yes
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
Installation location:         G:\x64\setup\
Installation edition:          STANDARD
Slipstream:                    True
SP Level                       1
User Input Settings:
ACTION:                        InstallFailoverCluster
AGTDOMAINGROUP:                <empty>
AGTSVCACCOUNT:                 MANAGEMENT\sqladmin
AGTSVCPASSWORD:                *****
ASBACKUPDIR:                   S:\OLAP\Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   S:\OLAP\Config
ASDATADIR:                     S:\OLAP\Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      S:\OLAP\Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  MANAGEMENT\sqladmin
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            MANAGEMENT\administrator
ASTEMPDIR:                     S:\OLAP\Temp
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\ConfigurationFile.ini
CUSOURCE:
ENU:                           True
ERRORREPORTING:                False
FAILOVERCLUSTERDISKS:          Cluster Disk 3,Cluster Disk 4,Cluster Disk 5
FAILOVERCLUSTERGROUP:          SQL Server (MSSQLSERVER)
FAILOVERCLUSTERIPADDRESSES:    IPv4;172.29.2.122;Cluster Network 2;255.255.255.0,IPv4;172.29.3.122;Cluster Network 3;255.255.255.0
FAILOVERCLUSTERNETWORKNAME:    CLUSTER02
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SSMS,ADV_SSMS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD:                 *****
HELP:                          False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             S:\
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    MSSQLSERVER
INSTANCENAME:                  MSSQLSERVER
ISSVCACCOUNT:                  NT AUTHORITY\SYSTEM
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
PASSPHRASE:                    *****
PCUSOURCE:                     d:\install\mssql\sp1
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
RSINSTALLMODE:                 FilesOnlyMode
RSSVCACCOUNT:                  MANAGEMENT\sqladmin
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  SQL
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLDOMAINGROUP:                <empty>
SQLSVCACCOUNT:                 MANAGEMENT\sqladmin
SQLSVCPASSWORD:                *****
SQLSYSADMINACCOUNTS:           MANAGEMENT\administrator
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               L:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQLUSERDBDIR:                  T:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQLUSERDBLOGDIR:               L:\MSSQL10_50.MSSQLSERVER\MSSQL\Data
SQMREPORTING:                  False
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Failed: see details below
Configuration error code:
0x1C2074D8@1216@1
Configuration error description: There was an error setting private property 'VirtualServerName' to value 'CLUSTER02' for resource 'SQL Server'. Error: Value does not fall within the expected range.
Configuration log:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\Detail.txt
Feature:                       Analysis Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Reporting Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Integration Services
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Connectivity
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Complete
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Business Intelligence Development Studio
Status:                        Passed
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120406_112205\SystemConfigurationCheck_Report.htm

Hi Andreas Plachy,
Please make sure that the Virtual Server Name ‘CLUSTER02’ is unique on the network. In addition, are there any resources named ‘SQL Server’ on the Windows cluster? If that is the case, you may need to rename the related resources to avoid conflicting with
SQL Server, and try again.
Stephanie Lv
TechNet Community Support

DI Server with SQL Server 2008

Hello.
In the company where I work we develop an application that uses B1WS.
In the development environment had the following characteristics:
SAP Business One 2007 SP01, PL 09
SQL Server 2005 Developer Edition
Windows XP Professional SP 3
SAP Business One Web Services 1.0
At the time we applied to the deploying the SAP Business One version 8.8, but I had a serious problem. The test environment has the following characteristics:
SQL Server 2008 Enterprise Edition
SAP Busines One 8.8 * PL 10
Windows Server 2008
The problem is that when trying to connect to the DI Server generates the following messages:
The TAO NT Naming Service has stopped. (WithOut DBUser and DBPassword)
Unable to access SBO-Common database Login (With DBUser and DBPassword)
I tested the connection directly to the DI Server disponbile by example in the SDK and it generates the same error. For the SAP interface is connected correctly.
DI Server allows connect with SQL Server 2008?
Messagge:
<DatabaseServer>mv-05910a0046</DatabaseServer>
<DatabaseName>Prueba</DatabaseName>
<DatabaseType>dst_MSSQL2008</DatabaseType>
<DatabaseUsername>sa</DatabaseUsername>
<DatabasePassword>12345</DatabasePassword>
<CompanyUsername>manager</CompanyUsername>
<CompanyPassword>12345</CompanyPassword>
<Language>ln_English</Language>
<LicenseServer>mv-05910a0046:30000</LicenseServer>
Thanks
Edited by: Andres Naranjo on May 14, 2010 12:47 AM
Edited by: Andres Naranjo on May 14, 2010 3:56 PM
Edited by: Andres Naranjo on May 14, 2010 3:58 PM

Had the same error
'The TAO NT Naming Service has stopped.'
Was using the external IP address for the LicenceServer - which is on the same server as SAP DIserver and B1WS.
I changed to using localhost:30000 and that solved the issue.
I suspect if I had used the internal IP it would have worked as well (ie the one you get from ipconfig) but as it works I'm not going to test that.
HTH

CF 9 Enterprise - SQL Server 2008 SLOW

Similar Messages

Maybe you are looking for