Can't connect from a vista client to SQL 2005 box,other machines work fine

Hey. I've a windows vista machine which can't connect to SQL 2005 box. Other machines which are lower than vista work fine. Also, vista box can connect to other SQL 2005 instances but can't connect to only one instance. But, I can connect to the instance fine from my XP box. Also, it's not a permissions issue. This user is an SA and can connect form some other machine. SQL 2005 box is at 2047 version right now. And, the user is able to connect to some other boxes which are also at 2047. Please help. Thank you

Add the account sepcifically to the SQL Server. When you connect from Vista (because of the UAC) it strips out your group SID from local admins, so SQL Server doesn't know who you are, and that's probably what is causing your issue. Add the user's account by name to the box.

If this post answers your question, make sure you mark it "answered" so others can find it quickly.

Thanks -

Buck Woody
http://www.buckwoody.com

Can't conenct to sql 2005

Hi,
Can you connect to SQL 2005 if you're not part of the domain the server is
installed in?
I installed the client and it can see my SQL 2000 server but not the SQL
2005 server.
Is it because the laptop I installed it on is not part of the domain?
If so, beside having it join the domain, is there a way to connect to it?
Thanks!
Simon
Hi,
this is not easy tell. Is SQL Server 2005 installed on the same box as SQL
Server 2000 ? Does it have a default port or any other than the 1433 port ?
If using a dynamic or any other port, do you have SQL Browser started on the
2k5 box ? If you cant start SQL Browser for some reason, did you try to
specify the port number after the server name to make the connection using
Servername,Portnumber as the servername within your connection dialogues ?
Jens K. Suessmeyer.
http://www.sqlserver2005.de
"Simon Renshaw" <simon@.benchmarkconsulting.com> wrote in message
news:OHQCXfoYHHA.4008@.TK2MSFTNGP05.phx.gbl...
> Hi,
> Can you connect to SQL 2005 if you're not part of the domain the server is
> installed in?
> I installed the client and it can see my SQL 2000 server but not the SQL
> 2005 server.
> Is it because the laptop I installed it on is not part of the domain?
> If so, beside having it join the domain, is there a way to connect to it?
> Thanks!
> Simon
>
|||No, 2005 and 2000 are installed on different machines. And I used the
standard ports.
By the client I meant the SQL Server Management Studio. Sorry for the
confusion.
On my station (which is part of the domain), I can access the 2005 server
using SQL Server Management Studio.
On the laptop, I cannot access the 2005 server using SQL Server Management
Studio.
"Jens K. Suessmeyer" <Jens@.NoSpamhere-sqlserver2005.de> wrote in message
news:82730AB1-9842-4B47-A61E-BAED0215B0DE@.microsoft.com...
> Hi,
> this is not easy tell. Is SQL Server 2005 installed on the same box as SQL
> Server 2000 ? Does it have a default port or any other than the 1433 port
> ? If using a dynamic or any other port, do you have SQL Browser started on
> the 2k5 box ? If you cant start SQL Browser for some reason, did you try
> to specify the port number after the server name to make the connection
> using Servername,Portnumber as the servername within your connection
> dialogues ?
> Jens K. Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Simon Renshaw" <simon@.benchmarkconsulting.com> wrote in message
> news:OHQCXfoYHHA.4008@.TK2MSFTNGP05.phx.gbl...
>

Can't assign connection manager object to DataReader Source

I'm trying to create a DataReader source object using a working ADO.NET Oracle Client connection object that exists in the connection manager.

Problem:

When I open the editor the DataReaderSrc component shows only one row under the Connection Managers tab:

Name=IDbConnection
Connection Manager=blank
Description=Managed connection manager

I cannot assign the ADO.NET connection (or any connections). I see a warning at the bottom of the Connection Managers tab:

"Not all connection managers have been set. Set all connection managers."

When I click refresh the warning message changes to:

"The runtime connection manager with the ID "" cannot be found. Verify that the connection manager collection has a connection manager with that ID."

I am prevented from removing the IDbConnection or assigning my Connection Manager object to the DataReader Source.

Thanks, -- Mike

I also have the same problem, I'm sure it must be some tiny detail somewhere / something very basic, but I have been unable to fix it. Can someone help? Thanks!

Hector

|||

I had the same problem because I was using the wrong Provider when specifying my Data Source.

Hope it helps,

Nuno

|||

I had the same problem. In my case the 'advanced editor for datareader source' is very, very confusing. First of all, you have to create a connection manager, which I did already. But, it was not at all intuitive that you have to click on the box under 'connection manager' and select a connection manager. By default the box is black and grayed out like both the other fields which you cannot change. Gee, thanks redmond.

|||Thanks for taking the time to post this answer. I finally learned this last week at a SQL Server training class. The instructor pointed out that you actually need to change the disabled looking box.|||

Hello.

I read that you found a solution, but I didn't understand it very well.

Could you tell me more how to resolve this problem. I have create the connection manager and a cant set it into the DataReader Source

Thank you.

|||

Data Reader source accepts connection manager of Type ADO.NET only.

so First you have to create a Connection Manager to your Data Base using ADO.net Provider ONLY.

open the advanced editior of data reader source, go to connection managers tab, you will see IdbConnection , beside that there will be another column named connection manger, select your created connection manager there (ADO.Net one). Then go to Component properties tab and in sql command enter your sql query. go to columns mapping tab ..now you can see your columns.

|||thank you for your reply. i resolve the problem.|||

hello,

i thought that I resolve the problem of the connection but there was another problem that didn't permit me to save the connection to the advanced editor.

the error is "Component is already connected. The component needs to be disconnected before attempting to connect it."

Can you help me?

Can't assign connection manager object to DataReader Source

I'm trying to create a DataReader source object using a working ADO.NET Oracle Client connection object that exists in the connection manager.

Problem:

When I open the editor the DataReaderSrc component shows only one row under the Connection Managers tab:

Name=IDbConnection
Connection Manager=blank
Description=Managed connection manager

I cannot assign the ADO.NET connection (or any connections). I see a warning at the bottom of the Connection Managers tab:

"Not all connection managers have been set. Set all connection managers."

When I click refresh the warning message changes to:

"The runtime connection manager with the ID "" cannot be found. Verify that the connection manager collection has a connection manager with that ID."

I am prevented from removing the IDbConnection or assigning my Connection Manager object to the DataReader Source.

Thanks, -- Mike

I also have the same problem, I'm sure it must be some tiny detail somewhere / something very basic, but I have been unable to fix it. Can someone help? Thanks!

