P6 v.7 configuration question (SQL 2008)

I'm in the process of creating a server to test a client/server deployment of P6 before we go live with it, but in reviewing the tested configurations in the Oracle knowledgebase I do not see our config, and I just wanted to see if anyone has successfullly used the one I want to go with. The config is:
Windows Server 2008 X64 R2 SP1 on a Virtual in Hyper V (4 GB RAM, 2 Virtual processors)
SQL 2008 with SP2
Specifically looking for if anyone has tested it with SQL 2008 SP2. We can forego installing the service packs on SQL if they seem to cause issues.
Thanks for any advice you all can give.

While I have not personally tested SQL 2k8 SP2 I doubt you will have any issues.
What you may be concerned with however is that when running on an unofficially-supported platform the vendor may chose not to assist you should something go severely wrong down the road. In Primavera's case I have never seen this to be a problem but now that Oracle has taken over things could potentially be different (especially in the case of MS SQL as I imagine they will eventually stop supporting it altogether).

Similar Messages

SCCM 2012 on SQL 2008 R2 cluster

Looking Positive and negative for SCCM 2012 SQL cluster configuration. I am looking for configuration for sql 2008 cluster.
can you any configured ? is yes please step by step configuration and preservative

positive: obviously, the SQL could have high availability and will auto fail over to another box if one of the boxes is down.
Juke Chou
TechNet Community Support

SQL 2008 On SBS 2011 Question

Hi.
We have an sbs2011 std server.
We are looking at a new accounts package that requires SQL 2008 r2 (not express).
Our first thought was to purchase the premium add on but we can not find a single stockist in the UK that has one left for sale.
So is the only option to purchase another server with server OS and SQL 2008r2 STD on it if so this would be very very expensive.
We have also been made aware of SQL 2008 r2 for SBS, if this is OK to run the new accounts with then can this version of SQL be installed on SBS 2011 as we have found an copy that is for 1 server 5 cals for £600 (not sure how we buy more cals though as we
would need 6 users)
I would appreciate any advice on this situation.
Many thanks for you time

Hi:
It has been awhile since I have thought about this, but looking up the requirements for SQL 2008 for SBS I find this:
http://blogs.technet.com/b/sbs/archive/2009/03/23/requirements-for-installing-sql-2008-standard-edition-for-small-business.aspx
It appears it would work, and iirc the PAO was added for SBS 2011 because of the need to add a second server for SQL because Exchange 2010 uses so many resources on SBS 2011.
Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

Cannot see new SQL 2008 R2 Express instance on Small Business Server 2011!

Hi,
As it is stated on the subject line, I'm having a problem after I did a new install of SQL 2008 R2 Express and put a new instance on SBS 2011.
I'm developing a new program using SQL 2008 in C# and VB.Net. I have SQL 2008 R2 Express installed on my computer called "MSQL8R2EDATA" on my PC. Now I need to deploy it on SBS 2011 so I can do some testing on other workstations.
I'm currently running Windows 7, 64 bit, and it's named STEVE-PC. The SBS 2011 is named SERVER1, and it's 64 bit as well.
After installation on SERVER1 (SBS 2011), I then fired up SQL Server Configuration Manager and enabled Named Pipes, TCP/IP, and VIA.
After I've completed the SQL Configuration on SERVER1, I went back on my PC (STEVE-PC) and I tried to use Management Studio to connect to the new instance MSQL8R2EDATA on SBS 2011, only problem is, I only see the computer name, not the new instance
I've installed.
Back on SBS 2011 (SERVER1), I've verified that all the protocols are enabled, and the SQL Server Browser is automatically loaded and currently running, as well the MSQL8R2EDATA instance is automatically loaded and running, yet I still cannot see
it from my PC (STEVE-PC). I even switched from dynamic ports to a static port of 64719 (that was what the MSQL8R2EDATA was listening on that port when it was dynamic), and then added new rules to the Windows Firewall for program of the SQLSERVR.EXE, and
for UDP and TCP for port 64719 to "Allow All Connections" for Domain, Private, and Public; yet I still cannot connect SERVER1\MSQL8R2EDATA. I even disabled the firewall and then trying to connect once again to SBS 2001 and it still fails.
In case you're wondering, I left it on port 64719 since there are other active SQL Servers on SBS 2011 (SharePoint, SBSMonitoring, and ACT7).
Interestingly, when I run Management Studio on SBS 2011, I can see STEVE-PC\MSQL8R2EDATA and I'm able to log in and connect to it.
So what's going on here?!? Why am I able to connect to STEVE-PC which is Windows 7 64 from SBS 2011 (SERVER1), but I cannot connect from my computer to that instance on SBS 2011??
I really could use some big time help on this.
EDIT: Sorry for the confusion, but on the Windows Firewall (WF.msc), I did add new rules for incoming connections on:
Program incoming connections to SQLSERVR.EXE
TCP Port 64719
UDP Port 64719
EDIT: To further assist, I have Management Studio installed on the SBS 2011, and I can locally log in and connect to the MSQL8R2DATA on SERVER1 with success. I even tried tcp:SERVER1\MSQL8R2DATA and again it is successful log-in and connection.
Thanks in advance!
Steve

Hi,
Thanks for the response, but I have a question:
Installing SQL Express or SQL Server is not recommended on SBS
2011 because it is a DC, however technically it will work.
I'm a newbie when it comes to SBS 2011 and I'm taking a crash course on the subject. Can you explain to me what you mean by "DC"? Also, why
isn't recommended to install a new instance on SBS 2011?
As I also stated, I've added "New Rules" to the Windows Firewall to allow incoming connections on port 64719 for both TCP and UDP, and I also allowed incoming connections for SQLSERVR.EXE but no joy to connect to the SERVER1\MSQL8R2EDATA.
And yes, I can log-in and connect locally on SERVER1 using Management Studio with success. I even used tcp:SERVER1\MSQL8R2EDATA with the same success. It's my workstation STEVE-PC that fails. If that fails, then the rest of the workstations are going to fail.
Are you suggesting that I put the SQL Server 2008 Express on another workstation and just allow to to be
accessed that way?

Upgrading SQL 2008 R2 to SQL 2012 SP1

Hi everyone,
We are testing some upgrades in a lab environment. We have upgraded to SCCM 2012 R2 and are now looking at upgrading to SQL 2012 SP1 from SQL 2008 R2. Both SCCM and SQL are on one server. (The next step is to split SCCM and SQL but that's another topic)
The question we are asking is, what should be our process for the upgrade? Do we need to stop SCCM services before doing the SQL upgrade? If, so, which ones?

Hi,
You need to stop all Configuration Manager services at the site.
For the process of the upgrade, you could check the following document.
http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigUpgradeDBSrv
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SQL 2008 R2 In-Place Upgrade or Fresh Install to SQL2104

We have a server running Windows 2008 R2 and SQL 2008 R2 currently. We will call it SQL01. This houses databases for about 8 different applications and also has the name hard coded into a lot, I repeat, a lot of various things.
We are at the point where one of our applications needs to be upgraded and it only works with SQL 2014. So we need to either do an in-place upgrade or fresh install.
The obvious choice to me as a system admin is to do a fresh install, but the development side of the department knows how many places the name "SQL01" is hard coded and they want to do an in-place upgrade to avoid all the issues that would show
up if we changed names.
I have several questions, and I'd appreciate that the answers address them all if possible.
1. What are people's experiences with in-place upgrades from SQL 2008 R2 to SQL 2014?
2. To avoid this naming and coding issue, do companies use a permanent alias for their SQL servers? Like with exchange, we have an alias or A record pointing "mail" to the current Exchange server. As we do upgrades and the Exchange
server names change, the "mail" entry will always be pointed to the current one. Do people do this for SQL as well to avoid our issue of hard coding names?
3. I've head that you can also have both SQL 2008 R2 and SQL 2014 on the same server running together. This really doesn't help though if the SQL 2014 instance would need to be something other than the default which everything is currently pointed
to correct?
4. Is there any advice about a better way to go about this? Or a better way to do this moving forward? Other than not hard coding which I can't change now?
Thanks!

Hello,
Adding to the answers provided above, please consider discontinued features no longer available on SQL Server 2014.
I often see company configuring SQL Server aliases when installing SQL Server on SharePoint environments. You can certainly use DNS or use the following article.
http://msdn.microsoft.com/en-us/library/ms190445.aspx
An in-place upgrade is easier but is difficult to rollback in case something goes wrong. Meanwhile, a side-by-side upgrade provides you more control over what is upgraded, it keeps the legacy server online during the upgrade allowing you to easy rollback if
needed, but is not an automated process and the instance will not keep the same name, requiring you to use aliases or other ways to avoid client redirection.
Since you cannot change the application, go for a side-by-side upgrade and try the DNS alias or the client-side alias as I provided the procedure above.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Excel 2007 ignores the roles configured on SSAS 2008

Hi,
I am facing a common problem for which I have found very useful threads but they didn't manage to help me.
My problem is on excel report, Dimension data is not filtering correctly when I connect with user credentials for which a role is configured on the cube. Excel 2007 ignores the roles configured on SSAS 2008 and I tested with 2 different users with the same
role configuration.
I ensured that the user doesn't fall in the server admin role and . I started up an SQL Profiler and I ensured no * in the list of roles of the user. I ensured also that there is no "built-in administrators group" configured (Security\BuiltinAdminsAreServerAdmin).
http://social.technet.microsoft.com/Forums/sqlserver/en-US/7052f751-8478-4ab2-aba8-d250a1606e07/deny-access-to-analysis-services-cube-from-excel-2007
Also I am planning to upgrade my Service Pack 1 to the cumulative pack Hot Fix 2710 ( KB969099 ) as it seems there are some known issues about dimension security on SSAS 2008. Do you really think it is a question of upgrade?
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/4b4e6e3c-bebe-4f81-8462-b2d0bd61ad11/dimension-attribute-security-on-ssas-2008-not-working-but-works-fine-on-2005
However I managed to work around the issue on SSAS and on Excel as follow but it is the not the solution expected:
- On SSAS 2008 R2 cube browser, while testing using the role: Dimension values filtered correctly the required data
- On Excel: Unless the role is specified in the configuration of the connection then the data is not filtered.
http://kevin_s_goff.typepad.com/kevin_s_goff_weblog/2009/12/1242009---testing-ssas-roles-in-excel.html
It is really urgent,
Many thanks

Hello,
I'm experiencing exactly the same issue and I can't find any solution to it.
Were you able to solve it? If so, how did you do it?
Thanks!!!

Issue With Report Builder After Installing SP3 for SQL 2008 R2

Hello. We are experiencing an issue with Report Builder 3.0 since installing SP3 for SQL 2008 R2 over the weekend. You can no longer launch Report Builder from the Reporting Services URL (http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application
      Server  : Microsoft-HTTPAPI/2.0
      X-AspNet-Version: 2.0.50727
Application url   :
http://dicomweb/ReportServer/ReportBuilder/RptBuilder_3/MSReportBuilder.exe.manifest
      Server  : Microsoft-HTTPAPI/2.0
      X-AspNet-Version: 2.0.50727
IDENTITIES
Deployment Identity  : ReportBuilder_3_0_0_0.application, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86
Application Identity  : MSReportBuilder.exe, Version=10.50.6000.34, Culture=neutral, PublicKeyToken=c3bce3770c238a49, processorArchitecture=x86, type=win32
APPLICATION SUMMARY
* Online only application.
* Trust url parameter is set.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of
http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application resulted in exception. Following failure messages were detected:
  + File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [10/15/2014 9:35:56 AM] : Activation of
http://dicomweb/ReportServer/ReportBuilder/ReportBuilder_3_0_0_0.application has started.
* [10/15/2014 9:36:29 AM] : Processing of deployment manifest has successfully completed.
* [10/15/2014 9:36:29 AM] : Installation of the application has started.
* [10/15/2014 9:36:31 AM] : Processing of application manifest has successfully completed.
* [10/15/2014 9:36:35 AM] : Found compatible runtime version 2.0.50727.
* [10/15/2014 9:36:35 AM] : Detecting dependent assembly Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=msil using Sentinel.v3.5Client, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a,
processorArchitecture=msil.
* [10/15/2014 9:36:35 AM] : Detecting dependent assembly System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=msil using System.Data.Entity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089,
processorArchitecture=msil.
* [10/15/2014 9:36:35 AM] : Request of trust and detection of platform is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [10/15/2014 9:36:43 AM] System.Deployment.Application.InvalidDeploymentException (HashValidation)
  - File, Microsoft.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, Hash hash)
   at System.Deployment.Application.ComponentVerifier.VerifyFileHash(String filePath, HashCollection hashCollection)
   at System.Deployment.Application.ComponentVerifier.VerifyComponents()
   at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification
notification, DownloadOptions options)
   at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
   at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
   at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
   at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Hi DMcGarveyt,
