If it could not reach the server by name, please try the IP address. The expected result is that the ping is able to resolve the host name to an IP address and connect to the machine.
There is probably a simple answer to this question but I do not have much experience with SQL Server/SSAS. I can connect to my local server PCNAMESQLEXPRESS in SQL Server 2008. On that server I have made a database, some dimension tables, and a fact table that I intend to build a cube from.
I have been following tutorials on the internet on how to build a cube. I can successfully make a data source that connects to PCNAMESQLEXPRESS, as well as make a data source view from it.
The problem is that after I build the cube, I get
A connection cannot be made. Ensure that the server is running.
and cannot process the cube. BIDS is displaying the star schema of my tables just fine, recognizes the relationships via foreign keys, etc... so I figured the server was running since it could access all of that data.Does anyone know why this is happening, and if my server really isn't running can someone tell me how to start it? I am using SQL Server 2008 R2.
Thanks,Logan
edit: I just tried to change the server name to PCNAMESQLEXPRESS instead of localhost in the Properties->Deployment option menu. I get
A connection cannot be made to redirector. Ensure that 'SQL Browser' is running.
Logan SermanLogan Serman
2 Answers
I solved this problem - for people that find this page on Google in the future: when I first installed SQL Server, the SSAS part failed to install. I uninstalled SQL Server and when I reinstalled, I looked deeper into the issue. Apparently one of the services needed to run SSAS has a weird bug where it cannot be started if your Event Log is full. I finished the installation of SQL Server, cleared my Event Log (Administrative Tools -> Event Viewer -> Click Each Log and go to Action -> Clear All Events), and then started the SSAS service in the SQL Configuration Manager.
Logan SermanLogan Serman
You can start by going to 'Programs->Microsoft SQL Server 2008->Configuration Tools->SQL Server Configuration Manager'. Once there, you need to start the services 'SQL Server', 'SQL Server Analysis Services', and maybe try starting 'SQL Server Browser', though I believe that is not necessary.
LamakLamak
Not the answer you're looking for? Browse other questions tagged sqlsql-serverssasbidscubes or ask your own question.
Siebel Installation Guide for Microsoft Windows > Configuring Siebel Enterprise Server and Related Components > Verifying the ODBC Data Source >
Verifying the ODBC Data Source for Oracle
This topic is part of Verifying the ODBC Data Source.
The Siebel Server installation program automatically creates an ODBC system data source name (DSN) that it uses to connect to the Siebel Database on the RDBMS. Prior to verifying the Siebel Server ODBC data source, make sure that the Siebel Server service is started.
Information in this topic applies also to virtual ODBC data sources in a clustered environment.
CAUTION: In general, do not change the default settings created automatically with the ODBC data source. However, if you have upgraded from Oracle 8i or 9i (RBO) to Oracle 10g (CBO), or if you manually created your ODBC, it is critical that you check your ODBC settings, as shown in the following procedure.
For more information about the ODBC data source, see Planning RDBMS Installation and Configuration.
To verify the ODBC data source for Oracle (on Windows)
- Navigate to Control Panel, Administrative Tools, then Data Sources (ODBC).
- On the ODBC Data Source Administrator dialog box, select the System DSN tab.
- Review the data source name; its default name is EnterpriseName_DSN, where EnterpriseName is the name you gave the Siebel Enterprise during its configuration.
- Record the name of the ODBC data source in Deployment Planning Worksheet if you have not already done so.
- Select the data source EnterpriseName_DSN, and click Configure. The ODBC Oracle Driver Setup screen appears.
- To test the connection, click Test Connect. If the connection is valid, you will see a message box confirming the connection.If the connection could not be made, see Verifying Network Connectivity for the Siebel Server Machine and Troubleshooting the ODBC Data Source Connection.
- In the Windows registry, locate the following registry entry: [HKEY_LOCAL_MACHINESOFTWAREODBCODBC.INI
EnterpriseName
_DSN]Verify that the following registry keys are set as shown. These values are required in order for the ODBC driver to behave correctly.PacketSize = 0
EnableScrollableCursors = 0
ColumnsAsChar = 1
ColumnSizeAsCharacter = 1