Hector

|||

I had the same problem because I was using the wrong Provider when specifying my Data Source.

Hope it helps,

Nuno

|||

I had the same problem. In my case the 'advanced editor for datareader source' is very, very confusing. First of all, you have to create a connection manager, which I did already. But, it was not at all intuitive that you have to click on the box under 'connection manager' and select a connection manager. By default the box is black and grayed out like both the other fields which you cannot change. Gee, thanks redmond.

|||Thanks for taking the time to post this answer. I finally learned this last week at a SQL Server training class. The instructor pointed out that you actually need to change the disabled looking box.|||

Hello.

I read that you found a solution, but I didn't understand it very well.

Could you tell me more how to resolve this problem. I have create the connection manager and a cant set it into the DataReader Source

Thank you.

|||

Data Reader source accepts connection manager of Type ADO.NET only.

so First you have to create a Connection Manager to your Data Base using ADO.net Provider ONLY.

open the advanced editior of data reader source, go to connection managers tab, you will see IdbConnection , beside that there will be another column named connection manger, select your created connection manager there (ADO.Net one). Then go to Component properties tab and in sql command enter your sql query. go to columns mapping tab ..now you can see your columns.

|||thank you for your reply. i resolve the problem.|||

hello,

i thought that I resolve the problem of the connection but there was another problem that didn't permit me to save the connection to the advanced editor.

the error is "Component is already connected. The component needs to be disconnected before attempting to connect it."

Can you help me?

Can't assign connection manager object to DataReader Source

I'm trying to create a DataReader source object using a working ADO.NET Oracle Client connection object that exists in the connection manager.

Problem:

When I open the editor the DataReaderSrc component shows only one row under the Connection Managers tab:

Name=IDbConnection
Connection Manager=blank
Description=Managed connection manager

I cannot assign the ADO.NET connection (or any connections). I see a warning at the bottom of the Connection Managers tab:

"Not all connection managers have been set. Set all connection managers."

When I click refresh the warning message changes to:

"The runtime connection manager with the ID "" cannot be found. Verify that the connection manager collection has a connection manager with that ID."

I am prevented from removing the IDbConnection or assigning my Connection Manager object to the DataReader Source.

Thanks, -- Mike

I also have the same problem, I'm sure it must be some tiny detail somewhere / something very basic, but I have been unable to fix it. Can someone help? Thanks!

Hector

|||

I had the same problem because I was using the wrong Provider when specifying my Data Source.

Hope it helps,

Nuno

|||

I had the same problem. In my case the 'advanced editor for datareader source' is very, very confusing. First of all, you have to create a connection manager, which I did already. But, it was not at all intuitive that you have to click on the box under 'connection manager' and select a connection manager. By default the box is black and grayed out like both the other fields which you cannot change. Gee, thanks redmond.

|||Thanks for taking the time to post this answer. I finally learned this last week at a SQL Server training class. The instructor pointed out that you actually need to change the disabled looking box.|||

Hello.

I read that you found a solution, but I didn't understand it very well.

Could you tell me more how to resolve this problem. I have create the connection manager and a cant set it into the DataReader Source

Thank you.

|||

Data Reader source accepts connection manager of Type ADO.NET only.

so First you have to create a Connection Manager to your Data Base using ADO.net Provider ONLY.

open the advanced editior of data reader source, go to connection managers tab, you will see IdbConnection , beside that there will be another column named connection manger, select your created connection manager there (ADO.Net one). Then go to Component properties tab and in sql command enter your sql query. go to columns mapping tab ..now you can see your columns.

|||thank you for your reply. i resolve the problem.|||

hello,

i thought that I resolve the problem of the connection but there was another problem that didn't permit me to save the connection to the advanced editor.

the error is "Component is already connected. The component needs to be disconnected before attempting to connect it."

Can you help me?

Can't assign connection manager object to DataReader Source

I'm trying to create a DataReader source object using a working ADO.NET Oracle Client connection object that exists in the connection manager.

Problem:

When I open the editor the DataReaderSrc component shows only one row under the Connection Managers tab:

Name=IDbConnection
Connection Manager=blank
Description=Managed connection manager

I cannot assign the ADO.NET connection (or any connections). I see a warning at the bottom of the Connection Managers tab:

"Not all connection managers have been set. Set all connection managers."

When I click refresh the warning message changes to:

"The runtime connection manager with the ID "" cannot be found. Verify that the connection manager collection has a connection manager with that ID."

I am prevented from removing the IDbConnection or assigning my Connection Manager object to the DataReader Source.

Thanks, -- Mike

I also have the same problem, I'm sure it must be some tiny detail somewhere / something very basic, but I have been unable to fix it. Can someone help? Thanks!

Hector

|||

I had the same problem because I was using the wrong Provider when specifying my Data Source.

Hope it helps,

Nuno

|||

I had the same problem. In my case the 'advanced editor for datareader source' is very, very confusing. First of all, you have to create a connection manager, which I did already. But, it was not at all intuitive that you have to click on the box under 'connection manager' and select a connection manager. By default the box is black and grayed out like both the other fields which you cannot change. Gee, thanks redmond.

|||Thanks for taking the time to post this answer. I finally learned this last week at a SQL Server training class. The instructor pointed out that you actually need to change the disabled looking box.|||

Hello.

I read that you found a solution, but I didn't understand it very well.

Could you tell me more how to resolve this problem. I have create the connection manager and a cant set it into the DataReader Source

Thank you.

|||

Data Reader source accepts connection manager of Type ADO.NET only.

so First you have to create a Connection Manager to your Data Base using ADO.net Provider ONLY.

open the advanced editior of data reader source, go to connection managers tab, you will see IdbConnection , beside that there will be another column named connection manger, select your created connection manager there (ADO.Net one). Then go to Component properties tab and in sql command enter your sql query. go to columns mapping tab ..now you can see your columns.

|||thank you for your reply. i resolve the problem.|||

hello,

i thought that I resolve the problem of the connection but there was another problem that didn't permit me to save the connection to the advanced editor.

the error is "Component is already connected. The component needs to be disconnected before attempting to connect it."

Can you help me?

Can't assign connection manager object to DataReader Source

I'm trying to create a DataReader source object using a working ADO.NET Oracle Client connection object that exists in the connection manager.

Problem:

When I open the editor the DataReaderSrc component shows only one row under the Connection Managers tab:

Name=IDbConnection
Connection Manager=blank
Description=Managed connection manager