This is an known issue in SSRS 2008 R2 SP3. For this issue, Microsoft has published an article addressing this issue. It is not planning to release a fix for this defect. But there's workarounds for this issue. Please refer to the link below:
Report Builder of SQL Server 2008 R2 Service Pack 3 does not launch.
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Data Services 4.0 installation with MS SQL 2008

hey guys,
I am trying to install data services 4.0 on a windows server with MS SQL database as the repository database. So, my plan was to install MS SQL 2008 first, then IPS, then data services. But i am facing a problem in installation of MS SQL itself. I installed MS SQL with following features - database engine, client tools and management tools. The installation process was smooth and the sql server services (server and agent) both startup just fine. I installed a custom instance for the same.
But problem is when I open the management studio and try to connect to the database engine, it does not connect, I choose database engine as the server type, local hostname as the server name and windows authentication as the authentican type but it fails with the following error:
TITLE: Connect to Server
Cannot connect to <myservername>.
ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=MicrosoftSQLServer&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
BUTTONS:
OK
Any clues as to what is causing this ??? Or is it normal at this stage of installation ?? I am confused. I have already tried to reinstall the server, no good, nothing in the event logs either.
Thanks,
RS

resolved via following:
In the TCP/IP Properties dialog box, on the IP Addresses tab, several IP addresses appear in the format IP1, IP2, up to IPAll. One of these is for the IP address of the loopback adapter, 127.0.0.1. Additional IP addresses appear for each IP Address on the computer. Right-click each address, and then click Properties to identify the IP address that you want to configure.
If the TCP Dynamic Ports dialog box contains 0, indicating the Database Engine is listening on dynamic ports, delete the 0.u201D
Once I deleted those zeros and put in 1433 for TCP ports on each IP address, voila!

