DTS designer

64b SQL2005 EE and all clent tools installed on the same server. Logged as
local admin user Im trying to create a new connection in DTS Designer but
after succesful test of the connection it errors out with
The new connection manager couldnt be created. Additional info : Exeption
from HRESULT 0xC0010014
Do you know if the client tools are installed by default in x86 Program
files folder and is it possible uninstalling and reinstalling in Program
files will fix the issue?
Any idea whats the problem and how to fix it ?
In our case the problem was SP1 unfinished /unsuccesful instalation. After
sql2005 setup REBOOT and when is up stop all sql services from Control panel
and then install SP1. Ensure you dont get open files errors if so close the
guilty apps and then continue and if so reapply the SP1 once again.
"Ellie" wrote:

> 64b SQL2005 EE and all clent tools installed on the same server. Logged as
> local admin user Im trying to create a new connection in DTS Designer but
> after succesful test of the connection it errors out with
> The new connection manager couldnt be created. Additional info : Exeption
> from HRESULT 0xC0010014
> Do you know if the client tools are installed by default in x86 Program
> files folder and is it possible uninstalling and reinstalling in Program
> files will fix the issue?
> Any idea whats the problem and how to fix it ?
>

DTS / Export Data in Sql2005 Mgm Studio

Dear all,

I have a SQL 2000 and SQL 2005 servers separately, but by whatever reason, I can't use SQL 2000 Enterprise Mgr anymore now so I have to use SQL 2005 Mgm studio to open up my SQL 2000 databases now.

However, I'd like to export data from Sql 2000 to another Sql 2000 server, but via a Sql 2005 mgm studio interface right now. How can I do so? I can't find "Export Data" from the "Task" context menu in Sql 2005 mgm studio.

Thanks,

Hi,

if you want to use the SQL Server MS for that you have to right click on whatever database on choose Tasks..Export data. That should be straight forward for you like in SQL 2k days.

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de

DTC Error and unresolved SQL transaction

I have a procedure that reads data from linked server, a SQL2005 box, and
writes a row in a SQL2000 database. This procedure and configuration have
been working successfully for several years. This Sunday at 4am, this
procedure failed to complete, leaving an unresolved transaction. The symptom
is an insert on this table will timeout and fail because the unresolved
transaction has a lock on the table, and it shows as a blocking transaction.
Otherwise the database is functional and responsive. I have tried to KILL the
unresponsive process, but it wont clear, and just reads "KILLED/ROLLED BACK"
under the Activity Monitor command column.
I had this same problem last weekend, and re-starting the SQL Server Service
resolved the transaction. However, this is not a viable option during
production hours.
I tried using "KILL 51 WITH STATUSONLY", and it returned:
SPID 51: transaction rollback in progress. Estimated rollback completion:
100%. Estimated time remaining: 0 seconds.
I tried using KILL "51457D54-4FD7-408A-B5CA-AFF33D601D00"
It it cam back with:
Server: Msg 6114, Level 16, State 1, Line 1
Distributed transaction with UOW {51457D54-4FD7-408A-B5CA-AFF33D601D00} is
being used by another user. KILL command failed.
My two questions are:
1) Is there anyway to clear this blocking transaction short of re-starting
the SQL Server?
2) Is there anyway to figure out the root cause of the problem? I believe it
is some sort of MSDTC issue, that seems to only happen early on Sunday
mornings.
The following DTC error happened at exactly the same timestamp as the SQL
procedure was executed.
___________________________________________
Application Event Log Error
___________________________________________
Date7/1/2007 4:09:31 AM
LogWindows NT (Application)
SourceMSDTC
Category(3)
Event3221229829
ComputerSERVER002
Message
The description for Event ID '-1073737467' in Source 'MSDTC' cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display the message, or you may not have permission to
access them. The following information is part of the
event:'.\iomgrclt.cpp:204, Pid: 1300, CmdLine: C:\WINNT\System32\msdtc.exe'
___________________________________________
Thank you in advance,
Ken
Hi Ken
"KenL" wrote:

> I have a procedure that reads data from linked server, a SQL2005 box, and
> writes a row in a SQL2000 database. This procedure and configuration have
> been working successfully for several years. This Sunday at 4am, this
> procedure failed to complete, leaving an unresolved transaction. The symptom
> is an insert on this table will timeout and fail because the unresolved
> transaction has a lock on the table, and it shows as a blocking transaction.
> Otherwise the database is functional and responsive. I have tried to KILL the
> unresponsive process, but it wont clear, and just reads "KILLED/ROLLED BACK"
> under the Activity Monitor command column.
> I had this same problem last weekend, and re-starting the SQL Server Service
> resolved the transaction. However, this is not a viable option during
> production hours.
> I tried using "KILL 51 WITH STATUSONLY", and it returned:
> SPID 51: transaction rollback in progress. Estimated rollback completion:
> 100%. Estimated time remaining: 0 seconds.
> I tried using KILL "51457D54-4FD7-408A-B5CA-AFF33D601D00"
> It it cam back with:
> Server: Msg 6114, Level 16, State 1, Line 1
> Distributed transaction with UOW {51457D54-4FD7-408A-B5CA-AFF33D601D00} is
> being used by another user. KILL command failed.
> My two questions are:
> 1) Is there anyway to clear this blocking transaction short of re-starting
> the SQL Server?
> 2) Is there anyway to figure out the root cause of the problem? I believe it
> is some sort of MSDTC issue, that seems to only happen early on Sunday
> mornings.
> The following DTC error happened at exactly the same timestamp as the SQL
> procedure was executed.
> ___________________________________________
> Application Event Log Error
> ___________________________________________
> Date7/1/2007 4:09:31 AM
> LogWindows NT (Application)
> SourceMSDTC
> Category(3)
> Event3221229829
> ComputerSERVER002
> Message
> The description for Event ID '-1073737467' in Source 'MSDTC' cannot be
> found. The local computer may not have the necessary registry information or
> message DLL files to display the message, or you may not have permission to
> access them. The following information is part of the
> event:'.\iomgrclt.cpp:204, Pid: 1300, CmdLine: C:\WINNT\System32\msdtc.exe'
> ___________________________________________
> Thank you in advance,
> Ken
I am not a MSDTC expert!!! Which process did you kill? I would expect a
process on the remote and local (originator) machines, and if there was an
order to be killed then local would be the first. If you stopped the DTC
services (NET STOP MSDTC) it should also rollback, but all distributed
transactions would be affected.
Is this the only time distributed transaction are used? If not then it would
narrow the issue down to either something with the process or something that
happens at that time. If the process is scheduled and works at other times
then it would rule the process out. If it is something that happens at a
specific time, check things like firewalls or antivirus updates/scans etc.
http://support.microsoft.com/default.aspx/kb/306843
Also look for blocking occuring during the process and how you handle errors
such as deadlocks in the code.
You could use DTCTester http://support.microsoft.com/kb/293799 or DTCPing to
check that DTC works ok.
John
|||Thank you for the response John.
<Is this the only time distributed transaction are used?
No, there are many procedures on this server that link to databases on
another server. The stored procedure that is failing runs hundreds of times
in a day. It had been reliable for years, up until last Sunday and this
Sunday when I have seen the two failures
<Which process did you kill?
I killed the spid on the SQL server initiating the link
I will review the kb's you referenced
Thanks,
Ken
"John Bell" wrote:

> Hi Ken
> "KenL" wrote:
>
> I am not a MSDTC expert!!! Which process did you kill? I would expect a
> process on the remote and local (originator) machines, and if there was an
> order to be killed then local would be the first. If you stopped the DTC
> services (NET STOP MSDTC) it should also rollback, but all distributed
> transactions would be affected.
> Is this the only time distributed transaction are used? If not then it would
> narrow the issue down to either something with the process or something that
> happens at that time. If the process is scheduled and works at other times
> then it would rule the process out. If it is something that happens at a
> specific time, check things like firewalls or antivirus updates/scans etc.
> http://support.microsoft.com/default.aspx/kb/306843
> Also look for blocking occuring during the process and how you handle errors
> such as deadlocks in the code.
> You could use DTCTester http://support.microsoft.com/kb/293799 or DTCPing to
> check that DTC works ok.
> John

DTC Error and unresolved SQL transaction

I have a procedure that reads data from linked server, a SQL2005 box, and
writes a row in a SQL2000 database. This procedure and configuration have
been working successfully for several years. This Sunday at 4am, this
procedure failed to complete, leaving an unresolved transaction. The symptom
is an insert on this table will timeout and fail because the unresolved
transaction has a lock on the table, and it shows as a blocking transaction.
Otherwise the database is functional and responsive. I have tried to KILL th
e
unresponsive process, but it wont clear, and just reads "KILLED/ROLLED BACK"
under the Activity Monitor command column.
I had this same problem last weekend, and re-starting the SQL Server Service
resolved the transaction. However, this is not a viable option during
production hours.
I tried using "KILL 51 WITH STATUSONLY", and it returned:
SPID 51: transaction rollback in progress. Estimated rollback completion:
100%. Estimated time remaining: 0 seconds.
I tried using KILL "51457D54-4FD7-408A-B5CA-AFF33D601D00"
It it cam back with:
Server: Msg 6114, Level 16, State 1, Line 1
Distributed transaction with UOW {51457D54-4FD7-408A-B5CA-AFF33D601D00}
is
being used by another user. KILL command failed.
My two questions are:
1) Is there anyway to clear this blocking transaction short of re-starting
the SQL Server?
2) Is there anyway to figure out the root cause of the problem? I believe it
is some sort of MSDTC issue, that seems to only happen early on Sunday
mornings.
The following DTC error happened at exactly the same timestamp as the SQL
procedure was executed.
________________________________________
___
Application Event Log Error
________________________________________
___
Date 7/1/2007 4:09:31 AM
Log Windows NT (Application)
Source MSDTC
Category (3)
Event 3221229829
Computer SERVER002
Message
The description for Event ID '-1073737467' in Source 'MSDTC' cannot be
found. The local computer may not have the necessary registry information o
r
message DLL files to display the message, or you may not have permission to
access them. The following information is part of the
event:'.\iomgrclt.cpp:204, Pid: 1300, CmdLine: C:\WINNT\System32\msdtc.exe'
________________________________________
___
Thank you in advance,
KenHi Ken
"KenL" wrote:

> I have a procedure that reads data from linked server, a SQL2005 box, and
> writes a row in a SQL2000 database. This procedure and configuration have
> been working successfully for several years. This Sunday at 4am, this
> procedure failed to complete, leaving an unresolved transaction. The sympt
om
> is an insert on this table will timeout and fail because the unresolved
> transaction has a lock on the table, and it shows as a blocking transactio
n.
> Otherwise the database is functional and responsive. I have tried to KILL
the
> unresponsive process, but it wont clear, and just reads "KILLED/ROLLED BAC
K"
> under the Activity Monitor command column.
> I had this same problem last weekend, and re-starting the SQL Server Servi
ce
> resolved the transaction. However, this is not a viable option during
> production hours.
> I tried using "KILL 51 WITH STATUSONLY", and it returned:
> SPID 51: transaction rollback in progress. Estimated rollback completion:
> 100%. Estimated time remaining: 0 seconds.
> I tried using KILL "51457D54-4FD7-408A-B5CA-AFF33D601D00"
> It it cam back with:
> Server: Msg 6114, Level 16, State 1, Line 1
> Distributed transaction with UOW {51457D54-4FD7-408A-B5CA-AFF33D601D0
0} is
> being used by another user. KILL command failed.
> My two questions are:
> 1) Is there anyway to clear this blocking transaction short of re-starting
> the SQL Server?
> 2) Is there anyway to figure out the root cause of the problem? I believe
it
> is some sort of MSDTC issue, that seems to only happen early on Sunday
> mornings.
> The following DTC error happened at exactly the same timestamp as the SQL
> procedure was executed.
> ________________________________________
___
> Application Event Log Error
> ________________________________________
___
> Date 7/1/2007 4:09:31 AM
> Log Windows NT (Application)
> Source MSDTC
> Category (3)
> Event 3221229829
> Computer SERVER002
> Message
> The description for Event ID '-1073737467' in Source 'MSDTC' cannot be
> found. The local computer may not have the necessary registry information
or
> message DLL files to display the message, or you may not have permission t
o
> access them. The following information is part of the
> event:'.\iomgrclt.cpp:204, Pid: 1300, CmdLine: C:\WINNT\System32\msdtc.exe
'
> ________________________________________
___
> Thank you in advance,
> Ken
I am not a MSDTC expert!!! Which process did you kill? I would expect a
process on the remote and local (originator) machines, and if there was an
order to be killed then local would be the first. If you stopped the DTC
services (NET STOP MSDTC) it should also rollback, but all distributed
transactions would be affected.
Is this the only time distributed transaction are used? If not then it would
narrow the issue down to either something with the process or something that
happens at that time. If the process is scheduled and works at other times
then it would rule the process out. If it is something that happens at a
specific time, check things like firewalls or antivirus updates/scans etc.
http://support.microsoft.com/default.aspx/kb/306843
Also look for blocking occuring during the process and how you handle errors
such as deadlocks in the code.
You could use DTCTester http://support.microsoft.com/kb/293799 or DTCPing to
check that DTC works ok.
John|||Thank you for the response John.
<Is this the only time distributed transaction are used?
No, there are many procedures on this server that link to databases on
another server. The stored procedure that is failing runs hundreds of times
in a day. It had been reliable for years, up until last Sunday and this
Sunday when I have seen the two failures
<Which process did you kill?
I killed the spid on the SQL server initiating the link
I will review the kb's you referenced
Thanks,
Ken
"John Bell" wrote:

> Hi Ken
> "KenL" wrote:
>
> I am not a MSDTC expert!!! Which process did you kill? I would expect a
> process on the remote and local (originator) machines, and if there was an
> order to be killed then local would be the first. If you stopped the DTC
> services (NET STOP MSDTC) it should also rollback, but all distributed
> transactions would be affected.
> Is this the only time distributed transaction are used? If not then it wou
ld
> narrow the issue down to either something with the process or something th
at
> happens at that time. If the process is scheduled and works at other times
> then it would rule the process out. If it is something that happens at a
> specific time, check things like firewalls or antivirus updates/scans etc.
> http://support.microsoft.com/default.aspx/kb/306843
> Also look for blocking occuring during the process and how you handle erro
rs
> such as deadlocks in the code.
> You could use DTCTester http://support.microsoft.com/kb/293799 or DTCPing
to
> check that DTC works ok.
> John

DTC Error and unresolved SQL transaction

I have a procedure that reads data from linked server, a SQL2005 box, and
writes a row in a SQL2000 database. This procedure and configuration have
been working successfully for several years. This Sunday at 4am, this
procedure failed to complete, leaving an unresolved transaction. The symptom
is an insert on this table will timeout and fail because the unresolved
transaction has a lock on the table, and it shows as a blocking transaction.
Otherwise the database is functional and responsive. I have tried to KILL the
unresponsive process, but it wont clear, and just reads "KILLED/ROLLED BACK"
under the Activity Monitor command column.
I had this same problem last weekend, and re-starting the SQL Server Service
resolved the transaction. However, this is not a viable option during
production hours.
I tried using "KILL 51 WITH STATUSONLY", and it returned:
SPID 51: transaction rollback in progress. Estimated rollback completion:
100%. Estimated time remaining: 0 seconds.
I tried using KILL "51457D54-4FD7-408A-B5CA-AFF33D601D00"
It it cam back with:
Server: Msg 6114, Level 16, State 1, Line 1
Distributed transaction with UOW {51457D54-4FD7-408A-B5CA-AFF33D601D00} is
being used by another user. KILL command failed.
My two questions are:
1) Is there anyway to clear this blocking transaction short of re-starting
the SQL Server?
2) Is there anyway to figure out the root cause of the problem? I believe it
is some sort of MSDTC issue, that seems to only happen early on Sunday
mornings.
The following DTC error happened at exactly the same timestamp as the SQL
procedure was executed.
___________________________________________
Application Event Log Error
___________________________________________
Date 7/1/2007 4:09:31 AM
Log Windows NT (Application)
Source MSDTC
Category (3)
Event 3221229829
Computer SERVER002
Message
The description for Event ID '-1073737467' in Source 'MSDTC' cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display the message, or you may not have permission to
access them. The following information is part of the
event:'.\iomgrclt.cpp:204, Pid: 1300, CmdLine: C:\WINNT\System32\msdtc.exe'
___________________________________________
Thank you in advance,
KenHi Ken
"KenL" wrote:
> I have a procedure that reads data from linked server, a SQL2005 box, and
> writes a row in a SQL2000 database. This procedure and configuration have
> been working successfully for several years. This Sunday at 4am, this
> procedure failed to complete, leaving an unresolved transaction. The symptom
> is an insert on this table will timeout and fail because the unresolved
> transaction has a lock on the table, and it shows as a blocking transaction.
> Otherwise the database is functional and responsive. I have tried to KILL the
> unresponsive process, but it wont clear, and just reads "KILLED/ROLLED BACK"
> under the Activity Monitor command column.
> I had this same problem last weekend, and re-starting the SQL Server Service
> resolved the transaction. However, this is not a viable option during
> production hours.
> I tried using "KILL 51 WITH STATUSONLY", and it returned:
> SPID 51: transaction rollback in progress. Estimated rollback completion:
> 100%. Estimated time remaining: 0 seconds.
> I tried using KILL "51457D54-4FD7-408A-B5CA-AFF33D601D00"
> It it cam back with:
> Server: Msg 6114, Level 16, State 1, Line 1
> Distributed transaction with UOW {51457D54-4FD7-408A-B5CA-AFF33D601D00} is
> being used by another user. KILL command failed.
> My two questions are:
> 1) Is there anyway to clear this blocking transaction short of re-starting
> the SQL Server?
> 2) Is there anyway to figure out the root cause of the problem? I believe it
> is some sort of MSDTC issue, that seems to only happen early on Sunday
> mornings.
> The following DTC error happened at exactly the same timestamp as the SQL
> procedure was executed.
> ___________________________________________
> Application Event Log Error
> ___________________________________________
> Date 7/1/2007 4:09:31 AM
> Log Windows NT (Application)
> Source MSDTC
> Category (3)
> Event 3221229829
> Computer SERVER002
> Message
> The description for Event ID '-1073737467' in Source 'MSDTC' cannot be
> found. The local computer may not have the necessary registry information or
> message DLL files to display the message, or you may not have permission to
> access them. The following information is part of the
> event:'.\iomgrclt.cpp:204, Pid: 1300, CmdLine: C:\WINNT\System32\msdtc.exe'
> ___________________________________________
> Thank you in advance,
> Ken
I am not a MSDTC expert!!! Which process did you kill? I would expect a
process on the remote and local (originator) machines, and if there was an
order to be killed then local would be the first. If you stopped the DTC
services (NET STOP MSDTC) it should also rollback, but all distributed
transactions would be affected.
Is this the only time distributed transaction are used? If not then it would
narrow the issue down to either something with the process or something that
happens at that time. If the process is scheduled and works at other times
then it would rule the process out. If it is something that happens at a
specific time, check things like firewalls or antivirus updates/scans etc.
http://support.microsoft.com/default.aspx/kb/306843
Also look for blocking occuring during the process and how you handle errors
such as deadlocks in the code.
You could use DTCTester http://support.microsoft.com/kb/293799 or DTCPing to
check that DTC works ok.
John|||Thank you for the response John.
<Is this the only time distributed transaction are used?
No, there are many procedures on this server that link to databases on
another server. The stored procedure that is failing runs hundreds of times
in a day. It had been reliable for years, up until last Sunday and this
Sunday when I have seen the two failures
<Which process did you kill?
I killed the spid on the SQL server initiating the link
I will review the kb's you referenced
Thanks,
Ken
"John Bell" wrote:
> Hi Ken
> "KenL" wrote:
> > I have a procedure that reads data from linked server, a SQL2005 box, and
> > writes a row in a SQL2000 database. This procedure and configuration have
> > been working successfully for several years. This Sunday at 4am, this
> > procedure failed to complete, leaving an unresolved transaction. The symptom
> > is an insert on this table will timeout and fail because the unresolved
> > transaction has a lock on the table, and it shows as a blocking transaction.
> > Otherwise the database is functional and responsive. I have tried to KILL the
> > unresponsive process, but it wont clear, and just reads "KILLED/ROLLED BACK"
> > under the Activity Monitor command column.
> > I had this same problem last weekend, and re-starting the SQL Server Service
> > resolved the transaction. However, this is not a viable option during
> > production hours.
> >
> > I tried using "KILL 51 WITH STATUSONLY", and it returned:
> > SPID 51: transaction rollback in progress. Estimated rollback completion:
> > 100%. Estimated time remaining: 0 seconds.
> >
> > I tried using KILL "51457D54-4FD7-408A-B5CA-AFF33D601D00"
> > It it cam back with:
> > Server: Msg 6114, Level 16, State 1, Line 1
> > Distributed transaction with UOW {51457D54-4FD7-408A-B5CA-AFF33D601D00} is
> > being used by another user. KILL command failed.
> >
> > My two questions are:
> > 1) Is there anyway to clear this blocking transaction short of re-starting
> > the SQL Server?
> > 2) Is there anyway to figure out the root cause of the problem? I believe it
> > is some sort of MSDTC issue, that seems to only happen early on Sunday
> > mornings.
> >
> > The following DTC error happened at exactly the same timestamp as the SQL
> > procedure was executed.
> > ___________________________________________
> > Application Event Log Error
> > ___________________________________________
> > Date 7/1/2007 4:09:31 AM
> > Log Windows NT (Application)
> >
> > Source MSDTC
> > Category (3)
> > Event 3221229829
> > Computer SERVER002
> >
> > Message
> > The description for Event ID '-1073737467' in Source 'MSDTC' cannot be
> > found. The local computer may not have the necessary registry information or
> > message DLL files to display the message, or you may not have permission to
> > access them. The following information is part of the
> > event:'.\iomgrclt.cpp:204, Pid: 1300, CmdLine: C:\WINNT\System32\msdtc.exe'
> > ___________________________________________
> >
> > Thank you in advance,
> > Ken
> I am not a MSDTC expert!!! Which process did you kill? I would expect a
> process on the remote and local (originator) machines, and if there was an
> order to be killed then local would be the first. If you stopped the DTC
> services (NET STOP MSDTC) it should also rollback, but all distributed
> transactions would be affected.
> Is this the only time distributed transaction are used? If not then it would
> narrow the issue down to either something with the process or something that
> happens at that time. If the process is scheduled and works at other times
> then it would rule the process out. If it is something that happens at a
> specific time, check things like firewalls or antivirus updates/scans etc.
> http://support.microsoft.com/default.aspx/kb/306843
> Also look for blocking occuring during the process and how you handle errors
> such as deadlocks in the code.
> You could use DTCTester http://support.microsoft.com/kb/293799 or DTCPing to
> check that DTC works ok.
> John

DSO in SQL2005

Anybody can share the way to administer AS2005 using DSO?

AMO (Analysis Management Objects) is the object model for administering AS2005 and it's highly recommended to be used instead of DSO 8.5 shipped in AS2005 (DSO 8.5 is DSO 8.0 with SP4 fixes and additions to support AS2005 connectivity).
DSO 8.5 is for administering databases who are:
1. migrated from AS2000 to AS2005
and
2. are not edited/maintained with the AS2005 tools or AMO

Because of the changes between AS2000 and AS2005, a total DSO compatibility with AS2005 was not obtained and these are the restrictions:
- DSO 8.5 sees only the databases from the repository (DSO8’s repository)
- DSO 8.5 does not see the databases on the AS2005 server, he only reads the repository and deploys on the AS2005 server when processing an object; in other words, new databases on AS2005 (created with AS2005 tools) are not exposed through DSO 8.5
- DSO 8.5 overwrites (if in conflict) the databases from AS2005; for example if you created a database on AS2005 with DSO 8.5, then you edit it with AS2005 tools, when using DS0 8.5 the database will be overwritten with its version from the DSO repository (the AS2005 tools do not update the DSO repository)
- Because of changes between the AS2000 and AS2005 models, DSO 8.5 has an un-optimal design, certainly not having the AMO’s speed for comparable tasks

Please note that sometimes DSO 8.5 is referred to as DSO9 (since it works with AS2005 aka AS 9.0). I am calling it DSO 8.5 because that's the actual file version.

To setup DSO 8.5 to work with AS2005, you need to:
- have the DSO repository (from AS2000); usually this is the msmdrep.mdb file from "%ProgramFiles%\Microsoft Analysis Services\Bin"
- setup AS2005 to specify connection string to the DSO repository and also the locks folder; to do this, stop the AS2005 server, edit the msmdsrv.ini file (from the AS2005 installation folder), look for the <DSO> xml section:
<DSO>
<RemoteRepositoryConnectionString/>
<RepositoryConnectionString/>
<RemoteLocksDirectory/>
<LocksDirectory/>
</DSO>
- specify values for those properties (to see what they mean, please check books online "ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/uas9/html/75e062bd-7f24-43b0-8b0b-d48437d3a116.htm")
- start the AS2005 server
- connect with DSO 8.5 (for example using Analysis Manager from AS2000); please remember you will see the databases from the repository and not the actual databases from the AS2005 server

Adrian Dumitrascu.

|||What about this errror that I get after connecting to the repository with DSO:

HAIdcom.clsDrillThrough.GetDTColumnNames(): Path not found

|||Hmm - so it seems that using DSO from an application against AS2005 is not a good idea? It sound slike from your description that the use of DSO will overwrite any modifications made directly using SQL Mgmt Studio? Thats not good.
I have been trying to use DSO also in this scenario - where is the RepositoryConnectString supposed to point to - and what provider shpuld be used? The MS documentation gives no hints to this, when I try pointing to the access mdb you suggested I get:
Errors in the OLE DB provider. The data source or location is not valid. Provide a valid server to which to connect.
If I point to the Analysis server database I want to connect to using the new Analysis 9.0 provider I get:
Query (1, 10) Parser: The syntax for ',' is incorrect.
I would have thought there would be more people trying to do this and getting similar issues?
Any help just to get back to previous functionality would be greatly appreciated, thanks.
|||Hi All.

The DSO has been replaced by the AMO.
But the problem that arises with this is as follows.
DSO was COM. So, VBA code could use the DSO to access data/metadata of AS2000.
Now, I intend to access the same in VBA/Excel.
Any idea how I could do this, since AMO is not a COM class, and can be used thru .NET.

