If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Contributor Architecture

Started by StuartS, 14 May 2008 10:57:13 AM

Previous topic - Next topic

StuartS

Hello

I am building a contributor installation of several machines.

I wish to know how the Application server (i.e. machine with Contributor) communicates to the Server hosting SQL.  I assume you do not need IIS on the SQL machine?

Do I need the Contributor server components on the SQL Server??

Contributor is version 8.1
OS is Windows 2003 Server Standard.

Thanks

Stuart

ducthcogtechie

You only need IIS on the application server.
you do not need to install Contributor on the sql server.
Don´t forget to install the sql server client tools on the application server including the sql server SP level as the server has.

StuartS

Hello

A further question.

I have my Application server running Contributor with IIS configured.  This has the SQL client tools installed.

I have my SQL server configured with COM+ connectivity and install of SQL Server 2005 Standard with SP1.

I get the Unable to connect EAdmin_74.iDB error.

Any thoughts about what Im missing?

Thanks

Stuart

ducthcogtechie

Database connectivity is through an oledb call, not a com call (that is only between jobservers configured to use com communication)
Are you using trusted or a sql account to connect to the DB?
Where do you get your error?

StuartS

Hi

I get my error when first starting the CAC and configuring.  Where you set the remote connection information.  I am entering the name of the SQL server and selecting COM, (as I suppose Http wouldnt work without IIS).

I am now doubting myself.  Should I be using localhost on the remote connection information, and then the name of the SQL server  when creating the PAD.

I have a feeling of DOH.

Stuart

ducthcogtechie

When you first start the CAC and the PAD tables are empty, in the wizzard you type in the hostname of the application server and select com for communication type.
Before you can do that you need to make sure that the com+ package PLANNING73 isup and running and that the identity on which it runs has been switched from localsystem to an a ccount that is a member of the local admingroup on the application server. Then swap the planning NT service for that same account.

Then inside CAC you create a datastore which is the oledb call i mentioned. (with trusted/non trusted)

StuartS

Thank you.

Yep the DOH stands..


StuartS

Hello

I tried the below from the link above.

Install Microsoft SQL Server 2005 Express Edition
Microsoft SQL Server 2005 Express Edition is the free, easy-to-use, lightweight version of SQL Server 2005. Integrated with Microsoft Visual Studio 2005, SQL Server Express makes it easy to develop data-driven applications that are rich in capability, offer enhanced storage security, and are fast to deploy. SQL Server Express is free to redistribute and can be seamlessly upgraded to more sophisticated versions of SQL Server.

Download * (36.5 MB)

And it didnt work.

I am aware (I believe) that the CAC uses SQLDMO.dll to communicate.  I have looked here http://support.microsoft.com/kb/248241 but am getting increasingly confused as to how to get this to work.

Can I register SQLDMO.dll instead of installing the SQL client components.  Just seems cleaner if I can get this to work.

Hope I am making sense. 

Stuart

ducthcogtechie

You are using the sqloledb.dll to communicate which is allready present in mdac.
The client tools are needed to read out the shares on the sql server.

StuartS

Hi

Ah, just realised I crossed threads.  Sorry the above post by me and this post should have been in 'Unable to get list of drives'.  Ill stick with this one now.


This is what I have done.  Please advise if I have missed anything.

Setup specific user on SQL server with sysAdmin rights

Installed MSMXL 6.0, (msxml6_x86.msi)
Installed SQLEXPR32.exe (Client Components)
Installed SQLServer2005_SSMEE.msi

Im still getting unable to list drives inside CAC on PAD setup.

Stuart

ducthcogtechie

What's the error you get when trying to browse the list?

StuartS

Hi

When trying to browse for the 'Location of SQL Server files' I get the 'Locate Folder' dialog box open, but underneath the SQL Server name I get a red circle with line and the message Unable to get list of drives.

Stuart

ducthcogtechie

Are you using trusted or non trusted?

StuartS

Hi

Am using untrusted.  I.e. specific SQL logon.

But have tried trusted and also same error.

Stuart

StuartS

Hello

I have swapped between threads.  This is posted in both threads to close this out..

Here is the conclusion to my problem.  This fixed my problem, hopefully the below can help someone else.

Recap.
Contributor on one server, SQL on another server.  Unable to get list of drives when creating PAD on Contributor server.


As mentioned in a Cognos document the SQL server distributed (SQLDMO) components are utilised by 8.1.  SQLDMO is a SQL 2000 technology.  Microsoft have replaced SQLDMO with SQLSMO in 2005.

The native client 2005 does not include SQLDMO.  Therefore installing native client 2005 on your contributor server does not fix the problem.  I personally found that Express did not include SQLDMO, although other posts seem to suggest is does.  Note, timing of posts in relation to software MS makes available for download, i.e. versions....

I downloaded the Backwards compatability components and installed them.  This installed SQLDMO.  It fixed my problem.

http://www.microsoft.com/downloads/details.aspx?FamilyID=50b97994-8453-4998-8226-fa42ec403d17&displaylang=en

and

Microsoft SQL Server 2005 Backward Compatibility Components
The SQL Server Backward Compatibility package includes the latest versions of Data Transformation Services 2000 runtime (DTS), SQL Distributed Management Objects (SQL-DMO), Decision Support Objects (DSO), and SQL Virtual Device Interface (SQLVDI). These versions have been updated for compatibility with SQL Server 2005 and include all fixes shipped through SQL Server 2000 SP4.

Audience(s): Customer, Partner, Developer


X86 Package (SQLServer2005_BC.msi) - 11258 KB


Thanks

Stuart