SharePoint 2010 + SQL 2008 + DPM 2012 Backup Failures

I have a single SharePoint 2010 WFE and a SQL 2008 server backend. Since configuring DPM to run the SharePoint backup through the WFE, I have had no success with backups.
DPM Reports:
The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError: The writer experienced a non-transient error. If the backup process
is retried, the error is likely to reoccur. (0x800423F4))
Event Log on SQL Server Reports:
Log Name:      Application
Source:        SQLWRITER
Date:          4/24/2014 4:44:17 PM
Event ID:      24583
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      srv-sql-01
Description:
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 319
Error state: 1, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.
SQLSTATE: 42000, Native Error: 103
Error state: 3, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: The file that starts with '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy334\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content30_1.mdf
' is too long. Maximum length is 259.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="SQLWRITER" />
    <EventID Qualifiers="0">24583</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-24T21:44:17.000000000Z" />
    <EventRecordID>293470</EventRecordID>
    <Channel>Application</Channel>
    <Computer>srv-sql-01</Computer>
    <Security />
</System>
<EventData>
    <Data>ICommandText::Execute</Data>
    <Data>0x80040e14</Data>
    <Data>SQLSTATE: 42000, Native Error: 319
Error state: 1, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: Incorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.
SQLSTATE: 42000, Native Error: 103
Error state: 3, Severity: 15
Source: Microsoft SQL Server Native Client 10.0
Error message: The file that starts with '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy334\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content30_1.mdf
' is too long. Maximum length is 259.
</Data>
    <Binary>53514C434F4E4E43313236330000000053514C434F4E4E433132323800000000</Binary>
</EventData>
</Event>
Followed by:
Log Name:      Application
Source:        VSS
Date:          4/24/2014 4:44:17 PM
Event ID:      8229
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      srv-sql-01
Description:
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
   PostSnapshot Event
Context:
   Execution Context: Writer
   Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Name: SqlServerWriter
   Writer Instance Name: SQL Server 2008 R2:SQLWriter
   Writer Instance ID: {18aa641d-ffcd-44be-84eb-77867e909c51}
   Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
   Process ID: 6036
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">8229</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-24T21:44:17.000000000Z" />
    <EventRecordID>293471</EventRecordID>
    <Channel>Application</Channel>
    <Computer>srv-sql-01</Computer>
    <Security />
</System>
<EventData>
    <Data>0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
</Data>
    <Data>
Operation:
   PostSnapshot Event
Context:
   Execution Context: Writer
   Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Name: SqlServerWriter
   Writer Instance Name: SQL Server 2008 R2:SQLWriter
   Writer Instance ID: {18aa641d-ffcd-44be-84eb-77867e909c51}
   Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
   Process ID: 6036</Data>
    <Binary>2D20436F64653A20575254575254494330303030353239392D2043616C6C3A20575254575254494330303030333336352D205049443A202030303030363033362D205449443A202030303030323630342D20434D443A202022433A5C50726F6772616D2046696C65735C4D6963726F736F66742053514C205365727665725C39305C5368617265645C73716C7772697465722E65786522202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
</EventData>
</Event>
When I run vssadmin list writers after the error, the "SqlServerWriter" show a State of [11]. I can restart the service and the error clears up showing stable, but the next time I run the backup it fails again.
From the error, it almost sounds like the path is too long. This doesn't totally make sense to me considering the database was successfully backed up before I tried to back it up as a SharePoint database.
Any suggestions would be appreciated.

Got the issue solved.
DPM has issues with DNS Aliases for SQL.
To get this issue sorted out i used the old HOSTS file to point the right name to the right SQL server.

Dg4odbc, unixODBC, freeTDS - connection problems to MS SQL 2008

I am trying to set up a database link between my 64bit Oracle 11g running on CentOS 6.2 and my MS SQL 2008 server running on MS Windows server 2003. I have installed the following -
freeTDS - version 0.91 (64 bit)
unixODBC - version 2.3.1 (64 bit)
I have successfully configured ODBC and freeTDS so that I can connect using isql and query my MSSQL database. The problem I am having is connecting Oracle to MSSQL, I am sure it is a simple configuration error but I have been going round in circles with this and hope someone can help!
freetds.conf
[global]
timeout = 10
connect timeout = 10
text size = 64512
[CERM]
host = 192.168.xxx.xxx
port = 1101
tds version = 7.2
instance = SSLSQLDB
dump file = /tmp/dump.log
odbc.ini
[ODBC Data Sources]
CERM=TDS connection
[CERM]
Servername = CERM
Description = TDS connection
Driver = /usr/local/lib/libtdsodbc.so
UsageCount = 1
FileUsage = 1
[ODBC]
Trace=255
odbcinst.ini
[TDS]
Description = FreeTDS driver for MS SQL
Driver = /usr/local/lib/libtdsodbc.so
Setup = /usr/lib64/libtdsS.so
Trace = Yes
TraceFile = /tmp/freetd.log
FileUsage = 1
[FreeTDS]
Description = FreeTDS driver for MS SQL
Driver = /usr/local/lib/libtdsodbc.so
Setup = /usr/lib64/libtdsS.so
Trace = Yes
TraceFile = /tmp/freetd.log
FileUsage = 1
(Because I have put the actual path to the driver in the odbc.ini file I don;t believe the odbcinst.ini file is actually used)
inithscerm.ora
# This is a sample agent init file containing the HS parameters that
# are needed for an ODBC Agent.
# HS init parameters
HS_FDS_CONNECT_INFO=CERM
HS_FDS_TRACE_LEVEL=255
#HS_FDS_TRACE_FILE_NAME = /tmp/hsodbcsql.trc
HS_FDS_SHAREABLE_NAME=/usr/local/lib/libodbc.so
HS_FDS_SUPPORT_STATISTICS=FALSE
set ODBCINI=/usr/local/etc/odbc.ini
(my odbc.ini file is located in /usr/local/etc)
listener.ora
# listener.ora Network Configuration File: /usr/oracle/product/network/admin/listener.ora
# Generated by Oracle configuration tools.
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = ssl-oracle.domain)(PORT = 1521))
ADR_BASE_LISTENER = /usr/oracle
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC=
(SID_NAME=hscerm)
(ORACLE_HOME=/usr/oracle/product)
(PROGRAM=dg4odbc)
(ENVS=LD_LIBRARY_PATH = /usr/local/lib:$ORACLE_HOME/lib)
(SID_DESC=
(SID_NAME=PROD)
(ORACLE_HOME=/usr/oracle/product)
tnsnames.ora
# tnsnames.ora Network Configuration File: /usr/oracle/product/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
PROD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = ssl-oracle.domain)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = PROD.DOMAIN)
hscerm=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=TCP)(HOST=ssl-oracle.domain)(PORT=1521))
(CONNECT_DATA= (SID=hscerm))
(HS=OK)
right - I can tnsping my hscerm instance and that returns ok so I'm fairly sure the configuration is fine for both tnsnames.ora and listener.ora. I can isql connect to the ODBC defined name for the the MSSQL database. but when I create a database link in Oracle and then test it I get the following trace output :-
[ODBC][14030][1339512618.356535][SQLSetConnectAttrW.c][332]
Entry:
Connection = 0x2054640
Attribute = SQL_ATTR_AUTOCOMMIT
Value = (nil)
StrLen = -5
[ODBC][14030][1339512618.356616][SQLSetConnectAttrW.c][616]
Exit:[SQL_SUCCESS]
[ODBC][14030][1339512618.356984][SQLDriverConnectW.c][290]
Entry:
Connection = 0x2054640
Window Hdl = (nil)
Str In = [DNCR;I=APDagj20][length = 30]
Str Out = 0x2053408
Str Out Max = 1024
Str Out Ptr = 0x7fff6d305770
Completion = 0
[ODBC][14030][1339512618.357030][SQLDriverConnectW.c][500]Error: IM002
[ODBC][14030][1339512618.357115][SQLGetDiagRecW.c][508]
Entry:
Connection = 0x2054640
Rec Number = 1
SQLState = 0x7fff6d3053d0
Native = 0x7fff6d3051c4
Message Text = 0x7fff6d3051d0
Buffer Length = 510
Text Len Ptr = 0x7fff6d305420
[ODBC][14030][1339512618.357153][SQLGetDiagRecW.c][550]
Exit:[SQL_SUCCESS]
SQLState = IM002
Native = 0x7fff6d3051c4 -> 0
Message Text = [[unixODBC][Driver Manager]Data source name not found, and no default driver specified]
[ODBC][14030][1339512618.357197][SQLGetDiagRecW.c][508]
Entry:
Connection = 0x2054640
Rec Number = 2
SQLState = 0x7fff6d3053d0
Native = 0x7fff6d3051c4
Message Text = 0x7fff6d3051d0
Buffer Length = 510
Text Len Ptr = 0x7fff6d305420
[ODBC][14030][1339512618.357228][SQLGetDiagRecW.c][550]
Exit:[SQL_NO_DATA]
[ODBC][14030][1339512618.357291][SQLDisconnect.c][208]
Entry:
Connection = 0x2054640
[ODBC][14030][1339512618.357321][SQLDisconnect.c][237]Error: 08003
[ODBC][14030][1339512618.357387][SQLFreeHandle.c][284]
Entry:
Handle Type = 2
Input Handle = 0x2054640
Now I can clearly see the error "Data source name not found, and no default driver specified" which according to all the documentation means that the entry HS_FDS_CONNECT_INFO=CERM does not match the entry in my odbc.ini file ([CERM]) but for the life of me I can;t see why they don;t match ??
Any help greatly received.

Yeah I verified with isql but I have changed the odbc.ini file as you suggested -
[root@ssl-oracle ~]# more /usr/local/etc/odbc.ini
[ODBC Data Sources]
CERM=TDS connection
[CERM]
Server = 192.168.xxx.xxx
Driver = /usr/local/lib/libtdsodbc.so
Database = sqlb00
Port = 1101
TDS_Version = 8.0
QuotedId = YES
[ODBC]
Trace=255
[root@ssl-oracle admin]# more inithscerm.ora
# This is a sample agent init file containing the HS parameters that
# are needed for an ODBC Agent.
# HS init parameters
HS_FDS_CONNECT_INFO=CERM
HS_FDS_TRACE_LEVEL=255
#HS_FDS_TRACE_FILE_NAME = /tmp/hsodbcsql.trc
HS_FDS_SHAREABLE_NAME=/usr/local/lib/libodbc.so
HS_FDS_SUPPORT_STATISTICS=FALSE
HS_LANGUAGE=american_america.we8mswin1252
HS_NLS_NCHAR=UCS2
set ODBCINI=/usr/local/etc/odbc.ini
[root@ssl-oracle admin]# osql -S CERM -U sa -P supersecretpassword
checking shared odbc libraries linked to isql for default directories...
trying /tmp/sql ... no
trying /tmp/sql ... no
trying /usr/loc ... no
trying /tmp/sql.log ... no
trying /home ... no
trying /.odbc.ini ... no
trying /usr/local/etc ... OK
checking odbc.ini files
cannot read "/root/.odbc.ini"
reading /usr/local/etc/odbc.ini
[CERM] found in /usr/local/etc/odbc.ini
found this section:
[CERM]
Server = 192.168.xxx.xxx
Driver = /usr/local/lib/libtdsodbc.so
Database = sqlb00
Port = 1101
TDS_Version = 8.0
QuotedId = YES
looking for driver for DSN [CERM] in /usr/local/etc/odbc.ini
found driver line: " Driver = /usr/local/lib/libtdsodbc.so"
driver "/usr/local/lib/libtdsodbc.so" found for [CERM] in odbc.ini
found driver named "/usr/local/lib/libtdsodbc.so"
/usr/local/lib/libtdsodbc.so is an executable file
"Server" found, not using freetds.conf
Server is "192.168.xxx.xxx"
looking up hostname for ip address 192.168.xxx.xxx
Configuration looks OK. Connection details:
DSN: CERM
odbc.ini: /usr/local/etc/odbc.ini
Driver: /usr/local/lib/libtdsodbc.so
Server hostname: ssl-database.domain
Address: 192.168.xxx.xxx
Attempting connection as sa ...
+ isql CERM sa supersecretpassword -v
| Connected! |
| |
| sql-statement |
| help [tablename] |
| quit |
| |
SQL>
sql.log
[ODBC][31473][1339581606.488571][SQLSetConnectAttr.c][396]
Entry:
Connection = 0x26c2a30
Attribute = SQL_ATTR_AUTOCOMMIT
Value = (nil)
StrLen = -5
[ODBC][31473][1339581606.488638][SQLSetConnectAttr.c][681]
Exit:[SQL_SUCCESS]
[ODBC][31473][1339581606.488924][SQLDriverConnect.c][726]
Entry:
Connection = 0x26c2a30
Window Hdl = (nil)
Str In = [DSN=CERM;UID=SA;PWD=**********][length = 30]
Str Out = 0x26c4b18
Str Out Max = 1024
Str Out Ptr = 0x7fff12846560
Completion = 0
UNICODE Using encoding ASCII 'ISO8859-1' and UNICODE 'UCS-2LE'
DIAG [01000] [FreeTDS][SQL Server]Unknown host machine name.
DIAG [08001] [FreeTDS][SQL Server]Unable to connect to data source
[ODBC][31473][1339581606.491276][SQLDriverConnect.c][1353]
Exit:[SQL_ERROR]
[ODBC][31473][1339581606.491358][SQLGetDiagRec.c][680]
Entry:
Connection = 0x26c2a30
Rec Number = 1
SQLState = 0x7fff128461c0
Native = 0x7fff12845fb4
Message Text = 0x7fff12845fc0
Buffer Length = 510
Text Len Ptr = 0x7fff12846210
[ODBC][31473][1339581606.491395][SQLGetDiagRec.c][717]
Exit:[SQL_SUCCESS]
SQLState = 08001
Native = 0x7fff12845fb4 -> 0
Message Text = [[unixODBC][FreeTDS][SQL Server]Unable to connect to data source]
[ODBC][31473][1339581606.491442][SQLGetDiagRec.c][680]
Entry:
Connection = 0x26c2a30
Rec Number = 2
SQLState = 0x7fff128461c0
Native = 0x7fff12845fb4
Message Text = 0x7fff12845fc0
Buffer Length = 510
Text Len Ptr = 0x7fff12846210
[ODBC][31473][1339581606.491493][SQLGetDiagRec.c][717]
Exit:[SQL_SUCCESS]
SQLState = 01000
Native = 0x7fff12845fb4 -> 20013
Message Text = [[unixODBC][FreeTDS][SQL Server]Unknown host machine name.]
[ODBC][31473][1339581606.491528][SQLGetDiagRec.c][680]
Entry:
Connection = 0x26c2a30
Rec Number = 3
SQLState = 0x7fff128461c0
Native = 0x7fff12845fb4
Message Text = 0x7fff12845fc0
Buffer Length = 510
Text Len Ptr = 0x7fff12846210
[ODBC][31473][1339581606.491558][SQLGetDiagRec.c][717]
Exit:[SQL_NO_DATA]
[ODBC][31473][1339581606.491623][SQLDisconnect.c][208]
Entry:
Connection = 0x26c2a30
[ODBC][31473][1339581606.491652][SQLDisconnect.c][237]Error: 08003
[ODBC][31473][1339581606.491719][SQLFreeHandle.c][284]
Entry:
Handle Type = 2
Input Handle = 0x26c2a30
[ODBC][31473][1339581606.491750][SQLFreeHandle.c][333]
Exit:[SQL_SUCCESS]
[ODBC][31473][1339581606.493083][SQLFreeHandle.c][219]
Entry:
Handle Type = 1
Input Handle = 0x26abfe0
I can also ping both the hostname and ip address of the MSSQL server.

Sharepoint 2010 SQl 2008 r2 Reporting Services Integrated with Claims

i have a 4 server sharepoint 2010 farm all servers are windows 2008 r2 x64
two severs are sharepoint app/wfe servers
one server is SQL sharepoint content db server sql 2008 r2 enterprise
one server is SQL Claims Provider DB and reporting services on SQL 2008 r2
the site is behind a forefront tmg proxy firewall for both internal and external users and both locations are producing the same results.
the web application i am having an issue with consists of a primary web app claims enabled web app that only has NTLM enabled, with an extended extranet webapp that supports claims and NTLM.
there is surrently a site collection that has been configured for reporting services when i log into the site as a SQL Claims user i am able to run the reportbuilder as a content type using the New Report builder report content type from a library on
this site. Reportbuilder launches and i am once gain prompted to login i login with the same credentials i used to log into the site and reportbuilder opens up and then i am able to open datasourceas and reports.
When i log in to the same site collection as a domain user i am able to log in to the site and launch reportbuilder. When reportbuilder opens up i am prompted to log in, i insert my domain\username and password and nothing happens the login prompt appears again
blank on the back end it throws the following exceptions
1. Password check on 'username' generated exception: 'System.ServiceModel.FaultException`1[Microsoft.IdentityModel.Tokens.FailedAuthenticationException]: The security token username and password could not be validated. (Fault Detail is equal to Microsoft.IdentityModel.Tokens.FailedAuthenticationException:
The security token username and password could not be validated.).'.
2.An exception occurred when trying to issue security token: The security token username and password could not be validated.
any thoughts on where i should begin troubleshooting this.