Essentially, my intention is to document a cube of AS2005 and throw the metadata into Excel sheets.
Thanx in advance.|||Hi,
thank you for the details.
I use the DSO Object for AS2000. Where can i find the DLL for DSO 8.5 ?
I use the Interop.DSO.dll for DSO and AS 2000 and have to set e new reference in the project for DSO 8.5. With the old DSO it is not possible to acces the AS 2005 :-(
Hop somebody can help me
|||

fantasimus wrote:

Hi,
thank you for the details.
I use the DSO Object for AS2000. Where can i find the DLL for DSO 8.5 ?
I use the Interop.DSO.dll for DSO and AS 2000 and have to set e new reference in the project for DSO 8.5. With the old DSO it is not possible to acces the AS 2005 :-(
Hop somebody can help me

Fantasimus, please read the earlier posts.

The AMO is what you should be using to access SSAS (AS2005).

And as I have said earlier, the AMO is a .NET library unlike the DSO which was COM.

However, using Visual Studio 2005 Tools for Office version, one can do VBA like work, since office project templates are available with VSTO.

And then, the programming can be in c# or vb.net

|||

Thanks for all comments.

It seems our work is proved to be correct. As these reasons Adrian refered, we never used DSO any more, neight DSO 8.5. But we made the wrapper for AMO using .NET, and CCW it to make COM visiable. That's saving time to update millions of codes. For balance to our worktime, at some points, we wrapper our business layer functions directly.

Hope our solution and choice will make sense to others who are willing to lift SQL2005, thanks!

|||

Hello,

I am testing the Beta Version of MS Project Server 2007, using Analysis Services 2005 to try to build an OLAP cube. I am consistently getting the following error (see below) and this forum is the only place that I can find any information on it. I'm not a developer, so I'm not sure how (or if) this issue relates to the DSO problem that you all discussed above. Do you have any insight?

=====Process Completed=====
[11/6/2006 2:11 PM] Failed to build the OLAP cubes. Error: Analysis Services
session failed with the following error: Query (1,10) Parser: The syntax for
',' is incorrect.

Thanks,

Brian

|||

Hi Brian,

Did you get a solution for the error "Query (1,10) Parser: The syntax for
',' is incorrect. "?

I'm also getting the same error and clueless of what should be done.

Thanks

Umanga.

Posted By: bciampa on 11-07-2006 8:48 PM UTC

Subject: Re: DSO in SQL2005 Message:

Hello,

I am testing the Beta Version of MS Project Server 2007, using Analysis Services 2005 to try to build an OLAP cube. I am consistently getting the following error (see below) and this forum is the only place that I can find any information on it. I'm not a developer, so I'm not sure how (or if) this issue relates to the DSO problem that you all discussed above. Do you have any insight?

=====Process Completed=====
[11/6/2006 2:11 PM] Failed to build the OLAP cubes. Error: Analysis Services
session failed with the following error: Query (1,10) Parser: The syntax for
',' is incorrect.

Thanks,

Brian

|||

Hi guys! Have you got any solution for that error message(Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Query (1, 10) Parser: The syntax for ',' is incorrect.)?

Pls. help if you have one

Thanks

|||

Hi,

I don't have a straight answer for this problem, but let's try to debug it.

You are using DSO version 8.5 to connect to Analysis Services 2005 (after you configured AS2005 to setup the DSO-related server properties, the connection string to the repository and the lock directory).

You are able to connect, to read all the objects (although please remember that you read all the objects from the repository, not from the real AS2005 server).

And you get the error when you try to process an object ? If yes, let's try to see what commands is DSO sending to the AS2005 server before the error.

- start SQL profiler for Analysis Services

- re-run the minimal DSO code that would generate the error

- in profiler you should see the commands that DSO sent to server just before the error

- I assume you will have 2 commands: an Alter statement (for the Database probably, or maybe for a Partition if you process a Partition) followed by a Process statement, the Alter succeeds, but the Process fails; but let's check these assumptions first

Adrian Dumitrascu

|||

Any one has idea how to create roles and permissions for a SSAS cube using VB and then using AMO

I basically want to create the VB script and then want to run it through cmd prompt

please, let me know all the stepsto do all this

thanks

|||

This seems to be unrelated with the DSO in AS2005, there are these other threads about creating roles and permissions:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1795829&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1798355&SiteID=1

DSO in SQL2005

Anybody can share the way to administer AS2005 using DSO?

AMO (Analysis Management Objects) is the object model for administering AS2005 and it's highly recommended to be used instead of DSO 8.5 shipped in AS2005 (DSO 8.5 is DSO 8.0 with SP4 fixes and additions to support AS2005 connectivity).
DSO 8.5 is for administering databases who are:
1. migrated from AS2000 to AS2005
and
2. are not edited/maintained with the AS2005 tools or AMO

Because of the changes between AS2000 and AS2005, a total DSO compatibility with AS2005 was not obtained and these are the restrictions:
- DSO 8.5 sees only the databases from the repository (DSO8’s repository)
- DSO 8.5 does not see the databases on the AS2005 server, he only reads the repository and deploys on the AS2005 server when processing an object; in other words, new databases on AS2005 (created with AS2005 tools) are not exposed through DSO 8.5
- DSO 8.5 overwrites (if in conflict) the databases from AS2005; for example if you created a database on AS2005 with DSO 8.5, then you edit it with AS2005 tools, when using DS0 8.5 the database will be overwritten with its version from the DSO repository (the AS2005 tools do not update the DSO repository)
- Because of changes between the AS2000 and AS2005 models, DSO 8.5 has an un-optimal design, certainly not having the AMO’s speed for comparable tasks

Please note that sometimes DSO 8.5 is referred to as DSO9 (since it works with AS2005 aka AS 9.0). I am calling it DSO 8.5 because that's the actual file version.

To setup DSO 8.5 to work with AS2005, you need to:
- have the DSO repository (from AS2000); usually this is the msmdrep.mdb file from "%ProgramFiles%\Microsoft Analysis Services\Bin"
- setup AS2005 to specify connection string to the DSO repository and also the locks folder; to do this, stop the AS2005 server, edit the msmdsrv.ini file (from the AS2005 installation folder), look for the <DSO> xml section:
<DSO>
<RemoteRepositoryConnectionString/>
<RepositoryConnectionString/>
<RemoteLocksDirectory/>
<LocksDirectory/>
</DSO>
- specify values for those properties (to see what they mean, please check books online "ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/uas9/html/75e062bd-7f24-43b0-8b0b-d48437d3a116.htm")
- start the AS2005 server
- connect with DSO 8.5 (for example using Analysis Manager from AS2000); please remember you will see the databases from the repository and not the actual databases from the AS2005 server

Adrian Dumitrascu.

|||What about this errror that I get after connecting to the repository with DSO:

HAIdcom.clsDrillThrough.GetDTColumnNames(): Path not found

|||Hmm - so it seems that using DSO from an application against AS2005 is not a good idea? It sound slike from your description that the use of DSO will overwrite any modifications made directly using SQL Mgmt Studio? Thats not good.
I have been trying to use DSO also in this scenario - where is the RepositoryConnectString supposed to point to - and what provider shpuld be used? The MS documentation gives no hints to this, when I try pointing to the access mdb you suggested I get:
Errors in the OLE DB provider. The data source or location is not valid. Provide a valid server to which to connect.
If I point to the Analysis server database I want to connect to using the new Analysis 9.0 provider I get:
Query (1, 10) Parser: The syntax for ',' is incorrect.
I would have thought there would be more people trying to do this and getting similar issues?
Any help just to get back to previous functionality would be greatly appreciated, thanks.
|||Hi All.

The DSO has been replaced by the AMO.
But the problem that arises with this is as follows.
DSO was COM. So, VBA code could use the DSO to access data/metadata of AS2000.
Now, I intend to access the same in VBA/Excel.
Any idea how I could do this, since AMO is not a COM class, and can be used thru .NET.

Essentially, my intention is to document a cube of AS2005 and throw the metadata into Excel sheets.
Thanx in advance.|||Hi,

thank you for the details.

I use the DSO Object for AS2000. Where can i find the DLL for DSO 8.5 ?

I use the Interop.DSO.dll for DSO and AS 2000 and have to set e new

reference in the project for DSO 8.5. With the old DSO it is not

possible to acces the AS 2005 :-(

Hop somebody can help me|||

fantasimus wrote:

Hi,
thank you for the details.
I use the DSO Object for AS2000. Where can i find the DLL for DSO 8.5 ?
I use the Interop.DSO.dll for DSO and AS 2000 and have to set e new reference in the project for DSO 8.5. With the old DSO it is not possible to acces the AS 2005 :-(
Hop somebody can help me

Fantasimus, please read the earlier posts.

The AMO is what you should be using to access SSAS (AS2005).

And as I have said earlier, the AMO is a .NET library unlike the DSO which was COM.

However, using Visual Studio 2005 Tools for Office version, one can do VBA like work, since office project templates are available with VSTO.

And then, the programming can be in c# or vb.net

|||

Thanks for all comments.

It seems our work is proved to be correct. As these reasons Adrian refered, we never used DSO any more, neight DSO 8.5. But we made the wrapper for AMO using .NET, and CCW it to make COM visiable. That's saving time to update millions of codes. For balance to our worktime, at some points, we wrapper our business layer functions directly.

Hope our solution and choice will make sense to others who are willing to lift SQL2005, thanks!

|||

Hello,

I am testing the Beta Version of MS Project Server 2007, using Analysis Services 2005 to try to build an OLAP cube. I am consistently getting the following error (see below) and this forum is the only place that I can find any information on it. I'm not a developer, so I'm not sure how (or if) this issue relates to the DSO problem that you all discussed above. Do you have any insight?

=====Process Completed=====
[11/6/2006 2:11 PM] Failed to build the OLAP cubes. Error: Analysis Services
session failed with the following error: Query (1,10) Parser: The syntax for
',' is incorrect.

Thanks,

Brian

|||

Hi Brian,

Did you get a solution for the error "Query (1,10) Parser: The syntax for
',' is incorrect. "?

I'm also getting the same error and clueless of what should be done.

Thanks

Umanga.

Posted By: bciampa on 11-07-2006 8:48 PM UTC

Subject: Re: DSO in SQL2005

Message:

Hello,

I am testing the Beta Version of MS Project Server 2007, using Analysis Services 2005 to try to build an OLAP cube. I am consistently getting the following error (see below) and this forum is the only place that I can find any information on it. I'm not a developer, so I'm not sure how (or if) this issue relates to the DSO problem that you all discussed above. Do you have any insight?

=====Process Completed=====
[11/6/2006 2:11 PM] Failed to build the OLAP cubes. Error: Analysis Services
session failed with the following error: Query (1,10) Parser: The syntax for
',' is incorrect.

Thanks,

Brian

|||

Hi guys! Have you got any solution for that error message(Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Query (1, 10) Parser: The syntax for ',' is incorrect.)?

Pls. help if you have one

Thanks

|||

Hi,

I don't have a straight answer for this problem, but let's try to debug it.

You are using DSO version 8.5 to connect to Analysis Services 2005 (after you configured AS2005 to setup the DSO-related server properties, the connection string to the repository and the lock directory).

You are able to connect, to read all the objects (although please remember that you read all the objects from the repository, not from the real AS2005 server).

And you get the error when you try to process an object ? If yes, let's try to see what commands is DSO sending to the AS2005 server before the error.

- start SQL profiler for Analysis Services

- re-run the minimal DSO code that would generate the error

- in profiler you should see the commands that DSO sent to server just before the error

- I assume you will have 2 commands: an Alter statement (for the Database probably, or maybe for a Partition if you process a Partition) followed by a Process statement, the Alter succeeds, but the Process fails; but let's check these assumptions first

Adrian Dumitrascu

|||

Any one has idea how to create roles and permissions for a SSAS cube using VB and then using AMO

I basically want to create the VB script and then want to run it through cmd prompt

please, let me know all the stepsto do all this

thanks

|||

This seems to be unrelated with the DSO in AS2005, there are these other threads about creating roles and permissions:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1795829&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1798355&SiteID=1

DSO in SQL2005

Anybody can share the way to administer AS2005 using DSO?

AMO (Analysis Management Objects) is the object model for administering AS2005 and it's highly recommended to be used instead of DSO 8.5 shipped in AS2005 (DSO 8.5 is DSO 8.0 with SP4 fixes and additions to support AS2005 connectivity).
DSO 8.5 is for administering databases who are:
1. migrated from AS2000 to AS2005
and
2. are not edited/maintained with the AS2005 tools or AMO

Because of the changes between AS2000 and AS2005, a total DSO compatibility with AS2005 was not obtained and these are the restrictions:
- DSO 8.5 sees only the databases from the repository (DSO8’s repository)
- DSO 8.5 does not see the databases on the AS2005 server, he only reads the repository and deploys on the AS2005 server when processing an object; in other words, new databases on AS2005 (created with AS2005 tools) are not exposed through DSO 8.5
- DSO 8.5 overwrites (if in conflict) the databases from AS2005; for example if you created a database on AS2005 with DSO 8.5, then you edit it with AS2005 tools, when using DS0 8.5 the database will be overwritten with its version from the DSO repository (the AS2005 tools do not update the DSO repository)
- Because of changes between the AS2000 and AS2005 models, DSO 8.5 has an un-optimal design, certainly not having the AMO’s speed for comparable tasks

Please note that sometimes DSO 8.5 is referred to as DSO9 (since it works with AS2005 aka AS 9.0). I am calling it DSO 8.5 because that's the actual file version.

To setup DSO 8.5 to work with AS2005, you need to:
- have the DSO repository (from AS2000); usually this is the msmdrep.mdb file from "%ProgramFiles%\Microsoft Analysis Services\Bin"
- setup AS2005 to specify connection string to the DSO repository and also the locks folder; to do this, stop the AS2005 server, edit the msmdsrv.ini file (from the AS2005 installation folder), look for the <DSO> xml section:
<DSO>
<RemoteRepositoryConnectionString/>
<RepositoryConnectionString/>
<RemoteLocksDirectory/>
<LocksDirectory/>
</DSO>
- specify values for those properties (to see what they mean, please check books online "ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/uas9/html/75e062bd-7f24-43b0-8b0b-d48437d3a116.htm")
- start the AS2005 server
- connect with DSO 8.5 (for example using Analysis Manager from AS2000); please remember you will see the databases from the repository and not the actual databases from the AS2005 server

Adrian Dumitrascu.

|||What about this errror that I get after connecting to the repository with DSO:

HAIdcom.clsDrillThrough.GetDTColumnNames(): Path not found

|||Hmm - so it seems that using DSO from an application against AS2005 is not a good idea? It sound slike from your description that the use of DSO will overwrite any modifications made directly using SQL Mgmt Studio? Thats not good.
I have been trying to use DSO also in this scenario - where is the RepositoryConnectString supposed to point to - and what provider shpuld be used? The MS documentation gives no hints to this, when I try pointing to the access mdb you suggested I get:
Errors in the OLE DB provider. The data source or location is not valid. Provide a valid server to which to connect.
If I point to the Analysis server database I want to connect to using the new Analysis 9.0 provider I get:
Query (1, 10) Parser: The syntax for ',' is incorrect.
I would have thought there would be more people trying to do this and getting similar issues?
Any help just to get back to previous functionality would be greatly appreciated, thanks.
|||Hi All.

The DSO has been replaced by the AMO.
But the problem that arises with this is as follows.
DSO was COM. So, VBA code could use the DSO to access data/metadata of AS2000.
Now, I intend to access the same in VBA/Excel.
Any idea how I could do this, since AMO is not a COM class, and can be used thru .NET.

Essentially, my intention is to document a cube of AS2005 and throw the metadata into Excel sheets.
Thanx in advance.|||Hi,
thank you for the details.
I use the DSO Object for AS2000. Where can i find the DLL for DSO 8.5 ?
I use the Interop.DSO.dll for DSO and AS 2000 and have to set e new reference in the project for DSO 8.5. With the old DSO it is not possible to acces the AS 2005 :-(
Hop somebody can help me
|||

fantasimus wrote:

Hi,
thank you for the details.
I use the DSO Object for AS2000. Where can i find the DLL for DSO 8.5 ?
I use the Interop.DSO.dll for DSO and AS 2000 and have to set e new reference in the project for DSO 8.5. With the old DSO it is not possible to acces the AS 2005 :-(
Hop somebody can help me

Fantasimus, please read the earlier posts.

The AMO is what you should be using to access SSAS (AS2005).

And as I have said earlier, the AMO is a .NET library unlike the DSO which was COM.

However, using Visual Studio 2005 Tools for Office version, one can do VBA like work, since office project templates are available with VSTO.

And then, the programming can be in c# or vb.net

|||

Thanks for all comments.

It seems our work is proved to be correct. As these reasons Adrian refered, we never used DSO any more, neight DSO 8.5. But we made the wrapper for AMO using .NET, and CCW it to make COM visiable. That's saving time to update millions of codes. For balance to our worktime, at some points, we wrapper our business layer functions directly.

Hope our solution and choice will make sense to others who are willing to lift SQL2005, thanks!

|||

Hello,

I am testing the Beta Version of MS Project Server 2007, using Analysis Services 2005 to try to build an OLAP cube. I am consistently getting the following error (see below) and this forum is the only place that I can find any information on it. I'm not a developer, so I'm not sure how (or if) this issue relates to the DSO problem that you all discussed above. Do you have any insight?

=====Process Completed=====
[11/6/2006 2:11 PM] Failed to build the OLAP cubes. Error: Analysis Services
session failed with the following error: Query (1,10) Parser: The syntax for
',' is incorrect.

Thanks,

Brian

|||

Hi Brian,

Did you get a solution for the error "Query (1,10) Parser: The syntax for
',' is incorrect. "?

I'm also getting the same error and clueless of what should be done.

Thanks

Umanga.

Posted By: bciampa on 11-07-2006 8:48 PM UTC

Subject: Re: DSO in SQL2005Message:

Hello,

I am testing the Beta Version of MS Project Server 2007, using Analysis Services 2005 to try to build an OLAP cube. I am consistently getting the following error (see below) and this forum is the only place that I can find any information on it. I'm not a developer, so I'm not sure how (or if) this issue relates to the DSO problem that you all discussed above. Do you have any insight?

=====Process Completed=====
[11/6/2006 2:11 PM] Failed to build the OLAP cubes. Error: Analysis Services
session failed with the following error: Query (1,10) Parser: The syntax for
',' is incorrect.

Thanks,

Brian

|||

Hi guys! Have you got any solution for that error message(Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Query (1, 10) Parser: The syntax for ',' is incorrect.)?

Pls. help if you have one

Thanks

|||

Hi,

I don't have a straight answer for this problem, but let's try to debug it.

You are using DSO version 8.5 to connect to Analysis Services 2005 (after you configured AS2005 to setup the DSO-related server properties, the connection string to the repository and the lock directory).

You are able to connect, to read all the objects (although please remember that you read all the objects from the repository, not from the real AS2005 server).

And you get the error when you try to process an object ? If yes, let's try to see what commands is DSO sending to the AS2005 server before the error.

- start SQL profiler for Analysis Services

- re-run the minimal DSO code that would generate the error

- in profiler you should see the commands that DSO sent to server just before the error

- I assume you will have 2 commands: an Alter statement (for the Database probably, or maybe for a Partition if you process a Partition) followed by a Process statement, the Alter succeeds, but the Process fails; but let's check these assumptions first

Adrian Dumitrascu

|||

Any one has idea how to create roles and permissions for a SSAS cube using VB and then using AMO

I basically want to create the VB script and then want to run it through cmd prompt

please, let me know all the stepsto do all this

thanks

|||

This seems to be unrelated with the DSO in AS2005, there are these other threads about creating roles and permissions:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1795829&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1798355&SiteID=1

DSO in SQL2005

Anybody can share the way to administer AS2005 using DSO?

AMO (Analysis Management Objects) is the object model for administering AS2005 and it's highly recommended to be used instead of DSO 8.5 shipped in AS2005 (DSO 8.5 is DSO 8.0 with SP4 fixes and additions to support AS2005 connectivity).
DSO 8.5 is for administering databases who are:
1. migrated from AS2000 to AS2005
and
2. are not edited/maintained with the AS2005 tools or AMO

Because of the changes between AS2000 and AS2005, a total DSO compatibility with AS2005 was not obtained and these are the restrictions:
- DSO 8.5 sees only the databases from the repository (DSO8’s repository)
- DSO 8.5 does not see the databases on the AS2005 server, he only reads the repository and deploys on the AS2005 server when processing an object; in other words, new databases on AS2005 (created with AS2005 tools) are not exposed through DSO 8.5
- DSO 8.5 overwrites (if in conflict) the databases from AS2005; for example if you created a database on AS2005 with DSO 8.5, then you edit it with AS2005 tools, when using DS0 8.5 the database will be overwritten with its version from the DSO repository (the AS2005 tools do not update the DSO repository)
- Because of changes between the AS2000 and AS2005 models, DSO 8.5 has an un-optimal design, certainly not having the AMO’s speed for comparable tasks

Please note that sometimes DSO 8.5 is referred to as DSO9 (since it works with AS2005 aka AS 9.0). I am calling it DSO 8.5 because that's the actual file version.

To setup DSO 8.5 to work with AS2005, you need to:
- have the DSO repository (from AS2000); usually this is the msmdrep.mdb file from "%ProgramFiles%\Microsoft Analysis Services\Bin"
- setup AS2005 to specify connection string to the DSO repository and also the locks folder; to do this, stop the AS2005 server, edit the msmdsrv.ini file (from the AS2005 installation folder), look for the <DSO> xml section:
<DSO>
<RemoteRepositoryConnectionString/>
<RepositoryConnectionString/>
<RemoteLocksDirectory/>
<LocksDirectory/>
</DSO>
- specify values for those properties (to see what they mean, please check books online "ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/uas9/html/75e062bd-7f24-43b0-8b0b-d48437d3a116.htm")
- start the AS2005 server
- connect with DSO 8.5 (for example using Analysis Manager from AS2000); please remember you will see the databases from the repository and not the actual databases from the AS2005 server

Adrian Dumitrascu.

|||What about this errror that I get after connecting to the repository with DSO:

HAIdcom.clsDrillThrough.GetDTColumnNames(): Path not found

|||Hmm - so it seems that using DSO from an application against AS2005 is not a good idea? It sound slike from your description that the use of DSO will overwrite any modifications made directly using SQL Mgmt Studio? Thats not good.
I have been trying to use DSO also in this scenario - where is the RepositoryConnectString supposed to point to - and what provider shpuld be used? The MS documentation gives no hints to this, when I try pointing to the access mdb you suggested I get:
Errors in the OLE DB provider. The data source or location is not valid. Provide a valid server to which to connect.
If I point to the Analysis server database I want to connect to using the new Analysis 9.0 provider I get:
Query (1, 10) Parser: The syntax for ',' is incorrect.
I would have thought there would be more people trying to do this and getting similar issues?
Any help just to get back to previous functionality would be greatly appreciated, thanks.
|||Hi All.

The DSO has been replaced by the AMO.
But the problem that arises with this is as follows.
DSO was COM. So, VBA code could use the DSO to access data/metadata of AS2000.
Now, I intend to access the same in VBA/Excel.
Any idea how I could do this, since AMO is not a COM class, and can be used thru .NET.

Essentially, my intention is to document a cube of AS2005 and throw the metadata into Excel sheets.
Thanx in advance.|||Hi,

thank you for the details.

I use the DSO Object for AS2000. Where can i find the DLL for DSO 8.5 ?

I use the Interop.DSO.dll for DSO and AS 2000 and have to set e new

reference in the project for DSO 8.5. With the old DSO it is not

possible to acces the AS 2005 :-(

Hop somebody can help me|||

fantasimus wrote:

Hi,
thank you for the details.
I use the DSO Object for AS2000. Where can i find the DLL for DSO 8.5 ?
I use the Interop.DSO.dll for DSO and AS 2000 and have to set e new reference in the project for DSO 8.5. With the old DSO it is not possible to acces the AS 2005 :-(
Hop somebody can help me

Fantasimus, please read the earlier posts.

The AMO is what you should be using to access SSAS (AS2005).

And as I have said earlier, the AMO is a .NET library unlike the DSO which was COM.

However, using Visual Studio 2005 Tools for Office version, one can do VBA like work, since office project templates are available with VSTO.

And then, the programming can be in c# or vb.net

|||

Thanks for all comments.

It seems our work is proved to be correct. As these reasons Adrian refered, we never used DSO any more, neight DSO 8.5. But we made the wrapper for AMO using .NET, and CCW it to make COM visiable. That's saving time to update millions of codes. For balance to our worktime, at some points, we wrapper our business layer functions directly.

Hope our solution and choice will make sense to others who are willing to lift SQL2005, thanks!

|||

Hello,

I am testing the Beta Version of MS Project Server 2007, using Analysis Services 2005 to try to build an OLAP cube. I am consistently getting the following error (see below) and this forum is the only place that I can find any information on it. I'm not a developer, so I'm not sure how (or if) this issue relates to the DSO problem that you all discussed above. Do you have any insight?

=====Process Completed=====
[11/6/2006 2:11 PM] Failed to build the OLAP cubes. Error: Analysis Services
session failed with the following error: Query (1,10) Parser: The syntax for
',' is incorrect.

Thanks,

Brian

|||

Hi Brian,

Did you get a solution for the error "Query (1,10) Parser: The syntax for
',' is incorrect. "?

I'm also getting the same error and clueless of what should be done.

Thanks

Umanga.

Posted By: bciampa on 11-07-2006 8:48 PM UTC

Subject: Re: DSO in SQL2005

Message:

Hello,

I am testing the Beta Version of MS Project Server 2007, using Analysis Services 2005 to try to build an OLAP cube. I am consistently getting the following error (see below) and this forum is the only place that I can find any information on it. I'm not a developer, so I'm not sure how (or if) this issue relates to the DSO problem that you all discussed above. Do you have any insight?

=====Process Completed=====
[11/6/2006 2:11 PM] Failed to build the OLAP cubes. Error: Analysis Services
session failed with the following error: Query (1,10) Parser: The syntax for
',' is incorrect.

Thanks,

Brian

|||

Hi guys! Have you got any solution for that error message(Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Query (1, 10) Parser: The syntax for ',' is incorrect.)?

Pls. help if you have one

Thanks

|||

Hi,

I don't have a straight answer for this problem, but let's try to debug it.

You are using DSO version 8.5 to connect to Analysis Services 2005 (after you configured AS2005 to setup the DSO-related server properties, the connection string to the repository and the lock directory).

You are able to connect, to read all the objects (although please remember that you read all the objects from the repository, not from the real AS2005 server).

And you get the error when you try to process an object ? If yes, let's try to see what commands is DSO sending to the AS2005 server before the error.

- start SQL profiler for Analysis Services

- re-run the minimal DSO code that would generate the error

- in profiler you should see the commands that DSO sent to server just before the error

- I assume you will have 2 commands: an Alter statement (for the Database probably, or maybe for a Partition if you process a Partition) followed by a Process statement, the Alter succeeds, but the Process fails; but let's check these assumptions first

Adrian Dumitrascu

|||

Any one has idea how to create roles and permissions for a SSAS cube using VB and then using AMO

I basically want to create the VB script and then want to run it through cmd prompt

please, let me know all the stepsto do all this

thanks

|||

This seems to be unrelated with the DSO in AS2005, there are these other threads about creating roles and permissions:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1795829&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1798355&SiteID=1

DSO in SQL2005

Anybody can share the way to administer AS2005 using DSO?

AMO (Analysis Management Objects) is the object model for administering AS2005 and it's highly recommended to be used instead of DSO 8.5 shipped in AS2005 (DSO 8.5 is DSO 8.0 with SP4 fixes and additions to support AS2005 connectivity).
DSO 8.5 is for administering databases who are:
1. migrated from AS2000 to AS2005
and
2. are not edited/maintained with the AS2005 tools or AMO

Because of the changes between AS2000 and AS2005, a total DSO compatibility with AS2005 was not obtained and these are the restrictions:
- DSO 8.5 sees only the databases from the repository (DSO8’s repository)
- DSO 8.5 does not see the databases on the AS2005 server, he only reads the repository and deploys on the AS2005 server when processing an object; in other words, new databases on AS2005 (created with AS2005 tools) are not exposed through DSO 8.5
- DSO 8.5 overwrites (if in conflict) the databases from AS2005; for example if you created a database on AS2005 with DSO 8.5, then you edit it with AS2005 tools, when using DS0 8.5 the database will be overwritten with its version from the DSO repository (the AS2005 tools do not update the DSO repository)
- Because of changes between the AS2000 and AS2005 models, DSO 8.5 has an un-optimal design, certainly not having the AMO’s speed for comparable tasks

Please note that sometimes DSO 8.5 is referred to as DSO9 (since it works with AS2005 aka AS 9.0). I am calling it DSO 8.5 because that's the actual file version.

To setup DSO 8.5 to work with AS2005, you need to:
- have the DSO repository (from AS2000); usually this is the msmdrep.mdb file from "%ProgramFiles%\Microsoft Analysis Services\Bin"
- setup AS2005 to specify connection string to the DSO repository and also the locks folder; to do this, stop the AS2005 server, edit the msmdsrv.ini file (from the AS2005 installation folder), look for the <DSO> xml section:
<DSO>
<RemoteRepositoryConnectionString/>
<RepositoryConnectionString/>
<RemoteLocksDirectory/>
<LocksDirectory/>
</DSO>
- specify values for those properties (to see what they mean, please check books online "ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/uas9/html/75e062bd-7f24-43b0-8b0b-d48437d3a116.htm")
- start the AS2005 server
- connect with DSO 8.5 (for example using Analysis Manager from AS2000); please remember you will see the databases from the repository and not the actual databases from the AS2005 server

Adrian Dumitrascu.

|||What about this errror that I get after connecting to the repository with DSO:

HAIdcom.clsDrillThrough.GetDTColumnNames(): Path not found

|||Hmm - so it seems that using DSO from an application against AS2005 is not a good idea? It sound slike from your description that the use of DSO will overwrite any modifications made directly using SQL Mgmt Studio? Thats not good.
I have been trying to use DSO also in this scenario - where is the RepositoryConnectString supposed to point to - and what provider shpuld be used? The MS documentation gives no hints to this, when I try pointing to the access mdb you suggested I get:
Errors in the OLE DB provider. The data source or location is not valid. Provide a valid server to which to connect.
If I point to the Analysis server database I want to connect to using the new Analysis 9.0 provider I get:
Query (1, 10) Parser: The syntax for ',' is incorrect.
I would have thought there would be more people trying to do this and getting similar issues?
Any help just to get back to previous functionality would be greatly appreciated, thanks.
|||Hi All.

The DSO has been replaced by the AMO.
But the problem that arises with this is as follows.
DSO was COM. So, VBA code could use the DSO to access data/metadata of AS2000.
Now, I intend to access the same in VBA/Excel.
Any idea how I could do this, since AMO is not a COM class, and can be used thru .NET.

Essentially, my intention is to document a cube of AS2005 and throw the metadata into Excel sheets.
Thanx in advance.|||Hi,
thank you for the details.
I use the DSO Object for AS2000. Where can i find the DLL for DSO 8.5 ?
I use the Interop.DSO.dll for DSO and AS 2000 and have to set e new reference in the project for DSO 8.5. With the old DSO it is not possible to acces the AS 2005 :-(
Hop somebody can help me
|||

fantasimus wrote:

Hi,
thank you for the details.
I use the DSO Object for AS2000. Where can i find the DLL for DSO 8.5 ?
I use the Interop.DSO.dll for DSO and AS 2000 and have to set e new reference in the project for DSO 8.5. With the old DSO it is not possible to acces the AS 2005 :-(
Hop somebody can help me

Fantasimus, please read the earlier posts.

The AMO is what you should be using to access SSAS (AS2005).

And as I have said earlier, the AMO is a .NET library unlike the DSO which was COM.

However, using Visual Studio 2005 Tools for Office version, one can do VBA like work, since office project templates are available with VSTO.

And then, the programming can be in c# or vb.net

|||

Thanks for all comments.

It seems our work is proved to be correct. As these reasons Adrian refered, we never used DSO any more, neight DSO 8.5. But we made the wrapper for AMO using .NET, and CCW it to make COM visiable. That's saving time to update millions of codes. For balance to our worktime, at some points, we wrapper our business layer functions directly.

Hope our solution and choice will make sense to others who are willing to lift SQL2005, thanks!

|||

Hello,

I am testing the Beta Version of MS Project Server 2007, using Analysis Services 2005 to try to build an OLAP cube. I am consistently getting the following error (see below) and this forum is the only place that I can find any information on it. I'm not a developer, so I'm not sure how (or if) this issue relates to the DSO problem that you all discussed above. Do you have any insight?

=====Process Completed=====
[11/6/2006 2:11 PM] Failed to build the OLAP cubes. Error: Analysis Services
session failed with the following error: Query (1,10) Parser: The syntax for
',' is incorrect.

Thanks,

Brian

|||

Hi Brian,

Did you get a solution for the error "Query (1,10) Parser: The syntax for
',' is incorrect. "?

I'm also getting the same error and clueless of what should be done.

Thanks

Umanga.

Posted By: bciampa on 11-07-2006 8:48 PM UTC

Subject: Re: DSO in SQL2005 Message:

Hello,

I am testing the Beta Version of MS Project Server 2007, using Analysis Services 2005 to try to build an OLAP cube. I am consistently getting the following error (see below) and this forum is the only place that I can find any information on it. I'm not a developer, so I'm not sure how (or if) this issue relates to the DSO problem that you all discussed above. Do you have any insight?

=====Process Completed=====
[11/6/2006 2:11 PM] Failed to build the OLAP cubes. Error: Analysis Services
session failed with the following error: Query (1,10) Parser: The syntax for
',' is incorrect.

Thanks,

Brian

|||

Hi guys! Have you got any solution for that error message(Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Query (1, 10) Parser: The syntax for ',' is incorrect.)?

Pls. help if you have one

Thanks

|||

Hi,

I don't have a straight answer for this problem, but let's try to debug it.

You are using DSO version 8.5 to connect to Analysis Services 2005 (after you configured AS2005 to setup the DSO-related server properties, the connection string to the repository and the lock directory).

You are able to connect, to read all the objects (although please remember that you read all the objects from the repository, not from the real AS2005 server).

And you get the error when you try to process an object ? If yes, let's try to see what commands is DSO sending to the AS2005 server before the error.

- start SQL profiler for Analysis Services

- re-run the minimal DSO code that would generate the error

- in profiler you should see the commands that DSO sent to server just before the error

- I assume you will have 2 commands: an Alter statement (for the Database probably, or maybe for a Partition if you process a Partition) followed by a Process statement, the Alter succeeds, but the Process fails; but let's check these assumptions first

Adrian Dumitrascu

|||

Any one has idea how to create roles and permissions for a SSAS cube using VB and then using AMO

I basically want to create the VB script and then want to run it through cmd prompt

please, let me know all the stepsto do all this

thanks

|||

This seems to be unrelated with the DSO in AS2005, there are these other threads about creating roles and permissions:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1795829&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1798355&SiteID=1

DSO in SQL2005

Anybody can share the way to administer AS2005 using DSO?

AMO (Analysis Management Objects) is the object model for administering AS2005 and it's highly recommended to be used instead of DSO 8.5 shipped in AS2005 (DSO 8.5 is DSO 8.0 with SP4 fixes and additions to support AS2005 connectivity).
DSO 8.5 is for administering databases who are:
1. migrated from AS2000 to AS2005
and
2. are not edited/maintained with the AS2005 tools or AMO

Because of the changes between AS2000 and AS2005, a total DSO compatibility with AS2005 was not obtained and these are the restrictions:
- DSO 8.5 sees only the databases from the repository (DSO8’s repository)
- DSO 8.5 does not see the databases on the AS2005 server, he only reads the repository and deploys on the AS2005 server when processing an object; in other words, new databases on AS2005 (created with AS2005 tools) are not exposed through DSO 8.5
- DSO 8.5 overwrites (if in conflict) the databases from AS2005; for example if you created a database on AS2005 with DSO 8.5, then you edit it with AS2005 tools, when using DS0 8.5 the database will be overwritten with its version from the DSO repository (the AS2005 tools do not update the DSO repository)
- Because of changes between the AS2000 and AS2005 models, DSO 8.5 has an un-optimal design, certainly not having the AMO’s speed for comparable tasks

Please note that sometimes DSO 8.5 is referred to as DSO9 (since it works with AS2005 aka AS 9.0). I am calling it DSO 8.5 because that's the actual file version.

To setup DSO 8.5 to work with AS2005, you need to:
- have the DSO repository (from AS2000); usually this is the msmdrep.mdb file from "%ProgramFiles%\Microsoft Analysis Services\Bin"
- setup AS2005 to specify connection string to the DSO repository and also the locks folder; to do this, stop the AS2005 server, edit the msmdsrv.ini file (from the AS2005 installation folder), look for the <DSO> xml section:
<DSO>
<RemoteRepositoryConnectionString/>
<RepositoryConnectionString/>
<RemoteLocksDirectory/>
<LocksDirectory/>
</DSO>
- specify values for those properties (to see what they mean, please check books online "ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/uas9/html/75e062bd-7f24-43b0-8b0b-d48437d3a116.htm")
- start the AS2005 server
- connect with DSO 8.5 (for example using Analysis Manager from AS2000); please remember you will see the databases from the repository and not the actual databases from the AS2005 server

Adrian Dumitrascu.

|||What about this errror that I get after connecting to the repository with DSO:

HAIdcom.clsDrillThrough.GetDTColumnNames(): Path not found

|||Hmm - so it seems that using DSO from an application against AS2005 is not a good idea? It sound slike from your description that the use of DSO will overwrite any modifications made directly using SQL Mgmt Studio? Thats not good.
I have been trying to use DSO also in this scenario - where is the RepositoryConnectString supposed to point to - and what provider shpuld be used? The MS documentation gives no hints to this, when I try pointing to the access mdb you suggested I get:
Errors in the OLE DB provider. The data source or location is not valid. Provide a valid server to which to connect.
If I point to the Analysis server database I want to connect to using the new Analysis 9.0 provider I get:
Query (1, 10) Parser: The syntax for ',' is incorrect.
I would have thought there would be more people trying to do this and getting similar issues?
Any help just to get back to previous functionality would be greatly appreciated, thanks.
|||Hi All.

The DSO has been replaced by the AMO.
But the problem that arises with this is as follows.
DSO was COM. So, VBA code could use the DSO to access data/metadata of AS2000.
Now, I intend to access the same in VBA/Excel.
Any idea how I could do this, since AMO is not a COM class, and can be used thru .NET.

Essentially, my intention is to document a cube of AS2005 and throw the metadata into Excel sheets.
Thanx in advance.|||Hi,

thank you for the details.

I use the DSO Object for AS2000. Where can i find the DLL for DSO 8.5 ?

I use the Interop.DSO.dll for DSO and AS 2000 and have to set e new

reference in the project for DSO 8.5. With the old DSO it is not

possible to acces the AS 2005 :-(

Hop somebody can help me|||

fantasimus wrote:

Hi,
thank you for the details.
I use the DSO Object for AS2000. Where can i find the DLL for DSO 8.5 ?
I use the Interop.DSO.dll for DSO and AS 2000 and have to set e new reference in the project for DSO 8.5. With the old DSO it is not possible to acces the AS 2005 :-(
Hop somebody can help me

Fantasimus, please read the earlier posts.

The AMO is what you should be using to access SSAS (AS2005).

And as I have said earlier, the AMO is a .NET library unlike the DSO which was COM.

However, using Visual Studio 2005 Tools for Office version, one can do VBA like work, since office project templates are available with VSTO.

And then, the programming can be in c# or vb.net

|||

Thanks for all comments.

It seems our work is proved to be correct. As these reasons Adrian refered, we never used DSO any more, neight DSO 8.5. But we made the wrapper for AMO using .NET, and CCW it to make COM visiable. That's saving time to update millions of codes. For balance to our worktime, at some points, we wrapper our business layer functions directly.

Hope our solution and choice will make sense to others who are willing to lift SQL2005, thanks!

|||

Hello,

I am testing the Beta Version of MS Project Server 2007, using Analysis Services 2005 to try to build an OLAP cube. I am consistently getting the following error (see below) and this forum is the only place that I can find any information on it. I'm not a developer, so I'm not sure how (or if) this issue relates to the DSO problem that you all discussed above. Do you have any insight?

=====Process Completed=====
[11/6/2006 2:11 PM] Failed to build the OLAP cubes. Error: Analysis Services
session failed with the following error: Query (1,10) Parser: The syntax for
',' is incorrect.

Thanks,

Brian

|||

Hi Brian,

Did you get a solution for the error "Query (1,10) Parser: The syntax for
',' is incorrect. "?

I'm also getting the same error and clueless of what should be done.

Thanks

Umanga.

Posted By: bciampa on 11-07-2006 8:48 PM UTC

Subject: Re: DSO in SQL2005

Message:

Hello,

I am testing the Beta Version of MS Project Server 2007, using Analysis Services 2005 to try to build an OLAP cube. I am consistently getting the following error (see below) and this forum is the only place that I can find any information on it. I'm not a developer, so I'm not sure how (or if) this issue relates to the DSO problem that you all discussed above. Do you have any insight?

=====Process Completed=====
[11/6/2006 2:11 PM] Failed to build the OLAP cubes. Error: Analysis Services
session failed with the following error: Query (1,10) Parser: The syntax for
',' is incorrect.

Thanks,

Brian

|||

Hi guys! Have you got any solution for that error message(Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Query (1, 10) Parser: The syntax for ',' is incorrect.)?

Pls. help if you have one

Thanks

|||

Hi,

I don't have a straight answer for this problem, but let's try to debug it.

You are using DSO version 8.5 to connect to Analysis Services 2005 (after you configured AS2005 to setup the DSO-related server properties, the connection string to the repository and the lock directory).

You are able to connect, to read all the objects (although please remember that you read all the objects from the repository, not from the real AS2005 server).

And you get the error when you try to process an object ? If yes, let's try to see what commands is DSO sending to the AS2005 server before the error.

- start SQL profiler for Analysis Services

- re-run the minimal DSO code that would generate the error

- in profiler you should see the commands that DSO sent to server just before the error

- I assume you will have 2 commands: an Alter statement (for the Database probably, or maybe for a Partition if you process a Partition) followed by a Process statement, the Alter succeeds, but the Process fails; but let's check these assumptions first

Adrian Dumitrascu

|||

Any one has idea how to create roles and permissions for a SSAS cube using VB and then using AMO

I basically want to create the VB script and then want to run it through cmd prompt

please, let me know all the stepsto do all this

thanks

|||

This seems to be unrelated with the DSO in AS2005, there are these other threads about creating roles and permissions:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1795829&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1798355&SiteID=1

DSO in SQL2005

Anybody can share the way to administer AS2005 using DSO?

AMO (Analysis Management Objects) is the object model for administering AS2005 and it's highly recommended to be used instead of DSO 8.5 shipped in AS2005 (DSO 8.5 is DSO 8.0 with SP4 fixes and additions to support AS2005 connectivity).
DSO 8.5 is for administering databases who are:
1. migrated from AS2000 to AS2005
and
2. are not edited/maintained with the AS2005 tools or AMO

Because of the changes between AS2000 and AS2005, a total DSO compatibility with AS2005 was not obtained and these are the restrictions:
- DSO 8.5 sees only the databases from the repository (DSO8’s repository)
- DSO 8.5 does not see the databases on the AS2005 server, he only reads the repository and deploys on the AS2005 server when processing an object; in other words, new databases on AS2005 (created with AS2005 tools) are not exposed through DSO 8.5
- DSO 8.5 overwrites (if in conflict) the databases from AS2005; for example if you created a database on AS2005 with DSO 8.5, then you edit it with AS2005 tools, when using DS0 8.5 the database will be overwritten with its version from the DSO repository (the AS2005 tools do not update the DSO repository)
- Because of changes between the AS2000 and AS2005 models, DSO 8.5 has an un-optimal design, certainly not having the AMO’s speed for comparable tasks

Please note that sometimes DSO 8.5 is referred to as DSO9 (since it works with AS2005 aka AS 9.0). I am calling it DSO 8.5 because that's the actual file version.

To setup DSO 8.5 to work with AS2005, you need to:
- have the DSO repository (from AS2000); usually this is the msmdrep.mdb file from "%ProgramFiles%\Microsoft Analysis Services\Bin"
- setup AS2005 to specify connection string to the DSO repository and also the locks folder; to do this, stop the AS2005 server, edit the msmdsrv.ini file (from the AS2005 installation folder), look for the <DSO> xml section:
<DSO>
<RemoteRepositoryConnectionString/>
<RepositoryConnectionString/>
<RemoteLocksDirectory/>
<LocksDirectory/>
</DSO>
- specify values for those properties (to see what they mean, please check books online "ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/uas9/html/75e062bd-7f24-43b0-8b0b-d48437d3a116.htm")
- start the AS2005 server
- connect with DSO 8.5 (for example using Analysis Manager from AS2000); please remember you will see the databases from the repository and not the actual databases from the AS2005 server

Adrian Dumitrascu.

|||What about this errror that I get after connecting to the repository with DSO:

HAIdcom.clsDrillThrough.GetDTColumnNames(): Path not found

|||Hmm - so it seems that using DSO from an application against AS2005 is not a good idea? It sound slike from your description that the use of DSO will overwrite any modifications made directly using SQL Mgmt Studio? Thats not good.
I have been trying to use DSO also in this scenario - where is the RepositoryConnectString supposed to point to - and what provider shpuld be used? The MS documentation gives no hints to this, when I try pointing to the access mdb you suggested I get:
Errors in the OLE DB provider. The data source or location is not valid. Provide a valid server to which to connect.
If I point to the Analysis server database I want to connect to using the new Analysis 9.0 provider I get:
Query (1, 10) Parser: The syntax for ',' is incorrect.
I would have thought there would be more people trying to do this and getting similar issues?
Any help just to get back to previous functionality would be greatly appreciated, thanks.
|||Hi All.

The DSO has been replaced by the AMO.
But the problem that arises with this is as follows.
DSO was COM. So, VBA code could use the DSO to access data/metadata of AS2000.
Now, I intend to access the same in VBA/Excel.
Any idea how I could do this, since AMO is not a COM class, and can be used thru .NET.

Essentially, my intention is to document a cube of AS2005 and throw the metadata into Excel sheets.
Thanx in advance.|||Hi,
thank you for the details.
I use the DSO Object for AS2000. Where can i find the DLL for DSO 8.5 ?
I use the Interop.DSO.dll for DSO and AS 2000 and have to set e new reference in the project for DSO 8.5. With the old DSO it is not possible to acces the AS 2005 :-(
Hop somebody can help me
|||

fantasimus wrote:

Hi,
thank you for the details.
I use the DSO Object for AS2000. Where can i find the DLL for DSO 8.5 ?
I use the Interop.DSO.dll for DSO and AS 2000 and have to set e new reference in the project for DSO 8.5. With the old DSO it is not possible to acces the AS 2005 :-(
Hop somebody can help me

Fantasimus, please read the earlier posts.

The AMO is what you should be using to access SSAS (AS2005).

And as I have said earlier, the AMO is a .NET library unlike the DSO which was COM.

However, using Visual Studio 2005 Tools for Office version, one can do VBA like work, since office project templates are available with VSTO.

And then, the programming can be in c# or vb.net

|||

Thanks for all comments.

It seems our work is proved to be correct. As these reasons Adrian refered, we never used DSO any more, neight DSO 8.5. But we made the wrapper for AMO using .NET, and CCW it to make COM visiable. That's saving time to update millions of codes. For balance to our worktime, at some points, we wrapper our business layer functions directly.

Hope our solution and choice will make sense to others who are willing to lift SQL2005, thanks!

|||

Hello,

I am testing the Beta Version of MS Project Server 2007, using Analysis Services 2005 to try to build an OLAP cube. I am consistently getting the following error (see below) and this forum is the only place that I can find any information on it. I'm not a developer, so I'm not sure how (or if) this issue relates to the DSO problem that you all discussed above. Do you have any insight?

=====Process Completed=====
[11/6/2006 2:11 PM] Failed to build the OLAP cubes. Error: Analysis Services
session failed with the following error: Query (1,10) Parser: The syntax for
',' is incorrect.

Thanks,

Brian

|||

Hi Brian,

Did you get a solution for the error "Query (1,10) Parser: The syntax for
',' is incorrect. "?

I'm also getting the same error and clueless of what should be done.

Thanks

Umanga.

Posted By: bciampa on 11-07-2006 8:48 PM UTC

Subject: Re: DSO in SQL2005 Message:

Hello,

I am testing the Beta Version of MS Project Server 2007, using Analysis Services 2005 to try to build an OLAP cube. I am consistently getting the following error (see below) and this forum is the only place that I can find any information on it. I'm not a developer, so I'm not sure how (or if) this issue relates to the DSO problem that you all discussed above. Do you have any insight?

=====Process Completed=====
[11/6/2006 2:11 PM] Failed to build the OLAP cubes. Error: Analysis Services
session failed with the following error: Query (1,10) Parser: The syntax for
',' is incorrect.

Thanks,

Brian

|||

Hi guys! Have you got any solution for that error message(Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Query (1, 10) Parser: The syntax for ',' is incorrect.)?

Pls. help if you have one

Thanks

|||

Hi,

I don't have a straight answer for this problem, but let's try to debug it.

You are using DSO version 8.5 to connect to Analysis Services 2005 (after you configured AS2005 to setup the DSO-related server properties, the connection string to the repository and the lock directory).

You are able to connect, to read all the objects (although please remember that you read all the objects from the repository, not from the real AS2005 server).

And you get the error when you try to process an object ? If yes, let's try to see what commands is DSO sending to the AS2005 server before the error.

- start SQL profiler for Analysis Services

- re-run the minimal DSO code that would generate the error

- in profiler you should see the commands that DSO sent to server just before the error

- I assume you will have 2 commands: an Alter statement (for the Database probably, or maybe for a Partition if you process a Partition) followed by a Process statement, the Alter succeeds, but the Process fails; but let's check these assumptions first

Adrian Dumitrascu

|||

Any one has idea how to create roles and permissions for a SSAS cube using VB and then using AMO

I basically want to create the VB script and then want to run it through cmd prompt

please, let me know all the stepsto do all this

thanks

|||

This seems to be unrelated with the DSO in AS2005, there are these other threads about creating roles and permissions:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1795829&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1798355&SiteID=1