I cannot assign the ADO.NET connection (or any connections). I see a warning at the bottom of the Connection Managers tab:

"Not all connection managers have been set. Set all connection managers."

When I click refresh the warning message changes to:

"The runtime connection manager with the ID "" cannot be found. Verify that the connection manager collection has a connection manager with that ID."

I am prevented from removing the IDbConnection or assigning my Connection Manager object to the DataReader Source.

Thanks, -- Mike

I also have the same problem, I'm sure it must be some tiny detail somewhere / something very basic, but I have been unable to fix it. Can someone help? Thanks!

Hector

|||

I had the same problem because I was using the wrong Provider when specifying my Data Source.

Hope it helps,

Nuno

|||

I had the same problem. In my case the 'advanced editor for datareader source' is very, very confusing. First of all, you have to create a connection manager, which I did already. But, it was not at all intuitive that you have to click on the box under 'connection manager' and select a connection manager. By default the box is black and grayed out like both the other fields which you cannot change. Gee, thanks redmond.

|||Thanks for taking the time to post this answer. I finally learned this last week at a SQL Server training class. The instructor pointed out that you actually need to change the disabled looking box.|||

Hello.

I read that you found a solution, but I didn't understand it very well.

Could you tell me more how to resolve this problem. I have create the connection manager and a cant set it into the DataReader Source

Thank you.

|||

Data Reader source accepts connection manager of Type ADO.NET only.

so First you have to create a Connection Manager to your Data Base using ADO.net Provider ONLY.

open the advanced editior of data reader source, go to connection managers tab, you will see IdbConnection , beside that there will be another column named connection manger, select your created connection manager there (ADO.Net one). Then go to Component properties tab and in sql command enter your sql query. go to columns mapping tab ..now you can see your columns.

|||thank you for your reply. i resolve the problem.|||

hello,

i thought that I resolve the problem of the connection but there was another problem that didn't permit me to save the connection to the advanced editor.

the error is "Component is already connected. The component needs to be disconnected before attempting to connect it."

Can you help me?

sql

Can't apply Sql 2k server service pack 4 on XP workstation.

After install sql 2000 server - client tools on Win XP workstation, it won't
allow to install sql 2000 server Service Pack 4 (it will quit to desktop
immediately without any error or warning) But we can intall it on win2000
workstation.
- Is it normal that can't apply or not need to apply service pack on winXP
clients?
- How can I check which sql 2000 server service pack applied on clients?
No that wouldn't be considered normal. You do want to apply
the service packs to PC where the client tools are
installed.
You can open Query Analyzer and go to Help, About to
determine the build number of the client tools.
Build numbers and corresponding service packs are listed in
this article:
http://support.microsoft.com/kb/321185
-Sue
On Thu, 14 Jun 2007 09:46:14 +0800, "Pleo"
<pleoel@.hotmail.com> wrote:

>After install sql 2000 server - client tools on Win XP workstation, it won't
>allow to install sql 2000 server Service Pack 4 (it will quit to desktop
>immediately without any error or warning) But we can intall it on win2000
>workstation.
>- Is it normal that can't apply or not need to apply service pack on winXP
>clients?
>- How can I check which sql 2000 server service pack applied on clients?
>
sql

Can't access SqlServer 2005 using JDBC

Hi;

I can access SqlServer 2000 fine, but not SqlServer 2005. My client is on Windows XP and SqlServer 2005 (dev version) is on Windows 2003. When I run I get:

Error: net.windward.datasource.DataSourceException: JdbcDataSource could not ope
n jdbc:sqlserver://T1-Databases;databaseName=AdventureWorks;integratedSecurity=t
rue;
net.windward.datasource.DataSourceException: net.windward.datasource.DataSourceE
xception: JdbcDataSource could not open jdbc:sqlserver://T1-Databases;databaseNa
me=AdventureWorks;integratedSecurity=true;
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1030)
at net.windward.xmlreport.RunReport.main(RunReport.java:165)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U
nknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour
ce)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1024)
... 1 more
Exception in thread "main" net.windward.datasource.DataSourceException: net.wind
ward.datasource.DataSourceException: JdbcDataSource could not open jdbc:sqlserve
r://T1-Databases;databaseName=AdventureWorks;integratedSecurity=true;
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1030)
at net.windward.xmlreport.RunReport.main(RunReport.java:165)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true
at
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U
nknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour
ce)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1024)
... 1 more

Any ideas?

thanks - dave

Are you using Microsoft SQL Server 2005 JDBC Driver version 1.1?

What platform (OS and version) does your JDBC client run on?

|||

I have similar error:

java.lang.NoClassDefFoundError
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)

I do have the JDBC driver version 1.1.

Cocoon 2.0

Tomcat 4.x

|||

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true

It appears as though it has something to do with integratedSecurity. I think the connection string is case sensitive, you did spell it IntegratedSecurity="True" right? The exception thrown seems to be targetted to integratedSecurity specifically. Also, are you authenticating in mixed mode or windows only? Did you configure the server on install correctly to be able to authenticate the kind of connection you are trying to make?

Hope we can figure this one out together,

John

|||

Have you tried enabling the TCP/IP Protocol through the SQL Server Configuration Manager? I seem to recall it being turned off by default in SQL 2005. Enable it and restart the SQL Service.

Good luck,

-Tom

|||You can run SQL Profiler to check if your application is indeed trying to establish a connection or not.|||It looks like you are using the 1.0 dirver which did not support integrated auth property.sql

Can't access SqlServer 2005 using JDBC

Hi;

I can access SqlServer 2000 fine, but not SqlServer 2005. My client is on Windows XP and SqlServer 2005 (dev version) is on Windows 2003. When I run I get:

Error: net.windward.datasource.DataSourceException: JdbcDataSource could not ope
n jdbc:sqlserver://T1-Databases;databaseName=AdventureWorks;integratedSecurity=t
rue;
net.windward.datasource.DataSourceException: net.windward.datasource.DataSourceE
xception: JdbcDataSource could not open jdbc:sqlserver://T1-Databases;databaseNa
me=AdventureWorks;integratedSecurity=true;
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1030)
at net.windward.xmlreport.RunReport.main(RunReport.java:165)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U
nknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour
ce)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1024)
... 1 more
Exception in thread "main" net.windward.datasource.DataSourceException: net.wind
ward.datasource.DataSourceException: JdbcDataSource could not open jdbc:sqlserve
r://T1-Databases;databaseName=AdventureWorks;integratedSecurity=true;
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1030)
at net.windward.xmlreport.RunReport.main(RunReport.java:165)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true
at
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U
nknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour
ce)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1024)
... 1 more

