Can't export report to CSV,XMl correctly, sql 2005 reporting service

Hi all,

I am developing reports using sql2005 report service. I can export reports in excel and pdf format, but can't export to csv and xml correctly.

The exported csv and xml files only contain some thing like the textbox,..., but no report content are there.

Anybody can help? thanks in advance.

BTW, all reports are matrix, is martrix can cause some issues?

Hi,

For most items on your report, you can define how it needs to be rendered to XML. For example the xml output for an item in a matrix can be set as follow:

select the item in the matrix|||

Thanks, Greert.

Your reply is really helpful. Now I know how to export report in xml format. But, how about CSV? I still can't export report to csv.

Thanks again

|||

Hi,

The same goes for CSV. For example if you set the Output of a column to No, you will see that the column is not included in the CSV file.

Greetz,

Geert

Geert Verhoeven
Consultant @. Ausy Belgium

My Personal Blog

|||Hi Geert,

Thanks a lot.

When I set th output of a column to yes, it works. Before, the the output of column was set to Auto.

Can't create a backup job in SQL2005

I'm trying to create a simple backup job using the maintenance wizard in SQL
2005 and get the error below, anyone know what I'm doing wrong? (of course
the "For help click" link goes nowhere as usual)
Thanks
Maintenance Plan Wizard Progress
- Creating maintenance plan "MaintenancePlan" (Error)
Messages
Create maintenance plan failed.
ADDITIONAL INFORMATION:
Create failed for JobStep 'Subplan'.
(Microsoft.SqlServer.MaintenancePlanTasks)
For help, click:
http://go.microsoft.com/fwlink?Prod...ep&LinkId=20476
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The specified '@.subsystem' is invalid (valid values are returned by
sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
For help, click:
http://go.microsoft.com/fwlink?Prod...34&LinkId=20476
- Adding tasks to the maintenance plan (Stopped)
- Adding scheduling options (Stopped)
- Adding reporting options (Stopped)
- Saving maintenance plan "MaintenancePlan" (Stopped)Make sure both SQL Agent and SSIS services are running.
Andrew J. Kelly SQL MVP
"Peter Lawton" <devnull@.fakedomain.com> wrote in message
news:u%23%23KJOZBGHA.3984@.TK2MSFTNGP14.phx.gbl...
> I'm trying to create a simple backup job using the maintenance wizard in
> SQL 2005 and get the error below, anyone know what I'm doing wrong? (of
> course the "For help click" link goes nowhere as usual)
> Thanks
> Maintenance Plan Wizard Progress
> - Creating maintenance plan "MaintenancePlan" (Error)
> Messages
> Create maintenance plan failed.
> --
> ADDITIONAL INFORMATION:
> Create failed for JobStep 'Subplan'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...ep&LinkId=20476
> --
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...34&LinkId=20476
> - Adding tasks to the maintenance plan (Stopped)
> - Adding scheduling options (Stopped)
> - Adding reporting options (Stopped)
> - Saving maintenance plan "MaintenancePlan" (Stopped)
>|||Very weird, everything looked OK, but I completely un-installed SQL2005 and
re-installed it and everything works now, no differences in the two installs
that I know of.
Anyway, problem fixed now - thanks for the help
Peter Lawton
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eJKecXZBGHA.3396@.tk2msftngp13.phx.gbl...
> Make sure both SQL Agent and SSIS services are running.
> --
> Andrew J. Kelly SQL MVP
>
> "Peter Lawton" <devnull@.fakedomain.com> wrote in message
> news:u%23%23KJOZBGHA.3984@.TK2MSFTNGP14.phx.gbl...
>|||I spoke too soon, I'm getting exactly the same issue on a second server I've
just upgraded from SQL 2000 to SQL 2005
If I try to create a new maintenance job or migrate any of the legace
maintenace jobs it fails with the error:-
The specified '@.subsystem' is invalid (valid values are returned by
sp_enum_sqlagent_subsystems). (.Net SqlClient Data Provider)
Error Number: 14234
Severity: 16
State: 1
Procedure: sp_verify_subsystem
Line Number: 21
"Peter Lawton" <devnull@.fakedomain.com> wrote in message
news:%23MAERcaBGHA.216@.TK2MSFTNGP15.phx.gbl...
> Very weird, everything looked OK, but I completely un-installed SQL2005
> and re-installed it and everything works now, no differences in the two
> installs that I know of.
> Anyway, problem fixed now - thanks for the help
> Peter Lawton
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eJKecXZBGHA.3396@.tk2msftngp13.phx.gbl...
>|||OK, I've found the problem
Maintenance plans need "SQL Integration Services" installed to work.
Peter Lawton
"Peter Lawton" <devnull@.dummydomain.com> wrote in message
news:%23b2pOPiBGHA.3840@.TK2MSFTNGP15.phx.gbl...
>I spoke too soon, I'm getting exactly the same issue on a second server
>I've just upgraded from SQL 2000 to SQL 2005
> If I try to create a new maintenance job or migrate any of the legace
> maintenace jobs it fails with the error:-
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum_sqlagent_subsystems). (.Net SqlClient Data Provider)
> Error Number: 14234
> Severity: 16
> State: 1
> Procedure: sp_verify_subsystem
> Line Number: 21
>
> "Peter Lawton" <devnull@.fakedomain.com> wrote in message
> news:%23MAERcaBGHA.216@.TK2MSFTNGP15.phx.gbl...
>|||Yes as I stated SQL Server Integration Services or "SSIS" for short must be
running. But by learning the hard way you won't have that problem again<g>.
Andrew J. Kelly SQL MVP
"Peter Lawton" <devnull@.dummydomain.com> wrote in message
news:uc2mfciBGHA.628@.TK2MSFTNGP14.phx.gbl...
> OK, I've found the problem
> Maintenance plans need "SQL Integration Services" installed to work.
> Peter Lawton
> "Peter Lawton" <devnull@.dummydomain.com> wrote in message
> news:%23b2pOPiBGHA.3840@.TK2MSFTNGP15.phx.gbl...
>|||Yes, you're very right
I expect it's a mistake a lot of people will make though as it's not at all
obvious why an optional component is needed for basic tasks, and the error
message isn't at all helpful.
Peter Lawton
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OuI9JcjBGHA.4076@.TK2MSFTNGP14.phx.gbl...
> Yes as I stated SQL Server Integration Services or "SSIS" for short must
> be running. But by learning the hard way you won't have that problem
> again<g>.
> --
> Andrew J. Kelly SQL MVP
>
> "Peter Lawton" <devnull@.dummydomain.com> wrote in message
> news:uc2mfciBGHA.628@.TK2MSFTNGP14.phx.gbl...
>

Can't create a backup job in SQL2005

I'm trying to create a simple backup job using the maintenance wizard in SQL
2005 and get the error below, anyone know what I'm doing wrong? (of course
the "For help click" link goes nowhere as usual)
Thanks
Maintenance Plan Wizard Progress
- Creating maintenance plan "MaintenancePlan" (Error)
Messages
Create maintenance plan failed.
ADDITIONAL INFORMATION:
Create failed for JobStep 'Subplan'.
(Microsoft.SqlServer.MaintenancePlanTasks)
For help, click:
http://go.microsoft.com/fwlink?ProdN...p&LinkId=20476
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The specified '@.subsystem' is invalid (valid values are returned by
sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
For help, click:
http://go.microsoft.com/fwlink?ProdN...4&LinkId=20476
- Adding tasks to the maintenance plan (Stopped)
- Adding scheduling options (Stopped)
- Adding reporting options (Stopped)
- Saving maintenance plan "MaintenancePlan" (Stopped)
Make sure both SQL Agent and SSIS services are running.
Andrew J. Kelly SQL MVP
"Peter Lawton" <devnull@.fakedomain.com> wrote in message
news:u%23%23KJOZBGHA.3984@.TK2MSFTNGP14.phx.gbl...
> I'm trying to create a simple backup job using the maintenance wizard in
> SQL 2005 and get the error below, anyone know what I'm doing wrong? (of
> course the "For help click" link goes nowhere as usual)
> Thanks
> Maintenance Plan Wizard Progress
> - Creating maintenance plan "MaintenancePlan" (Error)
> Messages
> Create maintenance plan failed.
> --
> ADDITIONAL INFORMATION:
> Create failed for JobStep 'Subplan'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> For help, click:
> http://go.microsoft.com/fwlink?ProdN...p&LinkId=20476
> --
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
> For help, click:
> http://go.microsoft.com/fwlink?ProdN...4&LinkId=20476
> - Adding tasks to the maintenance plan (Stopped)
> - Adding scheduling options (Stopped)
> - Adding reporting options (Stopped)
> - Saving maintenance plan "MaintenancePlan" (Stopped)
>
|||Very weird, everything looked OK, but I completely un-installed SQL2005 and
re-installed it and everything works now, no differences in the two installs
that I know of.
Anyway, problem fixed now - thanks for the help
Peter Lawton
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eJKecXZBGHA.3396@.tk2msftngp13.phx.gbl...
> Make sure both SQL Agent and SSIS services are running.
> --
> Andrew J. Kelly SQL MVP
>
> "Peter Lawton" <devnull@.fakedomain.com> wrote in message
> news:u%23%23KJOZBGHA.3984@.TK2MSFTNGP14.phx.gbl...
>
|||I spoke too soon, I'm getting exactly the same issue on a second server I've
just upgraded from SQL 2000 to SQL 2005
If I try to create a new maintenance job or migrate any of the legace
maintenace jobs it fails with the error:-
The specified '@.subsystem' is invalid (valid values are returned by
sp_enum_sqlagent_subsystems). (.Net SqlClient Data Provider)
Error Number: 14234
Severity: 16
State: 1
Procedure: sp_verify_subsystem
Line Number: 21
"Peter Lawton" <devnull@.fakedomain.com> wrote in message
news:%23MAERcaBGHA.216@.TK2MSFTNGP15.phx.gbl...
> Very weird, everything looked OK, but I completely un-installed SQL2005
> and re-installed it and everything works now, no differences in the two
> installs that I know of.
> Anyway, problem fixed now - thanks for the help
> Peter Lawton
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eJKecXZBGHA.3396@.tk2msftngp13.phx.gbl...
>
|||OK, I've found the problem
Maintenance plans need "SQL Integration Services" installed to work.
Peter Lawton
"Peter Lawton" <devnull@.dummydomain.com> wrote in message
news:%23b2pOPiBGHA.3840@.TK2MSFTNGP15.phx.gbl...
>I spoke too soon, I'm getting exactly the same issue on a second server
>I've just upgraded from SQL 2000 to SQL 2005
> If I try to create a new maintenance job or migrate any of the legace
> maintenace jobs it fails with the error:-
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum_sqlagent_subsystems). (.Net SqlClient Data Provider)
> Error Number: 14234
> Severity: 16
> State: 1
> Procedure: sp_verify_subsystem
> Line Number: 21
>
> "Peter Lawton" <devnull@.fakedomain.com> wrote in message
> news:%23MAERcaBGHA.216@.TK2MSFTNGP15.phx.gbl...
>
|||Yes as I stated SQL Server Integration Services or "SSIS" for short must be
running. But by learning the hard way you won't have that problem again<g>.
Andrew J. Kelly SQL MVP
"Peter Lawton" <devnull@.dummydomain.com> wrote in message
news:uc2mfciBGHA.628@.TK2MSFTNGP14.phx.gbl...
> OK, I've found the problem
> Maintenance plans need "SQL Integration Services" installed to work.
> Peter Lawton
> "Peter Lawton" <devnull@.dummydomain.com> wrote in message
> news:%23b2pOPiBGHA.3840@.TK2MSFTNGP15.phx.gbl...
>
|||Yes, you're very right
I expect it's a mistake a lot of people will make though as it's not at all
obvious why an optional component is needed for basic tasks, and the error
message isn't at all helpful.
Peter Lawton
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OuI9JcjBGHA.4076@.TK2MSFTNGP14.phx.gbl...
> Yes as I stated SQL Server Integration Services or "SSIS" for short must
> be running. But by learning the hard way you won't have that problem
> again<g>.
> --
> Andrew J. Kelly SQL MVP
>
> "Peter Lawton" <devnull@.dummydomain.com> wrote in message
> news:uc2mfciBGHA.628@.TK2MSFTNGP14.phx.gbl...
>