I think i am getting close i am now seeing a new error it seems that the sp farm account is unable my domain account when launching reportbuilder.
vent code: 4006
Event message: Membership credential verification failed.
Event time: 4/6/2014 10:59:05 AM
Event time (UTC): 4/6/2014 2:59:05 PM
Event ID: 7640af98dab846829f78e7d74a4e1e8a
Event sequence: 9
Event occurrence: 8
Event detail code: 0
Application information:
    Application domain: /LM/W3SVC/2/ROOT/SecurityTokenServiceApplication-1-130412687342754349
    Trust level: Full
    Application Virtual Path: /SecurityTokenServiceApplication
    Application Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\SecurityToken\
    Machine name: (SP WFE MACHINE NAME)
Process information:
    Process ID: 8044
    Process name: w3wp.exe
    Account name: (SP FARM ACCOUNT)
Request information:
    Request URL:
    Request path:
    User host address:
    User:
    Is authenticated: False
    Authentication Type:
    Thread account name: (SP FARM ACCOUNT)
Name to authenticate: (doamin account launching reportbuilder)
Custom event details:

SQL 2008 Reporting Services: Setting BackgroundRepeat = NoRepeat in SQL 2008

Good day
I have an report that has a background image set. The BackgroundRepeat property = Clip (which is the alternative to 2005 NoRepeat). This background image is only suppose to print on the first page. When the report was still in SQL 2005 it printed fine,
with the image displaying on the first page but NOT on the second page. After the conversion to SQL 2008 I noticed that the image is now printing on both pages.
Please advise on the way forward. Is there another property that I need to provide to make the image only print on the first page?
Your response will be much appresiated.
Kind Regards
Ronelle

Hi Ronelle,
The
BackgroundRepeat property indicates how the background image fills the available space. So if set the property to
Clip in Reporting Services 2008 or NoRepeat in Reporting Services 2005, the background image will not repeat in both horizontal and vertical in current page, but it will be displayed as background in every
page.
However, as you mentioned, the background image only print on the first page as you desired in your report in Reporting Services 2005. If you achieve this just by setting the
BackgroundRepeat property to NoRepeat, could please post the specific version of your Reporting Services 2005 which you can find it in the bottom of your Report Server pages? It will be helpful for us to provide you
further assistance.
If you have any question, please feel free to ask.
Best Regards,
Tony Chain

Error in sql 2008 reporting services with sharepoint 2013

i have database sql 2008r2 and sharepoint 2013 enterprise
database is in cluster server and sharepoint have 2 servers one for webfront end and one for services.
im tring to configer ssrs in the web front end server for sharepoint and i install sql 2008 add on for sharepoint 2010 but still have this error
The configuration parameter SharePointIntegrated is set to True but Share
Point Object Model cannot be loaded. The error was:
System.IO.FileNotFoundException: Could not load file or assembly
'Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot
find the file specified. File name: 'Microsoft.SharePoint, Version=14.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c' at
Microsoft.ReportingServices.SharePoint.Objects.RSSPImpSecurity.set_StaticCatchAccessDeniedException(Boolean
value) at
Microsoft.ReportingServices.SharePoint.Server.SharePointServiceHelper..ctor() at
Microsoft.ReportingServices.SharePoint.Server.SharePointServiceHelperFactory.get_ServiceHelper()
WRN: Assembly binding logging is turned OFF. To enable assembly bind failure
logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]
(DWORD) to 1. Note: There is some performance penalty associated with assembly
bind failure logging. To turn this feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog]. .
(rsSharePointObjectModelNotInstalled)
and befour that i was install sql 2012 add on for sharepoint 2013 but was the same error so i did uninstall for it
this error when i try to open reporting services url
Thanks for any help :) my blog is: http://www.waelk.com

SharePoint 2013 only supports SSRS 2012 SP1 - http://msdn.microsoft.com/en-us/library/gg492257.aspx. You'll need to upgrade your SSRS instance to 2012 SP1.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

XL Reporter in Sap 8.8 PL 16running On Server 2008 R2 and SQL 2008 R2

Within the above environment (XL Reporter in Sap 8.8 PL 16 running On Server 2008 R2 and SQL 2008 R2)
Xl reporter is loading and appears to work fine until you look at the spreadsheet result
It is completely blank except for the titles
Yet Excel Macros and the attachment paths are defined correctly
As can be seen when we export any report to Excel successfully
I've had another consultant look at my setup carefully just to be sure
He can't figure out why
Anyone with similar results
I would appreciate any comments
Georges Ostiguy

Even something as simple as a list of BP 's and phone number gives a blank report
When my friend who knows xl reporter much more than I do tried, he managed to get the
BP numbers but nothing further
I then brought him to another server with the same configuration , same result
He then tried it on one of his own servers with similar config = same result
Server 2008 Standard R2 64bit
MSSQL 2008 R2
SAP 8.8 PL 16
Sample demo database
I don't get it

P6 v.7 configuration question (SQL 2008)

Similar Messages

Maybe you are looking for