Any ideas?

thanks - dave

Are you using Microsoft SQL Server 2005 JDBC Driver version 1.1?

What platform (OS and version) does your JDBC client run on?

|||

I have similar error:

java.lang.NoClassDefFoundError
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)

I do have the JDBC driver version 1.1.

Cocoon 2.0

Tomcat 4.x

|||

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true

It appears as though it has something to do with integratedSecurity. I think the connection string is case sensitive, you did spell it IntegratedSecurity="True" right? The exception thrown seems to be targetted to integratedSecurity specifically. Also, are you authenticating in mixed mode or windows only? Did you configure the server on install correctly to be able to authenticate the kind of connection you are trying to make?

Hope we can figure this one out together,

John

|||

Have you tried enabling the TCP/IP Protocol through the SQL Server Configuration Manager? I seem to recall it being turned off by default in SQL 2005. Enable it and restart the SQL Service.

Good luck,

-Tom

|||You can run SQL Profiler to check if your application is indeed trying to establish a connection or not.|||It looks like you are using the 1.0 dirver which did not support integrated auth property.

Can't access SqlServer 2005 using JDBC

Hi;

I can access SqlServer 2000 fine, but not SqlServer 2005. My client is on Windows XP and SqlServer 2005 (dev version) is on Windows 2003. When I run I get:

Error: net.windward.datasource.DataSourceException: JdbcDataSource could not ope
n jdbc:sqlserver://T1-Databases;databaseName=AdventureWorks;integratedSecurity=t
rue;
net.windward.datasource.DataSourceException: net.windward.datasource.DataSourceE
xception: JdbcDataSource could not open jdbc:sqlserver://T1-Databases;databaseNa
me=AdventureWorks;integratedSecurity=true;
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1030)
at net.windward.xmlreport.RunReport.main(RunReport.java:165)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U
nknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour
ce)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1024)
... 1 more
Exception in thread "main" net.windward.datasource.DataSourceException: net.wind
ward.datasource.DataSourceException: JdbcDataSource could not open jdbc:sqlserve
r://T1-Databases;databaseName=AdventureWorks;integratedSecurity=true;
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1030)
at net.windward.xmlreport.RunReport.main(RunReport.java:165)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true
at
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U
nknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour
ce)
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav
a:1024)
... 1 more

Any ideas?

thanks - dave

Are you using Microsoft SQL Server 2005 JDBC Driver version 1.1?

What platform (OS and version) does your JDBC client run on?

|||

I have similar error:

java.lang.NoClassDefFoundError
at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)

I do have the JDBC driver version 1.1.

Cocoon 2.0

Tomcat 4.x

|||

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe
curity property value:true

It appears as though it has something to do with integratedSecurity. I think the connection string is case sensitive, you did spell it IntegratedSecurity="True" right? The exception thrown seems to be targetted to integratedSecurity specifically. Also, are you authenticating in mixed mode or windows only? Did you configure the server on install correctly to be able to authenticate the kind of connection you are trying to make?

Hope we can figure this one out together,

John

|||

Have you tried enabling the TCP/IP Protocol through the SQL Server Configuration Manager? I seem to recall it being turned off by default in SQL 2005. Enable it and restart the SQL Service.

Good luck,

-Tom

|||You can run SQL Profiler to check if your application is indeed trying to establish a connection or not.|||It looks like you are using the 1.0 dirver which did not support integrated auth property.

Cannot view SQL Server logs

Just installed SQL2005 on a clustered Windows server. Trying to view
the SQL Server logs from my client machine, but receive the following:
TITLE: Microsoft SQL Server Management Studio
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476[ /url]
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
A severe error occurred on the current command. The results, if any,
should be discarded. (Microsoft SQL Server, Error: 0)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .1399&EvtSrc=MSSQLServer&EvtID=0&LinkId=20476[/url]
BUTTONS:
OK
Everything else in the Management Studio works fine. Can anyone
interpret this?
I can't interpret or solve, but I can confirm that it also happens on our
clusters.

> Everything else in the Management Studio works fine. Can anyone
> interpret this?
>

Cannot view SQL Server logs

Just installed SQL2005 on a clustered Windows server. Trying to view
the SQL Server logs from my client machine, but receive the following:
TITLE: Microsoft SQL Server Management Studio
--
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
--
A severe error occurred on the current command. The results, if any,
should be discarded. (Microsoft SQL Server, Error: 0)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=0&LinkId=20476
--
BUTTONS:
OK
--
Everything else in the Management Studio works fine. Can anyone
interpret this?I can't interpret or solve, but I can confirm that it also happens on our
clusters.
> Everything else in the Management Studio works fine. Can anyone
> interpret this?
>|||Interesting...I found out that when I was trying to view the logs, for
some reason it was trying to direct me to the virtual servername used
by the Data Group of the cluster. I don't know why it would do that.
I created an alias for the data group name, and pointed it to the ip
address of the sql server instance, and it connects properly now.
Not sure if I explained this right, I'm kinda new to clusters, but
hopefully this will help you.
Aaron Bertrand [SQL Server MVP] wrote:
> I can't interpret or solve, but I can confirm that it also happens on our
> clusters.
>
>
> > Everything else in the Management Studio works fine. Can anyone
> > interpret this?
> >

Cannot view SQL Server logs

Just installed SQL2005 on a clustered Windows server. Trying to view
the SQL Server logs from my client machine, but receive the following:
TITLE: Microsoft SQL Server Management Studio
--
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click:
http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
A severe error occurred on the current command. The results, if any,
should be discarded. (Microsoft SQL Server, Error: 0)
For help, click:
http://go.microsoft.com/fwlink?Prod...=0&LinkId=20476
BUTTONS:
OK
--
Everything else in the Management Studio works fine. Can anyone
interpret this?I can't interpret or solve, but I can confirm that it also happens on our
clusters.

> Everything else in the Management Studio works fine. Can anyone
> interpret this?
>|||Interesting...I found out that when I was trying to view the logs, for
some reason it was trying to direct me to the virtual servername used
by the Data Group of the cluster. I don't know why it would do that.
I created an alias for the data group name, and pointed it to the ip
address of the sql server instance, and it connects properly now.
Not sure if I explained this right, I'm kinda new to clusters, but
hopefully this will help you.
Aaron Bertrand [SQL Server MVP] wrote:[vbcol=seagreen]
> I can't interpret or solve, but I can confirm that it also happens on our
> clusters.
>
>

Cannot use the OUTPUT option when passing a constant Stored Proced

I am having a very difficult problem.
I get the following error:
Microsoft SQL Native Client
Cannot use the OUTPUT option when passing a constant to a Stored Procedure
In SQL 2005 SP2, I check Profiler, here are my findings:
UserA (w/ Domain Admin rights in ADUC) - SQL Profiler reports that user exec
this sp as "dbo"
UserB (w/out Domain Admin rights in ADUC) - SQL Profiler reports that user
exec this sp as "DOMAIN\UserName"
If I change UserB to w/ Domain Admin rights in ADUC - SQL Profiler reports
that user exec this sp as "dbo".
What is going on? This started after updating SQL 2005 to SP2.
Thanks
StephenCan you tell us more about how exactly you are calling this sp? Can you
show the actual code?
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Stephen" <Stephen@.discussions.microsoft.com> wrote in message
news:C234429C-44A8-4400-BF3A-CF792F7EBF2A@.microsoft.com...
>I am having a very difficult problem.
> I get the following error:
> Microsoft SQL Native Client
> Cannot use the OUTPUT option when passing a constant to a Stored Procedure
> In SQL 2005 SP2, I check Profiler, here are my findings:
> UserA (w/ Domain Admin rights in ADUC) - SQL Profiler reports that user
> exec
> this sp as "dbo"
> UserB (w/out Domain Admin rights in ADUC) - SQL Profiler reports that user
> exec this sp as "DOMAIN\UserName"
> If I change UserB to w/ Domain Admin rights in ADUC - SQL Profiler reports
> that user exec this sp as "dbo".
> What is going on? This started after updating SQL 2005 to SP2.
> Thanks
> Stephen
>|||> Cannot use the OUTPUT option when passing a constant to a Stored Procedure
I can reproduce this error message with the following test script:
EXEC dbo.test 1 OUT
So it would seem that your application is doing something similar; a
constant cannot be passed as an output parameter.
> In SQL 2005 SP2, I check Profiler, here are my findings:
> UserA (w/ Domain Admin rights in ADUC) - SQL Profiler reports that user
> exec
> this sp as "dbo"
> UserB (w/out Domain Admin rights in ADUC) - SQL Profiler reports that user
> exec this sp as "DOMAIN\UserName"
> If I change UserB to w/ Domain Admin rights in ADUC - SQL Profiler reports
> that user exec this sp as "dbo".
> What is going on? This started after updating SQL 2005 to SP2.
I don't see how this information is related to the subject of this post but
this is expected behavior. Administrators are SQL Server sysadmin role
members by default and are therefore the "dbo" user in all databases.
Non-sysadmin role members access databases under their normal database user
security context.
--
Hope this helps.
Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/
"Stephen" <Stephen@.discussions.microsoft.com> wrote in message
news:C234429C-44A8-4400-BF3A-CF792F7EBF2A@.microsoft.com...
>I am having a very difficult problem.
> I get the following error:
> Microsoft SQL Native Client
> Cannot use the OUTPUT option when passing a constant to a Stored Procedure
> In SQL 2005 SP2, I check Profiler, here are my findings:
> UserA (w/ Domain Admin rights in ADUC) - SQL Profiler reports that user
> exec
> this sp as "dbo"
> UserB (w/out Domain Admin rights in ADUC) - SQL Profiler reports that user
> exec this sp as "DOMAIN\UserName"
> If I change UserB to w/ Domain Admin rights in ADUC - SQL Profiler reports
> that user exec this sp as "dbo".
> What is going on? This started after updating SQL 2005 to SP2.
> Thanks
> Stephen
>|||Yes, I will post it in about 2 hours.
Thanks
Stephen
"Andrew J. Kelly" wrote:
> Can you tell us more about how exactly you are calling this sp? Can you
> show the actual code?
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Stephen" <Stephen@.discussions.microsoft.com> wrote in message
> news:C234429C-44A8-4400-BF3A-CF792F7EBF2A@.microsoft.com...
> >I am having a very difficult problem.
> > I get the following error:
> > Microsoft SQL Native Client
> > Cannot use the OUTPUT option when passing a constant to a Stored Procedure
> >
> > In SQL 2005 SP2, I check Profiler, here are my findings:
> > UserA (w/ Domain Admin rights in ADUC) - SQL Profiler reports that user
> > exec
> > this sp as "dbo"
> > UserB (w/out Domain Admin rights in ADUC) - SQL Profiler reports that user
> > exec this sp as "DOMAIN\UserName"
> > If I change UserB to w/ Domain Admin rights in ADUC - SQL Profiler reports
> > that user exec this sp as "dbo".
> > What is going on? This started after updating SQL 2005 to SP2.
> > Thanks
> > Stephen
> >
>|||Dan, I am sorry but I don't understand your reply.
I listed the information because that is all I know about how I can get this
sp to work... by giving my ADUsers "Domain Admin" rights.
So is it an sp issue or a permission problem? Sorry for not understanding
your reply.
Here is the sp:
USE [Database]
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER PROCEDURE [dbo].[cf_data_info]
@.table_name varchar(128),
@.column_name varchar(128),
@.data_type varchar(128) OUTPUT,
@.colprecision integer OUTPUT,
@.colscale integer OUTPUT
AS
SELECT @.data_type = systypes.name,
@.colprecision = syscolumns.prec,
@.colscale = syscolumns.scale
FROM sysobjects
LEFT OUTER JOIN syscolumns
ON syscolumns.id = sysobjects.id
LEFT OUTER JOIN systypes
ON systypes.xusertype = syscolumns.xusertype
INNER JOIN sysusers
ON sysusers.uid = sysobjects.uid
AND Upper(sysusers.name) = 'DBO'
WHERE sysobjects.name = @.table_name
AND syscolumns.name = @.column_name
Everything worked fine before upgrading to SQL 2005 SP2.
Thanks
Stephen
"Dan Guzman" wrote:
> > Cannot use the OUTPUT option when passing a constant to a Stored Procedure
> I can reproduce this error message with the following test script:
> EXEC dbo.test 1 OUT
> So it would seem that your application is doing something similar; a
> constant cannot be passed as an output parameter.
> > In SQL 2005 SP2, I check Profiler, here are my findings:
> > UserA (w/ Domain Admin rights in ADUC) - SQL Profiler reports that user
> > exec
> > this sp as "dbo"
> > UserB (w/out Domain Admin rights in ADUC) - SQL Profiler reports that user
> > exec this sp as "DOMAIN\UserName"
> > If I change UserB to w/ Domain Admin rights in ADUC - SQL Profiler reports
> > that user exec this sp as "dbo".
> > What is going on? This started after updating SQL 2005 to SP2.
> I don't see how this information is related to the subject of this post but
> this is expected behavior. Administrators are SQL Server sysadmin role
> members by default and are therefore the "dbo" user in all databases.
> Non-sysadmin role members access databases under their normal database user
> security context.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> http://weblogs.sqlteam.com/dang/
> "Stephen" <Stephen@.discussions.microsoft.com> wrote in message
> news:C234429C-44A8-4400-BF3A-CF792F7EBF2A@.microsoft.com...
> >I am having a very difficult problem.
> > I get the following error:
> > Microsoft SQL Native Client
> > Cannot use the OUTPUT option when passing a constant to a Stored Procedure
> >
> > In SQL 2005 SP2, I check Profiler, here are my findings:
> > UserA (w/ Domain Admin rights in ADUC) - SQL Profiler reports that user
> > exec
> > this sp as "dbo"
> > UserB (w/out Domain Admin rights in ADUC) - SQL Profiler reports that user
> > exec this sp as "DOMAIN\UserName"
> > If I change UserB to w/ Domain Admin rights in ADUC - SQL Profiler reports
> > that user exec this sp as "dbo".
> > What is going on? This started after updating SQL 2005 to SP2.
> > Thanks
> > Stephen
> >
>|||> So is it an sp issue or a permission problem? Sorry for not understanding
> your reply.
I think you are getting this error because the actual call to this procedure
is not formed correctly. For example, the code below attempts to pass
literals as OUTPUT parameters:
DECLARE
@.data_type sysname,
@.colprecision int,
@.colscale int
EXEC [dbo].[cf_data_info]
@.table_name = 'MyTable',
@.column_name = 'MyColumn',
@.data_type = 'test' OUTPUT,
@.colprecision = 4 OUTPUT,
@.colscale = 2 OUTPUT
I can't explain how permissions might come into play here. Does the
profiler trace show the execute statement?
--
Hope this helps.
Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/
"Stephen" <Stephen@.discussions.microsoft.com> wrote in message
news:706C9BEF-9A37-4EBA-9FE2-7B58B5B781DA@.microsoft.com...
> Dan, I am sorry but I don't understand your reply.
> I listed the information because that is all I know about how I can get
> this
> sp to work... by giving my ADUsers "Domain Admin" rights.
> So is it an sp issue or a permission problem? Sorry for not understanding
> your reply.
> Here is the sp:
> USE [Database]
> GO
> SET ANSI_NULLS ON
> GO
> SET QUOTED_IDENTIFIER ON
> GO
>
> ALTER PROCEDURE [dbo].[cf_data_info]
> @.table_name varchar(128),
> @.column_name varchar(128),
> @.data_type varchar(128) OUTPUT,
> @.colprecision integer OUTPUT,
> @.colscale integer OUTPUT
> AS
> SELECT @.data_type = systypes.name,
> @.colprecision = syscolumns.prec,
> @.colscale = syscolumns.scale
> FROM sysobjects
> LEFT OUTER JOIN syscolumns
> ON syscolumns.id = sysobjects.id
> LEFT OUTER JOIN systypes
> ON systypes.xusertype = syscolumns.xusertype
> INNER JOIN sysusers
> ON sysusers.uid = sysobjects.uid
> AND Upper(sysusers.name) = 'DBO'
> WHERE sysobjects.name = @.table_name
> AND syscolumns.name = @.column_name
> Everything worked fine before upgrading to SQL 2005 SP2.
> Thanks
> Stephen
> "Dan Guzman" wrote:
>> > Cannot use the OUTPUT option when passing a constant to a Stored
>> > Procedure
>> I can reproduce this error message with the following test script:
>> EXEC dbo.test 1 OUT
>> So it would seem that your application is doing something similar; a
>> constant cannot be passed as an output parameter.
>> > In SQL 2005 SP2, I check Profiler, here are my findings:
>> > UserA (w/ Domain Admin rights in ADUC) - SQL Profiler reports that user
>> > exec
>> > this sp as "dbo"
>> > UserB (w/out Domain Admin rights in ADUC) - SQL Profiler reports that
>> > user
>> > exec this sp as "DOMAIN\UserName"
>> > If I change UserB to w/ Domain Admin rights in ADUC - SQL Profiler
>> > reports
>> > that user exec this sp as "dbo".
>> > What is going on? This started after updating SQL 2005 to SP2.
>> I don't see how this information is related to the subject of this post
>> but
>> this is expected behavior. Administrators are SQL Server sysadmin role
>> members by default and are therefore the "dbo" user in all databases.
>> Non-sysadmin role members access databases under their normal database
>> user
>> security context.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> http://weblogs.sqlteam.com/dang/
>> "Stephen" <Stephen@.discussions.microsoft.com> wrote in message
>> news:C234429C-44A8-4400-BF3A-CF792F7EBF2A@.microsoft.com...
>> >I am having a very difficult problem.
>> > I get the following error:
>> > Microsoft SQL Native Client
>> > Cannot use the OUTPUT option when passing a constant to a Stored
>> > Procedure
>> >
>> > In SQL 2005 SP2, I check Profiler, here are my findings:
>> > UserA (w/ Domain Admin rights in ADUC) - SQL Profiler reports that user
>> > exec
>> > this sp as "dbo"
>> > UserB (w/out Domain Admin rights in ADUC) - SQL Profiler reports that
>> > user
>> > exec this sp as "DOMAIN\UserName"
>> > If I change UserB to w/ Domain Admin rights in ADUC - SQL Profiler
>> > reports
>> > that user exec this sp as "dbo".
>> > What is going on? This started after updating SQL 2005 to SP2.
>> > Thanks
>> > Stephen
>> >|||The issue is that the reference to the output needs to be declared in the
execution.
The error is in your execute call "EXEC dbo.test 1 OUT"
Declare @.InAndOutParammeterName
Select @.InAndOutParammeterName=1
EXEC dbo.test @.InAndOutParammeterName OUT
@.InAndOutParammeterName now holds the reference in memory for the returned
value to reside.
"Stephen" <Stephen@.discussions.microsoft.com> wrote in message
news:706C9BEF-9A37-4EBA-9FE2-7B58B5B781DA@.microsoft.com...
> Dan, I am sorry but I don't understand your reply.
> I listed the information because that is all I know about how I can get
> this
> sp to work... by giving my ADUsers "Domain Admin" rights.
> So is it an sp issue or a permission problem? Sorry for not understanding
> your reply.
> Here is the sp:
> USE [Database]
> GO
> SET ANSI_NULLS ON
> GO
> SET QUOTED_IDENTIFIER ON
> GO
>
> ALTER PROCEDURE [dbo].[cf_data_info]
> @.table_name varchar(128),
> @.column_name varchar(128),
> @.data_type varchar(128) OUTPUT,
> @.colprecision integer OUTPUT,
> @.colscale integer OUTPUT
> AS
> SELECT @.data_type = systypes.name,
> @.colprecision = syscolumns.prec,
> @.colscale = syscolumns.scale
> FROM sysobjects
> LEFT OUTER JOIN syscolumns
> ON syscolumns.id = sysobjects.id
> LEFT OUTER JOIN systypes
> ON systypes.xusertype = syscolumns.xusertype
> INNER JOIN sysusers
> ON sysusers.uid = sysobjects.uid
> AND Upper(sysusers.name) = 'DBO'
> WHERE sysobjects.name = @.table_name
> AND syscolumns.name = @.column_name
> Everything worked fine before upgrading to SQL 2005 SP2.
> Thanks
> Stephen
> "Dan Guzman" wrote:
>> > Cannot use the OUTPUT option when passing a constant to a Stored
>> > Procedure
>> I can reproduce this error message with the following test script:
>> EXEC dbo.test 1 OUT
>> So it would seem that your application is doing something similar; a
>> constant cannot be passed as an output parameter.
>> > In SQL 2005 SP2, I check Profiler, here are my findings:
>> > UserA (w/ Domain Admin rights in ADUC) - SQL Profiler reports that user
>> > exec
>> > this sp as "dbo"
>> > UserB (w/out Domain Admin rights in ADUC) - SQL Profiler reports that
>> > user
>> > exec this sp as "DOMAIN\UserName"
>> > If I change UserB to w/ Domain Admin rights in ADUC - SQL Profiler
>> > reports
>> > that user exec this sp as "dbo".
>> > What is going on? This started after updating SQL 2005 to SP2.
>> I don't see how this information is related to the subject of this post
>> but
>> this is expected behavior. Administrators are SQL Server sysadmin role
>> members by default and are therefore the "dbo" user in all databases.
>> Non-sysadmin role members access databases under their normal database
>> user
>> security context.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> http://weblogs.sqlteam.com/dang/
>> "Stephen" <Stephen@.discussions.microsoft.com> wrote in message
>> news:C234429C-44A8-4400-BF3A-CF792F7EBF2A@.microsoft.com...
>> >I am having a very difficult problem.
>> > I get the following error:
>> > Microsoft SQL Native Client
>> > Cannot use the OUTPUT option when passing a constant to a Stored
>> > Procedure
>> >
>> > In SQL 2005 SP2, I check Profiler, here are my findings:
>> > UserA (w/ Domain Admin rights in ADUC) - SQL Profiler reports that user
>> > exec
>> > this sp as "dbo"
>> > UserB (w/out Domain Admin rights in ADUC) - SQL Profiler reports that
>> > user
>> > exec this sp as "DOMAIN\UserName"
>> > If I change UserB to w/ Domain Admin rights in ADUC - SQL Profiler
>> > reports
>> > that user exec this sp as "dbo".
>> > What is going on? This started after updating SQL 2005 to SP2.
>> > Thanks
>> > Stephen
>> >

Cannot use TCP of SQL Server Client.

Our IIS Webserver and SQL server 2000 installed into two
machine and separate by a firewall.
Recently, I need to disable name-pipe protocol in our SQL
client of webserver. But the TCP/IP not work, even I
opened the port 1433 of this.
I've a test that I release all port for that and set the
client network setting to use TCP IP only. It still not
work.
Please help.
(P.S: if I added Name-pipe in network config. of client,
it request port 445 & 139 on the firewall. Is it correct
response? I afraid we are under attack)Things to test.
1. Can you make a tcp socket connection to the server inside the firewall?
Test with ISQL.
ISQL -Stcp:ServerNameHere -Uuser -Ppassword -Q"select @.@.version"
If it fails, search on the OS error returned.
Example:
10060 is connection timeout
10061 is the server is not listening on the socket.
11001 host not found
If it works inside the firewall, try the same on the machine outside the
firewall.
Check the firewall logs.
Or make simultaneous network traces on both the client and server when
running the ISQL command above.
Hope this helps.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Cannot uninstall reporting services

Hi,
I am trying to install reporting services client tools onto my desktop PC.
It appears that reporting services enterprise edition have been installed on
here before but there is nothing listed in add/remove programs for RS.
An excerpt of the install log is below, I am not sure what is setting the
paths for the reporting services databases to be on "d:\program files" as
this is not on my PC. I have searched through the registry with no joy.
Can anyone tell me how I can completely remove RS and start again? Oh yes
and I have checked for the COM objects prescence on my PC too and there are
not there.
Thanks in advance for your help,
Nick
-- excerpt from installation log
Property(C): DataBases.3882F579_1BCB_4C44_991C_060D38C9C09D = D:\Program
Files\Microsoft SQL Server\MSSQL\Reporting Services\Samples\Databases\
Property(C): SamplesDB1 = AdventureWorks2000
Property(C): CostingComplete = 1
Property(C): OutOfDiskSpace = 0
Property(C): OutOfNoRbDiskSpace = 0
Property(C): PrimaryVolumeSpaceAvailable = 0
Property(C): PrimaryVolumeSpaceRequired = 0
Property(C): PrimaryVolumeSpaceRemaining = 0
Property(C): _FeatDescription = Report Server
Property(C): _DefaultInstance = Installed
Property(C): SQL_SHOWLIC = 1
Property(C): RSAutoStart = 1
Property(C): _Service = RS
Property(C): Asp_Net_Accout_For_GUI_Display = URSUS\ASPNET
Property(C): WizardDialog = StartCopyDlg
Property(C): DisableBack = MaintenanceDlg
Property(C): SqlMaintType = 1
=== Logging stopped: 28/02/2006 15:11:48 === MSI (c) (30:20) [15:11:48:982]: Note: 1: 1729
MSI (c) (30:20) [15:11:48:982]: Product: Microsoft SQL Server 2000 Reporting
Services Enterprise Edition -- Configuration failed.
MSI (c) (30:20) [15:11:48:992]: Grabbed execution mutex.
MSI (c) (30:20) [15:11:48:992]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (30:20) [15:11:48:992]: MainEngineThread is returning 1603
=== Verbose logging stopped: 28/02/2006 15:11:48 ===Hi,
replying to my own post!!
I actually eventually found some rogue entries in the registry with the help
of "regmon". There were alittle obscure, well that's my excuse and I'm
sticking to it!
Nick
"Nick Long" wrote:
> Hi,
> I am trying to install reporting services client tools onto my desktop PC.
> It appears that reporting services enterprise edition have been installed on
> here before but there is nothing listed in add/remove programs for RS.
> An excerpt of the install log is below, I am not sure what is setting the
> paths for the reporting services databases to be on "d:\program files" as
> this is not on my PC. I have searched through the registry with no joy.
> Can anyone tell me how I can completely remove RS and start again? Oh yes
> and I have checked for the COM objects prescence on my PC too and there are
> not there.
> Thanks in advance for your help,
> Nick
> -- excerpt from installation log
> Property(C): DataBases.3882F579_1BCB_4C44_991C_060D38C9C09D = D:\Program
> Files\Microsoft SQL Server\MSSQL\Reporting Services\Samples\Databases\
> Property(C): SamplesDB1 = AdventureWorks2000
> Property(C): CostingComplete = 1
> Property(C): OutOfDiskSpace = 0
> Property(C): OutOfNoRbDiskSpace = 0
> Property(C): PrimaryVolumeSpaceAvailable = 0
> Property(C): PrimaryVolumeSpaceRequired = 0
> Property(C): PrimaryVolumeSpaceRemaining = 0
> Property(C): _FeatDescription = Report Server
> Property(C): _DefaultInstance = Installed
> Property(C): SQL_SHOWLIC = 1
> Property(C): RSAutoStart = 1
> Property(C): _Service = RS
> Property(C): Asp_Net_Accout_For_GUI_Display = URSUS\ASPNET
> Property(C): WizardDialog = StartCopyDlg
> Property(C): DisableBack = MaintenanceDlg
> Property(C): SqlMaintType = 1
> === Logging stopped: 28/02/2006 15:11:48 ===> MSI (c) (30:20) [15:11:48:982]: Note: 1: 1729
> MSI (c) (30:20) [15:11:48:982]: Product: Microsoft SQL Server 2000 Reporting
> Services Enterprise Edition -- Configuration failed.
> MSI (c) (30:20) [15:11:48:992]: Grabbed execution mutex.
> MSI (c) (30:20) [15:11:48:992]: Cleaning up uninstalled install packages, if
> any exist
> MSI (c) (30:20) [15:11:48:992]: MainEngineThread is returning 1603
> === Verbose logging stopped: 28/02/2006 15:11:48 ===>|||If you're re-installing all of SQLServer, make sure you delete all the
MSSQL folders.
For RS, you may want to check and confirm that everything is gone out
of IIS as well.
Jim

Cannot start SQL Trace (Profiler) on Windows 2000 Professional

Hello all!
I have installed SQL Server 7 Client components on a Windows 2000
Professional machine.
I can start the Query analyzer and I can use it to connect to servers.
However, when I try to start SQL trace, I am getting the following
error message
"sqltrace.exe, not a valid win32 application."
Have any of you come across this problem? Please suggest a solution.
If you need any more information, please let me know.
Thank you,
Martin.
The file could have been corrupted. Have you checked your disk to see if
there are any errors?
You may be able to fix it by reinstalling the client utilities, if that is
not a problem.
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Martin Thomas" <martintms99@.yahoo.com> wrote in message
news:752207f2.0408090315.1eb0d689@.posting.google.c om...
> Hello all!
> I have installed SQL Server 7 Client components on a Windows 2000
> Professional machine.
> I can start the Query analyzer and I can use it to connect to servers.
> However, when I try to start SQL trace, I am getting the following
> error message
> "sqltrace.exe, not a valid win32 application."
> Have any of you come across this problem? Please suggest a solution.
> If you need any more information, please let me know.
> Thank you,
> Martin.

cannot run DTS Package from SQL Query Analyzer

I attemped to run dts package to transform data from AS400/DB2 by using Client Access ODBC ( Ms Windows 2000 Server, Ms SQL 2K, Client Access Driver 4.5)

but the result of testing has messed me up

because when i used this command via SQL Query Analyzer

exec master..xp_cmdshell 'DTSRun /S "MySVR" /U "sa" /N "dtsTEST" /G "{482209FD-0891-11D8-868C-00E0299B4BCF}" /A "G1":"8"="200310" /W "0"'

but it doesn't work

I wonder why.. because it can be executed in MS-Dos prompt successfully.
if I type

DTSRun /S "MySVR" /U "sa" /N "dtsTEST" /G "{482209FD-0891-11D8-868C-00E0299B4BCF}" /A "G1":"8"="200310" /W "0"

in the command line.

If somebody know please give me some advice (urgently!!).What is the error?

When run from dos it will be run on your client m/c. When from query analyser on the server using the sql server service account (probably)

Try logging on to the server as the sql server service account and running it in the designer and see what happens.|||I didn't run dos-command on Client M/C, I tested on Server M/C itself
and it success.

But when I tried to run by query analyzer, it takes much time (> 20 min and nothing happens) for executing and there was no error show on the screen. so I had to kill the process because it seemed not work .
And this process I tested on Server M/C also, by using Sql Admin (sa).

How could I solve this problem?|||It can be run properly in DTS Designer, but cannot run in Query analyzer.|||Does it have any user interaction - have you left in a debug msgbox?

I meant the account that the sql server service uses to logon - see services.
Maybe it needs access to something that this account doesn't have permission on.|||I checked already that the log on user-id has full permission, and the sign on user name and password for AS400 has been specify in DSN that use via client access express driver by setting the sign on information as 'use windows user name and password, no promping'.

If this problem is related to the security of sql server, why it can be run in DTS Designer(which has no pop up message box for user interface) with no popup error message and the result of transformation is correct.|||Because dts is a client application.
When you run it from query analyser the client is the server which gives it a different environment.

If you have already run it from the sql server service account then that limits the things that can be wrong.
Try turning on logging to see if any steps are run and what the error is.|||why i can run DTS Package in query analyzer if i change the source of DTS to be MsAccess file, on the server m/c not client. run in command line, no problem also.

why i cannot run in query analyzer if i specified source DSN as AS400/DB2, but run properly in command line by using same script.