Can't create a backup job in SQL2005

I'm trying to create a simple backup job using the maintenance wizard in SQL
2005 and get the error below, anyone know what I'm doing wrong? (of course
the "For help click" link goes nowhere as usual)
Thanks
Maintenance Plan Wizard Progress
- Creating maintenance plan "MaintenancePlan" (Error)
Messages
Create maintenance plan failed.
--
ADDITIONAL INFORMATION:
Create failed for JobStep 'Subplan'.
(Microsoft.SqlServer.MaintenancePlanTasks)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+JobStep&LinkId=20476
--
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
The specified '@.subsystem' is invalid (valid values are returned by
sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=14234&LinkId=20476
- Adding tasks to the maintenance plan (Stopped)
- Adding scheduling options (Stopped)
- Adding reporting options (Stopped)
- Saving maintenance plan "MaintenancePlan" (Stopped)Make sure both SQL Agent and SSIS services are running.
--
Andrew J. Kelly SQL MVP
"Peter Lawton" <devnull@.fakedomain.com> wrote in message
news:u%23%23KJOZBGHA.3984@.TK2MSFTNGP14.phx.gbl...
> I'm trying to create a simple backup job using the maintenance wizard in
> SQL 2005 and get the error below, anyone know what I'm doing wrong? (of
> course the "For help click" link goes nowhere as usual)
> Thanks
> Maintenance Plan Wizard Progress
> - Creating maintenance plan "MaintenancePlan" (Error)
> Messages
> Create maintenance plan failed.
> --
> ADDITIONAL INFORMATION:
> Create failed for JobStep 'Subplan'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+JobStep&LinkId=20476
> --
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=14234&LinkId=20476
> - Adding tasks to the maintenance plan (Stopped)
> - Adding scheduling options (Stopped)
> - Adding reporting options (Stopped)
> - Saving maintenance plan "MaintenancePlan" (Stopped)
>|||Very weird, everything looked OK, but I completely un-installed SQL2005 and
re-installed it and everything works now, no differences in the two installs
that I know of.
Anyway, problem fixed now - thanks for the help
Peter Lawton
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eJKecXZBGHA.3396@.tk2msftngp13.phx.gbl...
> Make sure both SQL Agent and SSIS services are running.
> --
> Andrew J. Kelly SQL MVP
>
> "Peter Lawton" <devnull@.fakedomain.com> wrote in message
> news:u%23%23KJOZBGHA.3984@.TK2MSFTNGP14.phx.gbl...
>> I'm trying to create a simple backup job using the maintenance wizard in
>> SQL 2005 and get the error below, anyone know what I'm doing wrong? (of
>> course the "For help click" link goes nowhere as usual)
>> Thanks
>> Maintenance Plan Wizard Progress
>> - Creating maintenance plan "MaintenancePlan" (Error)
>> Messages
>> Create maintenance plan failed.
>> --
>> ADDITIONAL INFORMATION:
>> Create failed for JobStep 'Subplan'.
>> (Microsoft.SqlServer.MaintenancePlanTasks)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+JobStep&LinkId=20476
>> --
>> An exception occurred while executing a Transact-SQL statement or batch.
>> (Microsoft.SqlServer.ConnectionInfo)
>> --
>> The specified '@.subsystem' is invalid (valid values are returned by
>> sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=14234&LinkId=20476
>> - Adding tasks to the maintenance plan (Stopped)
>> - Adding scheduling options (Stopped)
>> - Adding reporting options (Stopped)
>> - Saving maintenance plan "MaintenancePlan" (Stopped)
>|||I spoke too soon, I'm getting exactly the same issue on a second server I've
just upgraded from SQL 2000 to SQL 2005
If I try to create a new maintenance job or migrate any of the legace
maintenace jobs it fails with the error:-
The specified '@.subsystem' is invalid (valid values are returned by
sp_enum_sqlagent_subsystems). (.Net SqlClient Data Provider)
Error Number: 14234
Severity: 16
State: 1
Procedure: sp_verify_subsystem
Line Number: 21
"Peter Lawton" <devnull@.fakedomain.com> wrote in message
news:%23MAERcaBGHA.216@.TK2MSFTNGP15.phx.gbl...
> Very weird, everything looked OK, but I completely un-installed SQL2005
> and re-installed it and everything works now, no differences in the two
> installs that I know of.
> Anyway, problem fixed now - thanks for the help
> Peter Lawton
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:eJKecXZBGHA.3396@.tk2msftngp13.phx.gbl...
>> Make sure both SQL Agent and SSIS services are running.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Peter Lawton" <devnull@.fakedomain.com> wrote in message
>> news:u%23%23KJOZBGHA.3984@.TK2MSFTNGP14.phx.gbl...
>> I'm trying to create a simple backup job using the maintenance wizard in
>> SQL 2005 and get the error below, anyone know what I'm doing wrong? (of
>> course the "For help click" link goes nowhere as usual)
>> Thanks
>> Maintenance Plan Wizard Progress
>> - Creating maintenance plan "MaintenancePlan" (Error)
>> Messages
>> Create maintenance plan failed.
>> --
>> ADDITIONAL INFORMATION:
>> Create failed for JobStep 'Subplan'.
>> (Microsoft.SqlServer.MaintenancePlanTasks)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+JobStep&LinkId=20476
>> --
>> An exception occurred while executing a Transact-SQL statement or batch.
>> (Microsoft.SqlServer.ConnectionInfo)
>> --
>> The specified '@.subsystem' is invalid (valid values are returned by
>> sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=14234&LinkId=20476
>> - Adding tasks to the maintenance plan (Stopped)
>> - Adding scheduling options (Stopped)
>> - Adding reporting options (Stopped)
>> - Saving maintenance plan "MaintenancePlan" (Stopped)
>>
>|||OK, I've found the problem :)
Maintenance plans need "SQL Integration Services" installed to work.
Peter Lawton
"Peter Lawton" <devnull@.dummydomain.com> wrote in message
news:%23b2pOPiBGHA.3840@.TK2MSFTNGP15.phx.gbl...
>I spoke too soon, I'm getting exactly the same issue on a second server
>I've just upgraded from SQL 2000 to SQL 2005
> If I try to create a new maintenance job or migrate any of the legace
> maintenace jobs it fails with the error:-
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum_sqlagent_subsystems). (.Net SqlClient Data Provider)
> Error Number: 14234
> Severity: 16
> State: 1
> Procedure: sp_verify_subsystem
> Line Number: 21
>
> "Peter Lawton" <devnull@.fakedomain.com> wrote in message
> news:%23MAERcaBGHA.216@.TK2MSFTNGP15.phx.gbl...
>> Very weird, everything looked OK, but I completely un-installed SQL2005
>> and re-installed it and everything works now, no differences in the two
>> installs that I know of.
>> Anyway, problem fixed now - thanks for the help
>> Peter Lawton
>> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> news:eJKecXZBGHA.3396@.tk2msftngp13.phx.gbl...
>> Make sure both SQL Agent and SSIS services are running.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Peter Lawton" <devnull@.fakedomain.com> wrote in message
>> news:u%23%23KJOZBGHA.3984@.TK2MSFTNGP14.phx.gbl...
>> I'm trying to create a simple backup job using the maintenance wizard
>> in SQL 2005 and get the error below, anyone know what I'm doing wrong?
>> (of course the "For help click" link goes nowhere as usual)
>> Thanks
>> Maintenance Plan Wizard Progress
>> - Creating maintenance plan "MaintenancePlan" (Error)
>> Messages
>> Create maintenance plan failed.
>> --
>> ADDITIONAL INFORMATION:
>> Create failed for JobStep 'Subplan'.
>> (Microsoft.SqlServer.MaintenancePlanTasks)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+JobStep&LinkId=20476
>> --
>> An exception occurred while executing a Transact-SQL statement or
>> batch. (Microsoft.SqlServer.ConnectionInfo)
>> --
>> The specified '@.subsystem' is invalid (valid values are returned by
>> sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=14234&LinkId=20476
>> - Adding tasks to the maintenance plan (Stopped)
>> - Adding scheduling options (Stopped)
>> - Adding reporting options (Stopped)
>> - Saving maintenance plan "MaintenancePlan" (Stopped)
>>
>>
>|||Yes as I stated SQL Server Integration Services or "SSIS" for short must be
running. But by learning the hard way you won't have that problem again<g>.
--
Andrew J. Kelly SQL MVP
"Peter Lawton" <devnull@.dummydomain.com> wrote in message
news:uc2mfciBGHA.628@.TK2MSFTNGP14.phx.gbl...
> OK, I've found the problem :)
> Maintenance plans need "SQL Integration Services" installed to work.
> Peter Lawton
> "Peter Lawton" <devnull@.dummydomain.com> wrote in message
> news:%23b2pOPiBGHA.3840@.TK2MSFTNGP15.phx.gbl...
>>I spoke too soon, I'm getting exactly the same issue on a second server
>>I've just upgraded from SQL 2000 to SQL 2005
>> If I try to create a new maintenance job or migrate any of the legace
>> maintenace jobs it fails with the error:-
>> The specified '@.subsystem' is invalid (valid values are returned by
>> sp_enum_sqlagent_subsystems). (.Net SqlClient Data Provider)
>> Error Number: 14234
>> Severity: 16
>> State: 1
>> Procedure: sp_verify_subsystem
>> Line Number: 21
>>
>> "Peter Lawton" <devnull@.fakedomain.com> wrote in message
>> news:%23MAERcaBGHA.216@.TK2MSFTNGP15.phx.gbl...
>> Very weird, everything looked OK, but I completely un-installed SQL2005
>> and re-installed it and everything works now, no differences in the two
>> installs that I know of.
>> Anyway, problem fixed now - thanks for the help
>> Peter Lawton
>> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> news:eJKecXZBGHA.3396@.tk2msftngp13.phx.gbl...
>> Make sure both SQL Agent and SSIS services are running.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Peter Lawton" <devnull@.fakedomain.com> wrote in message
>> news:u%23%23KJOZBGHA.3984@.TK2MSFTNGP14.phx.gbl...
>> I'm trying to create a simple backup job using the maintenance wizard
>> in SQL 2005 and get the error below, anyone know what I'm doing wrong?
>> (of course the "For help click" link goes nowhere as usual)
>> Thanks
>> Maintenance Plan Wizard Progress
>> - Creating maintenance plan "MaintenancePlan" (Error)
>> Messages
>> Create maintenance plan failed.
>> --
>> ADDITIONAL INFORMATION:
>> Create failed for JobStep 'Subplan'.
>> (Microsoft.SqlServer.MaintenancePlanTasks)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+JobStep&LinkId=20476
>> --
>> An exception occurred while executing a Transact-SQL statement or
>> batch. (Microsoft.SqlServer.ConnectionInfo)
>> --
>> The specified '@.subsystem' is invalid (valid values are returned by
>> sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=14234&LinkId=20476
>> - Adding tasks to the maintenance plan (Stopped)
>> - Adding scheduling options (Stopped)
>> - Adding reporting options (Stopped)
>> - Saving maintenance plan "MaintenancePlan" (Stopped)
>>
>>
>>
>|||Yes, you're very right :)
I expect it's a mistake a lot of people will make though as it's not at all
obvious why an optional component is needed for basic tasks, and the error
message isn't at all helpful.
Peter Lawton
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OuI9JcjBGHA.4076@.TK2MSFTNGP14.phx.gbl...
> Yes as I stated SQL Server Integration Services or "SSIS" for short must
> be running. But by learning the hard way you won't have that problem
> again<g>.
> --
> Andrew J. Kelly SQL MVP
>
> "Peter Lawton" <devnull@.dummydomain.com> wrote in message
> news:uc2mfciBGHA.628@.TK2MSFTNGP14.phx.gbl...
>> OK, I've found the problem :)
>> Maintenance plans need "SQL Integration Services" installed to work.
>> Peter Lawton
>> "Peter Lawton" <devnull@.dummydomain.com> wrote in message
>> news:%23b2pOPiBGHA.3840@.TK2MSFTNGP15.phx.gbl...
>>I spoke too soon, I'm getting exactly the same issue on a second server
>>I've just upgraded from SQL 2000 to SQL 2005
>> If I try to create a new maintenance job or migrate any of the legace
>> maintenace jobs it fails with the error:-
>> The specified '@.subsystem' is invalid (valid values are returned by
>> sp_enum_sqlagent_subsystems). (.Net SqlClient Data Provider)
>> Error Number: 14234
>> Severity: 16
>> State: 1
>> Procedure: sp_verify_subsystem
>> Line Number: 21
>>
>> "Peter Lawton" <devnull@.fakedomain.com> wrote in message
>> news:%23MAERcaBGHA.216@.TK2MSFTNGP15.phx.gbl...
>> Very weird, everything looked OK, but I completely un-installed SQL2005
>> and re-installed it and everything works now, no differences in the two
>> installs that I know of.
>> Anyway, problem fixed now - thanks for the help
>> Peter Lawton
>> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
>> news:eJKecXZBGHA.3396@.tk2msftngp13.phx.gbl...
>> Make sure both SQL Agent and SSIS services are running.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Peter Lawton" <devnull@.fakedomain.com> wrote in message
>> news:u%23%23KJOZBGHA.3984@.TK2MSFTNGP14.phx.gbl...
>> I'm trying to create a simple backup job using the maintenance wizard
>> in SQL 2005 and get the error below, anyone know what I'm doing
>> wrong? (of course the "For help click" link goes nowhere as usual)
>> Thanks
>> Maintenance Plan Wizard Progress
>> - Creating maintenance plan "MaintenancePlan" (Error)
>> Messages
>> Create maintenance plan failed.
>> --
>> ADDITIONAL INFORMATION:
>> Create failed for JobStep 'Subplan'.
>> (Microsoft.SqlServer.MaintenancePlanTasks)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+JobStep&LinkId=20476
>> --
>> An exception occurred while executing a Transact-SQL statement or
>> batch. (Microsoft.SqlServer.ConnectionInfo)
>> --
>> The specified '@.subsystem' is invalid (valid values are returned by
>> sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=14234&LinkId=20476
>> - Adding tasks to the maintenance plan (Stopped)
>> - Adding scheduling options (Stopped)
>> - Adding reporting options (Stopped)
>> - Saving maintenance plan "MaintenancePlan" (Stopped)
>>
>>
>>
>>
>

Can't connect to SQl Server 2005 with sa Login

Hello,

I recently installed SQL2005 and SQL2000. I only created SA login permissions with Admin access to the database (There are no Windows Users that have access).

I then installed SQL2000 and it overwrote the "mixed connection mode" . whenever I try to connect with the sa login I get the following error

Login failed for user 'sa'. The user is not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)

The problem is explained in a fix http://support.microsoft.com/kb/269587

The only problem is that the fix requires access rights that I don't have. My only logins are "BuiltIn\Users" that have public access rights and then a "sa" login (that doesn't work) that has Admin rights within the db engine.

So my question is... Can I create an sysadmin account with windows authentication (for a normal Windows Admin Account) without having the proper rights within the database engine?

-Tom

I would recommend taking a look to the followign post:

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

If the information there doesn't help you, please let us know, we will be glad to help.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

Can't connect to sql server 2005 after sysprep

I've installed sql2005 on win2k3, running on virtual pc... I can connect to
the sql server using sql server management studio... Because I'm building
base environment for testing, I seal the machine using sysprep. When I start
a new machine, I get this error...
"A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. (provider: Shraed Memory
Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft
SQL Server, Error: 233)
Any idea how to solve this?
Best Regards,
Kit Kai
MVP (asp.net)
SgDotNet Council Member
Visit us @. http://www.sgdotnet.org
My Blog: http://community.sgdotnet.org/blogs/kitkaiHi Loke,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you setup a machine with SQL Server
2005 and after using sysprep (something like GHOST, am I right?), the SQL
Server report the error message 233. If I have misunderstood your concern,
please feel free to point it out.
Since you are using sysprep, does the machine name remains the same? Please
perform the steps below and let me knwo whether it resolved your issue.
1. Open SQL Server Surface Area Configuration
Click 'Surface Area Configuration for Services and Connections'
Extend Database Engine and make sure Remote Connections is enabled for
both TCP/IP and named pipes.
2. Restart the SQL Server
3. Make sure the Firewall is configured correctly.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Yup... You understood my problem perfectly.
In this case, the machine name remains the same, but this would be the only
case where the machine name remains the same... Basically, this setup will
be used as a base for other differentiating disk to build upon.
I've followed your steps, but the problem still remains. Firewall shouldn't
be the cause, since I'm still access sql using the same machine...
Best Regards,
Kit Kai
MVP (asp.net)
SgDotNet Council Member
Visit us @. http://www.sgdotnet.org
My Blog: http://community.sgdotnet.org/blogs/kitkai
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:7nDahdh%23FHA.1236@.TK2MSFTNGXA02.phx.gbl...
> Hi Loke,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood you setup a machine with SQL Server
> 2005 and after using sysprep (something like GHOST, am I right?), the SQL
> Server report the error message 233. If I have misunderstood your concern,
> please feel free to point it out.
> Since you are using sysprep, does the machine name remains the same?
> Please
> perform the steps below and let me knwo whether it resolved your issue.
> 1. Open SQL Server Surface Area Configuration
> Click 'Surface Area Configuration for Services and Connections'
> Extend Database Engine and make sure Remote Connections is enabled for
> both TCP/IP and named pipes.
> 2. Restart the SQL Server
> 3. Make sure the Firewall is configured correctly.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Kit,
This is a very strange issue. Unfortunately, I am afraid it is not
supported to install SQL Server 2005 like this due to license issues. Would
you please completely uninstall SQL Server 2005 and then reinstall it to
see whether you could login SQL Server 2005 this time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Found the solution with Sukhdev's help.
Posted it @.
http://community.sgdotnet.org/blogs...2/13/23344.aspx
Best Regards,
Kit Kai
MVP (asp.net)
SgDotNet Council Member
Visit us @. http://www.sgdotnet.org
My Blog: http://community.sgdotnet.org/blogs/kitkai
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:Tx%23OqCx%23FHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Kit,
> This is a very strange issue. Unfortunately, I am afraid it is not
> supported to install SQL Server 2005 like this due to license issues.
> Would
> you please completely uninstall SQL Server 2005 and then reinstall it to
> see whether you could login SQL Server 2005 this time?
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Kit,
Thanks so much for the update and share this invaluable experience here. I
believe other communities will also benefit much from this.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

Can't connect to sql server 2005 after sysprep

I've installed sql2005 on win2k3, running on virtual pc... I can connect to
the sql server using sql server management studio... Because I'm building
base environment for testing, I seal the machine using sysprep. When I start
a new machine, I get this error...
"A connection was successfully established with the server, but then an
error occurred during the pre-login handshake. (provider: Shraed Memory
Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft
SQL Server, Error: 233)
Any idea how to solve this?
Best Regards,
Kit Kai
MVP (asp.net)
SgDotNet Council Member
Visit us @. http://www.sgdotnet.org
My Blog: http://community.sgdotnet.org/blogs/kitkai
Hi Loke,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you setup a machine with SQL Server
2005 and after using sysprep (something like GHOST, am I right?), the SQL
Server report the error message 233. If I have misunderstood your concern,
please feel free to point it out.
Since you are using sysprep, does the machine name remains the same? Please
perform the steps below and let me knwo whether it resolved your issue.
1. Open SQL Server Surface Area Configuration
Click 'Surface Area Configuration for Services and Connections'
Extend Database Engine and make sure Remote Connections is enabled for
both TCP/IP and named pipes.
2. Restart the SQL Server
3. Make sure the Firewall is configured correctly.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Yup... You understood my problem perfectly.
In this case, the machine name remains the same, but this would be the only
case where the machine name remains the same... Basically, this setup will
be used as a base for other differentiating disk to build upon.
I've followed your steps, but the problem still remains. Firewall shouldn't
be the cause, since I'm still access sql using the same machine...
Best Regards,
Kit Kai
MVP (asp.net)
SgDotNet Council Member
Visit us @. http://www.sgdotnet.org
My Blog: http://community.sgdotnet.org/blogs/kitkai
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:7nDahdh%23FHA.1236@.TK2MSFTNGXA02.phx.gbl...
> Hi Loke,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood you setup a machine with SQL Server
> 2005 and after using sysprep (something like GHOST, am I right?), the SQL
> Server report the error message 233. If I have misunderstood your concern,
> please feel free to point it out.
> Since you are using sysprep, does the machine name remains the same?
> Please
> perform the steps below and let me knwo whether it resolved your issue.
> 1. Open SQL Server Surface Area Configuration
> Click 'Surface Area Configuration for Services and Connections'
> Extend Database Engine and make sure Remote Connections is enabled for
> both TCP/IP and named pipes.
> 2. Restart the SQL Server
> 3. Make sure the Firewall is configured correctly.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||Hi Kit,
This is a very strange issue. Unfortunately, I am afraid it is not
supported to install SQL Server 2005 like this due to license issues. Would
you please completely uninstall SQL Server 2005 and then reinstall it to
see whether you could login SQL Server 2005 this time?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Found the solution with Sukhdev's help.
Posted it @.
http://community.sgdotnet.org/blogs/.../13/23344.aspx
Best Regards,
Kit Kai
MVP (asp.net)
SgDotNet Council Member
Visit us @. http://www.sgdotnet.org
My Blog: http://community.sgdotnet.org/blogs/kitkai
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:Tx%23OqCx%23FHA.3764@.TK2MSFTNGXA02.phx.gbl...
> Hi Kit,
> This is a very strange issue. Unfortunately, I am afraid it is not
> supported to install SQL Server 2005 like this due to license issues.
> Would
> you please completely uninstall SQL Server 2005 and then reinstall it to
> see whether you could login SQL Server 2005 this time?
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||Hi Kit,
Thanks so much for the update and share this invaluable experience here. I
believe other communities will also benefit much from this.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Cant connect to SQL server 2000 instance from domain machines

Hi
We currently have installed sql2005 (installed first as default
instance) and sql 2000 with a named instance. When developing sites
and using connection strings, we can access the sql2000 db fine by
using SERVERNAME\INSTANCENAME.
However, if we try to connect via enterprise manager from any other
machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
and the instance name alone wont work either.
How do we get round this as at present, we are having to log into the
database server to make any changes etc!!!
Novice here so excuse me if I have missed anything obvious!
Cheers
RajThe easiest workaround would be to connect to the instance using its IP
address followed by a comma and then the port number. You should not use just
hte instance name alone. The SQL Server instance name is not a newtwork name
and won't get resolved to an IP/port number.
Can you connect to the default instance (SQL2005) from a machine where you
can't connect to the SQL2000 instance using ServerName\Instance?
Linchi
"karwalr@.hotmail.com" wrote:
> Hi
> We currently have installed sql2005 (installed first as default
> instance) and sql 2000 with a named instance. When developing sites
> and using connection strings, we can access the sql2000 db fine by
> using SERVERNAME\INSTANCENAME.
> However, if we try to connect via enterprise manager from any other
> machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
> and the instance name alone wont work either.
> How do we get round this as at present, we are having to log into the
> database server to make any changes etc!!!
> Novice here so excuse me if I have missed anything obvious!
> Cheers
> Raj
>|||Managed to sort it. I set it up on my client machine Client Network
Alias to map to the server and the port as suggested. Found the
documentation at Microsoft..
http://support.microsoft.com/kb/265808/en-us
Many thanks!

Cant connect to SQL server 2000 instance from domain machines

Hi
We currently have installed sql2005 (installed first as default
instance) and sql 2000 with a named instance. When developing sites
and using connection strings, we can access the sql2000 db fine by
using SERVERNAME\INSTANCENAME.
However, if we try to connect via enterprise manager from any other
machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
and the instance name alone wont work either.
How do we get round this as at present, we are having to log into the
database server to make any changes etc!!!
Novice here so excuse me if I have missed anything obvious!
Cheers
RajThe easiest workaround would be to connect to the instance using its IP
address followed by a comma and then the port number. You should not use jus
t
hte instance name alone. The SQL Server instance name is not a newtwork name
and won't get resolved to an IP/port number.
Can you connect to the default instance (SQL2005) from a machine where you
can't connect to the SQL2000 instance using ServerName\Instance?
Linchi
"karwalr@.hotmail.com" wrote:

> Hi
> We currently have installed sql2005 (installed first as default
> instance) and sql 2000 with a named instance. When developing sites
> and using connection strings, we can access the sql2000 db fine by
> using SERVERNAME\INSTANCENAME.
> However, if we try to connect via enterprise manager from any other
> machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
> and the instance name alone wont work either.
> How do we get round this as at present, we are having to log into the
> database server to make any changes etc!!!
> Novice here so excuse me if I have missed anything obvious!
> Cheers
> Raj
>|||Managed to sort it. I set it up on my client machine Client Network
Alias to map to the server and the port as suggested. Found the
documentation at Microsoft..
http://support.microsoft.com/kb/265808/en-us
Many thanks!

Can't connect to SeptCTP x64

I've built and deployed cubes on a x64 server, with x64 SQL2005 SeptCTP.

Works pretty much fine. I can run 32 bit Excel on the server, and browse the cubes no problem.

However, if I fire up 32 bit Excel on my 32 bit client machine, and go through the MultiDimensional data source wizard to connet to the cubes, after I put the server name in, it throws this error:

"The peer prematurely closed the connection"

Then this error:

"An error was encountered in the transport layer"

Like a fool, I went from 32 bit to 64 bit and from JunCTP to SeptCTP at the same time, so I don't know which is to blame.

I'm aware of the classic "re-register msolap90.dll on the client" fix, and I've tried it, and it aint that.

Any ideas?

Some more info on this:

If I open up SeptCTP Management Studio on a 32 bit client machine, connect to the Analysis Server on the 64 bit server, it connects. I can see the database on teh x64 machine, and below that, I can see the Data Source, DSVs, Cubes etc.

BUT

When I right click on cube, and try to browse, it fails with the following error:

Cannot show requested dialog.

ADDITIONAL INFORMATION:

Deserialization failed: The 'EditionID' element in the 'http://schemas.microsoft.com/analysisservices/2003/engine' namespace is unexpected. (Microsoft.AnalysisServices)

Exactly the same error presents whether I try to get the properties of a cub, data source, dsv, whatever.

I do not understand this at all.

|||I got the same error on deploying my project. It works fine on Jun CTP but got the error in Sep CTP and the MSSQL 2005 evaluation copy. Any advise? Thanks in advance!

Can't connect to SeptCTP x64

I've built and deployed cubes on a x64 server, with x64 SQL2005 SeptCTP.

Works pretty much fine. I can run 32 bit Excel on the server, and browse the cubes no problem.

However, if I fire up 32 bit Excel on my 32 bit client machine, and go through the MultiDimensional data source wizard to connet to the cubes, after I put the server name in, it throws this error:

"The peer prematurely closed the connection"

Then this error:

"An error was encountered in the transport layer"

Like a fool, I went from 32 bit to 64 bit and from JunCTP to SeptCTP at the same time, so I don't know which is to blame.

I'm aware of the classic "re-register msolap90.dll on the client" fix, and I've tried it, and it aint that.

Any ideas?

Some more info on this:

If I open up SeptCTP Management Studio on a 32 bit client machine, connect to the Analysis Server on the 64 bit server, it connects. I can see the database on teh x64 machine, and below that, I can see the Data Source, DSVs, Cubes etc.

BUT

When I right click on cube, and try to browse, it fails with the following error:

Cannot show requested dialog.

ADDITIONAL INFORMATION:

Deserialization failed: The 'EditionID' element in the 'http://schemas.microsoft.com/analysisservices/2003/engine' namespace is unexpected. (Microsoft.AnalysisServices)

Exactly the same error presents whether I try to get the properties of a cub, data source, dsv, whatever.

I do not understand this at all.

|||I got the same error on deploying my project. It works fine on Jun CTP but got the error in Sep CTP and the MSSQL 2005 evaluation copy. Any advise? Thanks in advance!

Can't connect from ASP.Net 2.0 to SQL2000 after installing SQL2005

Hey guys,
I have a web application in ASP.Net 2.0 that needs to connect to a local
SQL2000 DB. After I installed SQL2005 this web app stopped working. I get
the following inner exception:
{"An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified)"}
So after unsuccessfully googling I'm at least pretty sure about the
following: My web app thinks it's talking to a SQL2005 server. That one by
default uses shared memory when local. I think SQL2000 uses TCP/IP.
Who can tell me what I have to do so that my ASP.Net 2.0 web app properly
connects to SQL2000? Among the ideas on Google there were cliconfg.exe,
using <clear /> in the <connectionStrings> area in web.config and a couple
more. But none of them worked.
Thanks a lot, ChristophI'm having a very similar error, only mine connects locally but not remotely.
I was able to change the error slightly by putting the referencing the
database by domain and db, myMachine/myDB.
If it helps I looked at my log and it gave an error of 17187 which seems to
be a file in use, full disk, or low memory. Still researching. If I find it
I'll let you know. If you find the answer would you please post it so I can
try it too?
--
---
Magic is not in the hands of the magician but in the mind of the audience.
Animadverto est verus
"Christoph Wienands" wrote:
> Hey guys,
> I have a web application in ASP.Net 2.0 that needs to connect to a local
> SQL2000 DB. After I installed SQL2005 this web app stopped working. I get
> the following inner exception:
> {"An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> (provider: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance Specified)"}
> So after unsuccessfully googling I'm at least pretty sure about the
> following: My web app thinks it's talking to a SQL2005 server. That one by
> default uses shared memory when local. I think SQL2000 uses TCP/IP.
> Who can tell me what I have to do so that my ASP.Net 2.0 web app properly
> connects to SQL2000? Among the ideas on Google there were cliconfg.exe,
> using <clear /> in the <connectionStrings> area in web.config and a couple
> more. But none of them worked.
> Thanks a lot, Christoph
>
>