Hello!

I am trying to deploy my own .NET-written OLAP-client. I use my own setup
program (Inno setup-based). My app can browse OLAP-data but when it comes to
use the DSO-objects the following err msg:

"CANNOT CONNECT TO THE REPOSITORY ... DATASOURCE NAME TOO LONG"

The code generating this is:

Dim oDSO As New DSO.Server
oDSO.Connect("myserver") ' error generated here

Apparently, there is something wrong with the DSO-objects on the client. I
have followed the guidelines here:
http://msdn.microsoft.com/library/de...intro_4fhv.asp

but this hasn't helped. Of course I've searched extensively for the err msg.
The recommended cures has been to unregister the DSO components and then
reregister them. This do not help me.

The client I am testing on is totally clean from the beginning. Then I
install
- Windows XP SP 2
- PTSlite.exe (Pivottable services)
- DSO objects
- My app

From other computers, the client app connects successfully to the server.
This implies that the problem is not server-related, but client related. The
difference between my clean test computer is that the test computer does not
have Analysis Services installed.

I can solve the problem on my test computer by installing Analysis Services,
but since my customers seldomly will have Analysis Services installed on
their clients this is not a good solution. I have tested against servers
running AS SP3 and SP4.

Please provide me with some clues...

Regards
Clarkie

Hi

How do you installed DSO-objects on your client computer?
Have you tried to install on the client computer the DSO-objects from AS
distribution CD and AS SP3 or SP4 and after it tested your client
application?

Vladimir Chtepa

"Clarkie" <clarkbones (AT) rock (DOT) sendmenot.etmail.com> schrieb im Newsbeitrag
news:OqkXcaXFGHA.2320 (AT) TK2MSFTNGP11 (DOT) phx.gbl...

Hi,

I didn't find useful the DSO installation guidelines. I have succeeded
by doing the following:
* Create directories C:\Program Files\Common Files\Microsoft Shared\DSO
and ...\DSO\Resources\1033
* Copy msmddo80.dll, msmdlock.dll, msmdnet.dll to C:\Program
Files\Common Files\Microsoft Shared\DSO
* Copy msmdso.rll to C:\Program Files\Common Files\Microsoft
Shared\DSO\Resources\1033 (for English)
* Register msmddo80.dll, msmdlock.dll, msmdnet.dll with regsvr32
* (Non-critical) Register the file installation (you can copy/paste in
a .reg file and import):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\SharedDLLs]
"C:\\Program Files\\Common Files\\Microsoft
Shared\\DSO\\msmddo80.dll"=dword:00000001
"C:\\Program Files\\Common Files\\Microsoft
Shared\\DSO\\msmdlock.dll"=dword:00000001
"C:\\Program Files\\Common Files\\Microsoft
Shared\\DSO\\msmdnet.dll"=dword:00000001
"C:\\Program Files\\Common Files\\Microsoft
Shared\\DSO\\Resources\\1033\\msmdso.rll"=dword:00 000001

In addition I found out that a repository installation is needed:
* Create dircotory C:\Program Files\Common Files\Microsoft
Shared\Repostry
* Copy repodbc.dll to C:\Program Files\Common Files\Microsoft
Shared\Repostry
* Register repodbc.dll with regsvr32

Kind regards,

Eugen

Rectification: guidelines for DSO distribution are at
<http://msdn2.microsoft.com/en-us/library/ms135462.aspx> and they are
fine. Still in my case I had to figure out the repository part.

Kind regards,

Eugen

Server 2000 AS SP4) to the relevant directories provided in
http://msdn2.microsoft.com/en-us/library/ms135462.aspx

I have tried to register them both manually and by the setup program I have
written in Inno Setup. I also tried unregister and register again.

guess it should be latest version.

When connecting to a server running AS SP 4 the error mess is slightly
different. This is the complete exception message and innerexception
message:
Cannot connect to the repository.
OLAP server: fuji
Error:
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified System.Runtime.InteropServices.COMException (0x80040033):
Cannot connect to the repository.

OLAP server: fuji
Error:

[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified at DSO.ServerClass.Connect(String ServerName)
at MyApp.Form1.Form1_Load(Object sender, EventArgs e) in
D:\LUCmini\Test\MyApp\Form1.vb:line 51


Note: I also tried the tip about creating a folder repostry and register the
relevant dll (provided by Baxter.) but still no success.

Thanks for your help,

The link you provided I have been using, but the repository -dll thing was
new to me.
Unfortunately, it did not solve my problem.

I migrated the repository to SQL server. No success.

The test computer is a member of the same domain as the servers.

"Baxter" <eugen.baloc (AT) jt-int (DOT) com> wrote

does the target user is member of the "OLAP Administrator" group? (Local
Windows NT Security Group on the server)

does your AS repository is store in Access (default) or in an SQL Server
database?
if Access, veruify that the user can access the shared folder
\\server\MSOLAPRepository$ (or a name like this)

verify that the user can access the
HKLM/Software/Microsoft/OLAPServer/OLAPConnection (not sure for the name)
registry key
the OLAP Administrators group must access this key, and specially a sub key
which contains the repository connectionstring.

"Clarkie" <clarkbones (AT) rock (DOT) sendmenot.etmail.com> wrote

Regarding users I have tried everything, pretty much. I will describe the
domain.
Domain name: lucorp.com
Client Computer name: EURO (Windows XP SP2 and some updates, MDAC 2.81,
PTSLite.exe from Analysis Services SP4, DSO Objects from AS SP4 )
OLAP-Server 1 name: LUC
OLAP-Server 2 name: FUJI
Account logged in on EURO: lee

The account lee is member of lucorp\Domain Admins group, Lucorp\OLAP
administrator group, lucorp\Enterprise Admin.

Both on EURO and on LUC there are local accounts named "lee" which
administrative priviligies, all with exactly the same password as the domain
account lee.

I have created a UDL-file and connected to the repository successfully from
the udl. The connection string I used was:
Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=\\LUC\MsOLAPRepository$\msmdrep.mdb;Persist Security Info=False

On LUC D:\Program Files\Microsoft Analysis Services\bin I have granted full
access to Lucorp\Domain Admins, LUC\OLAP Admins, Lucorp\OLAP Admins and
Lucorp\Everyone.

The LUC server runs under Local System Account.

On OLAP server FUJI, I have migrated the repository to SQL Server, the error
remains the same.

I have given full access for most accounts to the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLAP Server\Server Connection Info
on server LUC.

When using a "dumb" client as I do ( I want to mimick customers' computers)
I can't understand what account is used. If I do install Analysis Services I
have no problem. I can't figure out if this is a
security issue or a DSO issue.

I been working on this problem for three days now...

Regards!

Clarkie




"Jéjé" <willgart (AT) BBBhotmailAAA (DOT) com> wrote

which SP is installed on both client and server sides?

I think you have try a lot of things!!! :-)
(too many ;-))

"Clarkie" <clarkbones (AT) rock (DOT) sendmenot.etmail.com> wrote

In article <#u$oJ#iFGHA.3176 (AT) TK2MSFTNGP12 (DOT) phx.gbl>,
clarkbones (AT) rock (DOT) sendmenot.etmail.com says...
If you are relying on the account mapping you should know that only
local accounts can map to other local accounts. A Domain account will
not produce the same hash and will not map to a local account.

If you set up a local account on the client with the same
username/password and logged on to the client using that account it
would map to the local accounts on the servers.

HTH

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell