June 3, 2003 at 9:34 pm
The Analysis Server of my customer has intermitent problems with connecting remotely from other servers. When I try to connect to it using Analysis Manager locally, everything works fine. But if I connect to it from another machine on the network, sometimes a message box pops up saying "Bad file name or server" and it does not connect. I have DTS package that processes the cube and it didn't work because of the same issue. The error message is:
DTSRun OnStart: DTSStep_DTSOlapProcess.Task_2
DTSRun OnError: DTSStep_DTSOlapProcess.Task_2, Error = -2146828236 (800A0034)
Error string: A duplicate name exists on the network.
Error source: Microsoft Data Transformation Services (DTS) Package Help . The step failed.
Step Error Source: Microsoft Data Transformation Services (DTS) Package
Step Error Description:A duplicate name exists on the network.
(DSO (80004005): Bad file name or number)
Step Error code: 800A0034
Step Error Help File:sqldts80.hlp
Step Error Help Context ID:700
All of the SQL Server and Analysis Servers are updated to SP3, and this problem persists. This has been a pain. Any help would be appreciated!
Alan Kan
Consultant - Business Intelligence
Edited by - alankan on 06/03/2003 9:35:14 PM
Alan Kan
Consultant - Business Intelligence
June 6, 2003 at 8:00 am
This was removed by the editor as SPAM
June 9, 2003 at 4:01 am
I did a search on the phrase "A duplicate name exists on the network" on http://support.microsoft.com. I would guess that you have a WINS problem, one of the computers are registered with the same name on two different IP-numbers.
June 9, 2003 at 4:11 am
How is your connection defined?
June 9, 2003 at 5:44 am
Hi alankan,
We encountered the same problem some time back on our development server. By default, Analysis Services has Access database as its data repository. We changed this to have a SQL Server database and everything was ok there on.
skraj
June 9, 2003 at 5:21 pm
Thanks a lot for your replies, people.
I tend to think that we don't have 2 machines with the same IP numbers, as everything else on the network works fine. But I'll check that with network admin.
The connection is done in Analysis Manager on a remote machine. Also DTS OLAP task is used to connect to it. (Sorry I don't quite get the question. Is this what you're after, Antares686?)
We are currently using SQL Server as the data repository. But the Querylog is still in MSAccess and I occasionally get #error# in the Access file. I usually just copy the good rows to a new file and cover the old query log file with the new one. May be that's the issue?
Alan Kan
Consultant - Business Intelligence
Alan Kan
Consultant - Business Intelligence
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply