datasource connection error

have developed a report on a test windows server machine in SSRS 2005 which
I can access from i./e. http://localhost/reports
DataSourcce is accessed using a sql login
My colleague on his machine can not access. His error is:
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'MarketAnalytics'.
(rsErrorOpeningConnection)
For more information about this error navigate to the report server on the
local server machine, or enable remote errorsCheck the SRS error logs they should have a better error for you. They can be
found in: C:\Program Files\Microsoft SQL Server\MSSQL.#\Reporting
Services\LogFiles.
--
SQL Server Developer Support Engineer
"arkiboys2" wrote:
> have developed a report on a test windows server machine in SSRS 2005 which
> I can access from i./e. http://localhost/reports
> DataSourcce is accessed using a sql login
> My colleague on his machine can not access. His error is:
> An error has occurred during report processing. (rsProcessingAborted)
> Cannot create a connection to data source 'MarketAnalytics'.
> (rsErrorOpeningConnection)
> For more information about this error navigate to the report server on the
> local server machine, or enable remote errors
>

Datasource = SQL 2000 sp2 (Cross-Database-Ownership Chaining?)

We have a report in RS 2005, data source uses Windows Integrated Security,
Initial Catalog is the database where the stored procedure is. The stored
procedure selects data from a different database on the server. This server
is running SQL Server 200 sp2 (so pre-Cross-Database-Ownership Chaining
option). The users can execute the stored procedure fine so it does not seem
to be a permissions issue to the data. The Report runs fine FROM the Report
Server. But, if I try to run the report from a different machine, I get:
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DataSourceNameIsHere'.
(rsErrorOpeningConnection)
For more information about this error navigate to the report server on the
local server machine, or enable remote errors
The report also runs fine if we don't use Windows Integrated Security. The
report runs fine if the datasource (both databases) are on SQL2000 sp3. Is
there anything that we can do to get this working on SQL2000 sp2? I'm not
sure that all systems on this server are supported on sp3 (3a or 4). It hosts
several databases from purchased products.I found this in the Reporting Services Log:
ERROR: Throwing
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'DataSourceNameIsHere'., ;
Info:
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Cannot create a connection to data source 'DataSourceNameIsHere'. -->
System.Data.SqlClient.SqlException: Login failed for user 'NT
AUTHORITY\ANONYMOUS LOGON'.
Michelle
"Michelle" wrote:
> We have a report in RS 2005, data source uses Windows Integrated Security,
> Initial Catalog is the database where the stored procedure is. The stored
> procedure selects data from a different database on the server. This server
> is running SQL Server 200 sp2 (so pre-Cross-Database-Ownership Chaining
> option). The users can execute the stored procedure fine so it does not seem
> to be a permissions issue to the data. The Report runs fine FROM the Report
> Server. But, if I try to run the report from a different machine, I get:
> An error has occurred during report processing. (rsProcessingAborted)
> Cannot create a connection to data source 'DataSourceNameIsHere'.
> (rsErrorOpeningConnection)
> For more information about this error navigate to the report server on the
> local server machine, or enable remote errors
> The report also runs fine if we don't use Windows Integrated Security. The
> report runs fine if the datasource (both databases) are on SQL2000 sp3. Is
> there anything that we can do to get this working on SQL2000 sp2? I'm not
> sure that all systems on this server are supported on sp3 (3a or 4). It hosts
> several databases from purchased products.sql

Datasource = SQL 2000 sp2 (Cross-Database-Ownership Chaining?)

We have a report in RS 2005, data source uses Windows Integrated

Security, Initial Catalog is the database where the stored procedure

is. The stored procedure selects data from a different database on the

server. This server is running SQL Server 200 sp2 (so

pre-Cross-Database-Ownership Chaining option). The users can execute

the stored procedure fine so it does not seem to be a permissions issue

to the data. The Report runs fine FROM the Report Server. But, if I try

to run the report from a different machine, I get:

An error has occurred during report processing. (rsProcessingAborted)

Cannot create a connection to data source 'DataSourceNameIsHere'. (rsErrorOpeningConnection)

For more information about this error navigate to the report server on the local server machine, or enable remote errors

The report also runs fine if we don't use Windows Integrated Security.

The report runs fine if the datasource (both databases) are on SQL2000

sp3. Is there anything that we can do to get this working on SQL2000

sp2? I'm not sure that all systems on this server are supported on sp3

(3a or 4). It hosts several databases from purchased products.I found this in the Reporting Services Log:

ERROR: Throwing

Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:

Cannot create a connection to data source 'DataSourceNameIsHere'., ;

Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'DataSourceNameIsHere'. > System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

Michelle

Datasource = SQL 2000 sp2 (Cross-Database-Ownership Chaining?)

We have a report in RS 2005, data source uses Windows Integrated

Security, Initial Catalog is the database where the stored procedure

is. The stored procedure selects data from a different database on the

server. This server is running SQL Server 200 sp2 (so

pre-Cross-Database-Ownership Chaining option). The users can execute

the stored procedure fine so it does not seem to be a permissions issue

to the data. The Report runs fine FROM the Report Server. But, if I try

to run the report from a different machine, I get:

An error has occurred during report processing. (rsProcessingAborted)

Cannot create a connection to data source 'DataSourceNameIsHere'. (rsErrorOpeningConnection)

For more information about this error navigate to the report server on the local server machine, or enable remote errors

The report also runs fine if we don't use Windows Integrated Security.

The report runs fine if the datasource (both databases) are on SQL2000

sp3. Is there anything that we can do to get this working on SQL2000

sp2? I'm not sure that all systems on this server are supported on sp3

(3a or 4). It hosts several databases from purchased products.I found this in the Reporting Services Log:

ERROR: Throwing

Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:

Cannot create a connection to data source 'DataSourceNameIsHere'., ;

Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source 'DataSourceNameIsHere'. > System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

Michelle

Datafile From Non-Windows Server

Can SQL Server 2000 import a flat data file directly from a mainframe
or other server that is not a Windows server or does the data file
need to be moved to a Windows server first?
Jerry
On Fri, 10 Aug 2007 18:18:01 -0000, Jerry <jerryalan@.gmail.com> wrote:

>Can SQL Server 2000 import a flat data file directly from a mainframe
>or other server that is not a Windows server or does the data file
>need to be moved to a Windows server first?
The first issue is whether the file can be "seen" and accessed. I
have seen AS/400 setups where that system had part of the disk visible
over the network so that a Windows box could access the files like any
other network drive. If the file is visible in that way something
should be possible. However I generally used a transfer utility
rather than a shared directory.
The next issue is whether the file is in a useable format. All the
files I ever loaded from a mainframe started on the mainframe end as
readable text, with no binary, float, packed, or zoned decimal fields,
likewise no "overpunch" where the sign is carried in half a byte. Then
it was a matter of using a transfer tool tool that converted IBM's
mainframe character set, EBCDIC, to the ASCII used by the rest of the
world.
A final aternative would be a driver that allowed ODBC or equivelent
access to mainframe data.
Roy Harvey
Beacon Falls, CT
|||In addition, the best approach here is to define your process:
1) dump the flat-file from the AS400 to a Windows machine or an FTP site
2) Use DTS to do ETL - there is a File Transfer Protocol Task if you intend
to read from an FTP site or a Text File Source if you intend to dump the
file on a Windows machine
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:s1gpb3prd16altj63k5qatvicte8vd2im7@.4ax.com...
> On Fri, 10 Aug 2007 18:18:01 -0000, Jerry <jerryalan@.gmail.com> wrote:
>
> The first issue is whether the file can be "seen" and accessed. I
> have seen AS/400 setups where that system had part of the disk visible
> over the network so that a Windows box could access the files like any
> other network drive. If the file is visible in that way something
> should be possible. However I generally used a transfer utility
> rather than a shared directory.
> The next issue is whether the file is in a useable format. All the
> files I ever loaded from a mainframe started on the mainframe end as
> readable text, with no binary, float, packed, or zoned decimal fields,
> likewise no "overpunch" where the sign is carried in half a byte. Then
> it was a matter of using a transfer tool tool that converted IBM's
> mainframe character set, EBCDIC, to the ASCII used by the rest of the
> world.
> A final aternative would be a driver that allowed ODBC or equivelent
> access to mainframe data.
> Roy Harvey
> Beacon Falls, CT

Datafile From Non-Windows Server

Can SQL Server 2000 import a flat data file directly from a mainframe
or other server that is not a Windows server or does the data file
need to be moved to a Windows server first?
--
JerryOn Fri, 10 Aug 2007 18:18:01 -0000, Jerry <jerryalan@.gmail.com> wrote:
>Can SQL Server 2000 import a flat data file directly from a mainframe
>or other server that is not a Windows server or does the data file
>need to be moved to a Windows server first?
The first issue is whether the file can be "seen" and accessed. I
have seen AS/400 setups where that system had part of the disk visible
over the network so that a Windows box could access the files like any
other network drive. If the file is visible in that way something
should be possible. However I generally used a transfer utility
rather than a shared directory.
The next issue is whether the file is in a useable format. All the
files I ever loaded from a mainframe started on the mainframe end as
readable text, with no binary, float, packed, or zoned decimal fields,
likewise no "overpunch" where the sign is carried in half a byte. Then
it was a matter of using a transfer tool tool that converted IBM's
mainframe character set, EBCDIC, to the ASCII used by the rest of the
world.
A final aternative would be a driver that allowed ODBC or equivelent
access to mainframe data.
Roy Harvey
Beacon Falls, CT|||In addition, the best approach here is to define your process:
1) dump the flat-file from the AS400 to a Windows machine or an FTP site
2) Use DTS to do ETL - there is a File Transfer Protocol Task if you intend
to read from an FTP site or a Text File Source if you intend to dump the
file on a Windows machine
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:s1gpb3prd16altj63k5qatvicte8vd2im7@.4ax.com...
> On Fri, 10 Aug 2007 18:18:01 -0000, Jerry <jerryalan@.gmail.com> wrote:
>>Can SQL Server 2000 import a flat data file directly from a mainframe
>>or other server that is not a Windows server or does the data file
>>need to be moved to a Windows server first?
> The first issue is whether the file can be "seen" and accessed. I
> have seen AS/400 setups where that system had part of the disk visible
> over the network so that a Windows box could access the files like any
> other network drive. If the file is visible in that way something
> should be possible. However I generally used a transfer utility
> rather than a shared directory.
> The next issue is whether the file is in a useable format. All the
> files I ever loaded from a mainframe started on the mainframe end as
> readable text, with no binary, float, packed, or zoned decimal fields,
> likewise no "overpunch" where the sign is carried in half a byte. Then
> it was a matter of using a transfer tool tool that converted IBM's
> mainframe character set, EBCDIC, to the ASCII used by the rest of the
> world.
> A final aternative would be a driver that allowed ODBC or equivelent
> access to mainframe data.
> Roy Harvey
> Beacon Falls, CT

Datafile From Non-Windows Server

Can SQL Server 2000 import a flat data file directly from a mainframe
or other server that is not a Windows server or does the data file
need to be moved to a Windows server first?
JerryOn Fri, 10 Aug 2007 18:18:01 -0000, Jerry <jerryalan@.gmail.com> wrote:

>Can SQL Server 2000 import a flat data file directly from a mainframe
>or other server that is not a Windows server or does the data file
>need to be moved to a Windows server first?
The first issue is whether the file can be "seen" and accessed. I
have seen AS/400 setups where that system had part of the disk visible
over the network so that a Windows box could access the files like any
other network drive. If the file is visible in that way something
should be possible. However I generally used a transfer utility
rather than a shared directory.
The next issue is whether the file is in a useable format. All the
files I ever loaded from a mainframe started on the mainframe end as
readable text, with no binary, float, packed, or zoned decimal fields,
likewise no "overpunch" where the sign is carried in half a byte. Then
it was a matter of using a transfer tool tool that converted IBM's
mainframe character set, EBCDIC, to the ASCII used by the rest of the
world.
A final aternative would be a driver that allowed ODBC or equivelent
access to mainframe data.
Roy Harvey
Beacon Falls, CT|||In addition, the best approach here is to define your process:
1) dump the flat-file from the AS400 to a Windows machine or an FTP site
2) Use DTS to do ETL - there is a File Transfer Protocol Task if you intend
to read from an FTP site or a Text File Source if you intend to dump the
file on a Windows machine
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:s1gpb3prd16altj63k5qatvicte8vd2im7@.
4ax.com...
> On Fri, 10 Aug 2007 18:18:01 -0000, Jerry <jerryalan@.gmail.com> wrote:
>
> The first issue is whether the file can be "seen" and accessed. I
> have seen AS/400 setups where that system had part of the disk visible
> over the network so that a Windows box could access the files like any
> other network drive. If the file is visible in that way something
> should be possible. However I generally used a transfer utility
> rather than a shared directory.
> The next issue is whether the file is in a useable format. All the
> files I ever loaded from a mainframe started on the mainframe end as
> readable text, with no binary, float, packed, or zoned decimal fields,
> likewise no "overpunch" where the sign is carried in half a byte. Then
> it was a matter of using a transfer tool tool that converted IBM's
> mainframe character set, EBCDIC, to the ASCII used by the rest of the
> world.
> A final aternative would be a driver that allowed ODBC or equivelent
> access to mainframe data.
> Roy Harvey
> Beacon Falls, CT

Data-driven subscription error

I'm using Windows 2003 server with Sql server 2005 June CTP. When I create a data-driven subscription for a report everything works fine, the query that gets the subscribers from a database is validated successfully. The subscription is time triggered, but when it should start and deliver the reports I get a logon failure error. I use credentials stored securely in the report server. I tried it with sa account and it still doesn't work. When I try to edit the subscription I can see there is blank space where the password should be, is this just to prevent abuse or because it just doesn't store the password? Could someone please tell me what am I doing wrong, thanks.
I believe the problem was that the report server didn't want to store my execution account, still not sure why...

databse properties causes mmc to close

Please help,
I am running SQL Server 2000 on a Windows 2000 server.
Whenever I open the Enterprise Manager and I right-click on any database and
select properties, the entire console just closes. No error or alert is cre
ated.
What should I doHave a look at Event log and see if there's anything there. Also, be sure to
update your sqlserver with latest service pack (sp3a).
-oj
http://www.rac4sql.net
"john" <anonymous@.discussions.microsoft.com> wrote in message
news:4BEAD47A-C47B-47ED-83EA-6AC9E00BE098@.microsoft.com...
> Please help,
> I am running SQL Server 2000 on a Windows 2000 server.
> Whenever I open the Enterprise Manager and I right-click on any database
and select properties, the entire console just closes. No error or alert is
created.
> What should I do|||I have SP3 loaded and I've checked the event logs but there is nothing regar
ding SQL.

Databse Link will not connect

I have a couple new servers - Windows 2003 R2 - with SQL Server 2000
SP4 installed. They are all Active/Active clustered instances (my
first ones).

I am trying to create database links to other SQL Server instances, but
there are 3 that I cannot connect to.

The dblink works if I connect to the instance as "sa", but not as my
Windows Authenticated account. We use Active Directory and I am in the
Administrator group on all of the boxes.

Of the 3 I can't get to, 1 is a cluster (Active/Passive) and the other
2 are just regular Enterprise instances. They are all SQL 2000 SP4.

I have several other instances, all SP4 on 2003 boxes and I can connect
to all of them.

Also, on the instances where the dblink does not work, I can actually
connect to these databases w/in Enterprise Manager successfully.

I am using a different port for the instances, but I have set them up
in the Client Network Utility as well and still can't connect.

I can connect via a dblink TO these new instances from the older boxes
fine.

I'm really stumped - I've had the Network people verify we don't have a
firewall issue or something.

Must be some sort of permissions problem, but I don't know what else to
check - - -

Please help!!

THANK YOU!!Not completely sure what you mean by a dblink, but what SQL permissions
do the Administrators have on each server? Are you sure the
BUILTIN/Administrators Windows group have the appropriate permissions
on the databases you want to select from?

Stu

traceable1 wrote:

Quote:

Originally Posted by

I have a couple new servers - Windows 2003 R2 - with SQL Server 2000
SP4 installed. They are all Active/Active clustered instances (my
first ones).
>
I am trying to create database links to other SQL Server instances, but
there are 3 that I cannot connect to.
>
The dblink works if I connect to the instance as "sa", but not as my
Windows Authenticated account. We use Active Directory and I am in the
Administrator group on all of the boxes.
>
Of the 3 I can't get to, 1 is a cluster (Active/Passive) and the other
2 are just regular Enterprise instances. They are all SQL 2000 SP4.
>
I have several other instances, all SP4 on 2003 boxes and I can connect
to all of them.
>
Also, on the instances where the dblink does not work, I can actually
connect to these databases w/in Enterprise Manager successfully.
>
I am using a different port for the instances, but I have set them up
in the Client Network Utility as well and still can't connect.
>
I can connect via a dblink TO these new instances from the older boxes
fine.
>
I'm really stumped - I've had the Network people verify we don't have a
firewall issue or something.
>
Must be some sort of permissions problem, but I don't know what else to
check - - -
>
Please help!!
>
THANK YOU!!

|||Thank you!

By dblink I am referring to a linked server. (I apologize - I come
from an Oracle background).

The BUILTIN/Administrators group has all of the System Roles and it
still did not work.
Other boxes have links into the server/instance which work fine, and
the new server can link to other servers.
It's strange because it's just this one combination that does not work.

Group A: oldest servers; non-clustered; Win 2003 SP1

Group B: medium servers; 1 a/p cluster; 2 non-clustered; Win 2003 SP1

Group C: newest servers; 3 a/a clusters; Win 2003 R2

All SQL Server 2000 SP4

Group A can link to Group B
Group A can link to Group C
Group B can link to Group A
Group B can link to Group C
Group C can link to Group A
Group C CANNOT link to Group A if logged in using Windows
Authentication

All of the links are set up using "sa".

Stu wrote:

Quote:

Originally Posted by

Not completely sure what you mean by a dblink, but what SQL permissions
do the Administrators have on each server? Are you sure the
BUILTIN/Administrators Windows group have the appropriate permissions
on the databases you want to select from?
>
Stu
>
>
traceable1 wrote:

Quote:

Originally Posted by

I have a couple new servers - Windows 2003 R2 - with SQL Server 2000
SP4 installed. They are all Active/Active clustered instances (my
first ones).

I am trying to create database links to other SQL Server instances, but
there are 3 that I cannot connect to.

The dblink works if I connect to the instance as "sa", but not as my
Windows Authenticated account. We use Active Directory and I am in the
Administrator group on all of the boxes.

Of the 3 I can't get to, 1 is a cluster (Active/Passive) and the other
2 are just regular Enterprise instances. They are all SQL 2000 SP4.

I have several other instances, all SP4 on 2003 boxes and I can connect
to all of them.

Also, on the instances where the dblink does not work, I can actually
connect to these databases w/in Enterprise Manager successfully.

I am using a different port for the instances, but I have set them up
in the Client Network Utility as well and still can't connect.

I can connect via a dblink TO these new instances from the older boxes
fine.

I'm really stumped - I've had the Network people verify we don't have a
firewall issue or something.

Must be some sort of permissions problem, but I don't know what else to
check - - -

Please help!!

THANK YOU!!

|||You may want to google "double-hop" and SQL Server; I'm not sure that I
understand your scenario, but a few articles might ring true.

HTH,
Stu

traceable1 wrote:

Quote:

Originally Posted by

Thank you!
>
By dblink I am referring to a linked server. (I apologize - I come
from an Oracle background).
>
The BUILTIN/Administrators group has all of the System Roles and it
still did not work.
Other boxes have links into the server/instance which work fine, and
the new server can link to other servers.
It's strange because it's just this one combination that does not work.
>
>
Group A: oldest servers; non-clustered; Win 2003 SP1
>
Group B: medium servers; 1 a/p cluster; 2 non-clustered; Win 2003 SP1
>
Group C: newest servers; 3 a/a clusters; Win 2003 R2
>
All SQL Server 2000 SP4
>
Group A can link to Group B
Group A can link to Group C
Group B can link to Group A
Group B can link to Group C
Group C can link to Group A
Group C CANNOT link to Group A if logged in using Windows
Authentication
>
All of the links are set up using "sa".
>
>
>
>
>
>
Stu wrote:

Quote:

Originally Posted by

Not completely sure what you mean by a dblink, but what SQL permissions
do the Administrators have on each server? Are you sure the
BUILTIN/Administrators Windows group have the appropriate permissions
on the databases you want to select from?

Stu

traceable1 wrote:

Quote:

Originally Posted by

I have a couple new servers - Windows 2003 R2 - with SQL Server 2000
SP4 installed. They are all Active/Active clustered instances (my
first ones).
>
I am trying to create database links to other SQL Server instances, but
there are 3 that I cannot connect to.
>
The dblink works if I connect to the instance as "sa", but not as my
Windows Authenticated account. We use Active Directory and I am in the
Administrator group on all of the boxes.
>
Of the 3 I can't get to, 1 is a cluster (Active/Passive) and the other
2 are just regular Enterprise instances. They are all SQL 2000 SP4.
>
I have several other instances, all SP4 on 2003 boxes and I can connect
to all of them.
>
Also, on the instances where the dblink does not work, I can actually
connect to these databases w/in Enterprise Manager successfully.
>
I am using a different port for the instances, but I have set them up
in the Client Network Utility as well and still can't connect.
>
I can connect via a dblink TO these new instances from the older boxes
fine.
>
I'm really stumped - I've had the Network people verify we don't have a
firewall issue or something.
>
Must be some sort of permissions problem, but I don't know what else to
check - - -
>
Please help!!
>
THANK YOU!!

|||Thanks -

we're not double-hopping.

If you go to Enterprise Manager, under Security there is "Linked
Servers".

If I am on one of the boxes in Group C, I am unable to open the link to
any of the instances in Group B if I am logged into the instance using
Windows Authentication. (Sorry I had a typo in the last message).

I've recently discovered that if I change the port back to 1433, the
database link will work. However, I am uncomfortable going back to the
default port.
All of my other links work fine.

Also, the servers in Group C are using 64-bit Windows (but 32-bit SQL).

thanks,
tc

Stu wrote:

Quote:

Originally Posted by

You may want to google "double-hop" and SQL Server; I'm not sure that I
understand your scenario, but a few articles might ring true.
>
HTH,
Stu
>
>
traceable1 wrote:

Quote:

Originally Posted by

Thank you!

By dblink I am referring to a linked server. (I apologize - I come
from an Oracle background).

The BUILTIN/Administrators group has all of the System Roles and it
still did not work.
Other boxes have links into the server/instance which work fine, and
the new server can link to other servers.
It's strange because it's just this one combination that does not work.

Group A: oldest servers; non-clustered; Win 2003 SP1

Group B: medium servers; 1 a/p cluster; 2 non-clustered; Win 2003 SP1

Group C: newest servers; 3 a/a clusters; Win 2003 R2

All SQL Server 2000 SP4

Group A can link to Group B
Group A can link to Group C
Group B can link to Group A
Group B can link to Group C
Group C can link to Group A
Group C CANNOT link to Group A if logged in using Windows
Authentication

All of the links are set up using "sa".

Stu wrote:

Quote:

Originally Posted by

Not completely sure what you mean by a dblink, but what SQL permissions
do the Administrators have on each server? Are you sure the
BUILTIN/Administrators Windows group have the appropriate permissions
on the databases you want to select from?
>
Stu
>
>
traceable1 wrote:
I have a couple new servers - Windows 2003 R2 - with SQL Server 2000
SP4 installed. They are all Active/Active clustered instances (my
first ones).

I am trying to create database links to other SQL Server instances, but
there are 3 that I cannot connect to.

The dblink works if I connect to the instance as "sa", but not as my
Windows Authenticated account. We use Active Directory and I am in the
Administrator group on all of the boxes.

Of the 3 I can't get to, 1 is a cluster (Active/Passive) and the other
2 are just regular Enterprise instances. They are all SQL 2000 SP4.

I have several other instances, all SP4 on 2003 boxes and I can connect
to all of them.

Also, on the instances where the dblink does not work, I can actually
connect to these databases w/in Enterprise Manager successfully.

I am using a different port for the instances, but I have set them up
in the Client Network Utility as well and still can't connect.

I can connect via a dblink TO these new instances from the older boxes
fine.

I'm really stumped - I've had the Network people verify we don't have a
firewall issue or something.

Must be some sort of permissions problem, but I don't know what else to
check - - -

Please help!!

THANK YOU!!

Databse is lost

Hi,
I am using windows server STD 2003, with SP1, with SQL server 2000 with SP1.
The database stops working almost every 24 hours. I have to stop/kill
services and then start again to get it back up.
Kindly advise.
ThanksYou would want to start by checking the SQL Server error
logs and the Windows event logs. There should be something
logged to give you some clues as to what is going on with
your SQL Server.
-Sue
On Mon, 15 May 2006 22:35:01 -0700, Al Gates
<AlGates@.discussions.microsoft.com> wrote:

>Hi,
>I am using windows server STD 2003, with SP1, with SQL server 2000 with SP1
.
>The database stops working almost every 24 hours. I have to stop/kill
>services and then start again to get it back up.
>Kindly advise.
>Thanks

DataBinding to radio button

I have a windows form containing some text boxes and radio buttons bount to an SQL Server database, with code like the following:

this.tbBorrowerLastName.DataBindings.Add (new Binding("Text", dsData.Tables["Results"],"BorrowerLastName"();

this.rbMale.DataBindings.Add(new Binding("Checked", dsData.Tables["Results"],"Male"))

If I add a new row and try to move there using the code below, nothing happens (neither movement to a new position nor error message), unless I remove the radio button bindings. (The same thing occurs if I attempt to move to any record that has a null value in the database field for a radio button).

myLastRow = dsData.Tables["Results"].NewRow();

dsData.Tables["Results"].Rows.Add(myLastRow);

I attempt to move by changing the value of the position property of the BindingContext object.

How can I retain the radio button bindings and still be able to add and move to a new row?

Any help would be appreciated.

I was able to figure my own solution.

The problem was a null value for the checked property of the radio buttons. I tried adding a default value to Visual Studio and to the database, but neither of those solved the problem.

Inbetween the two lines of code in my earlier post (beginning myLastRow and dsData.Tables respectively), I added:

myLastRow["Male"]=true;

myLastRow["Female"]=false;

Problem solved.

Databases per Server

All,

I have 2 web applications running on 2 W2K servers. Each server has a local SQL server(2000). We are about to upgrade the servers to Windows 2003. The web applications are running classic ASP and VB COM+ objects. We are going to take the opportunity to seperate SQL from the web server. What will end up with is 2 web servers running the applications and a single database server with 2 databases servering up the data. We will upgrade the SQL2K to SQL2K5.

My question is how will the SQL performance be affected? What's the best place to locate the COM+ objects? What kind of pitfalls do I need to be aware of?

Thanks

BB

Make sure that the consolidated box has suitable hardware to support both apps (memory, disks, processors). Also, remember that now the a failure of the SQL Server will bring down both while if one database starts hogging resources, the other would be adversely affected. Similarly you'll only have one set of system databases so make sure that tempdb is on a fast set of disks.

Certainly one area you may need to check any conflicts arising from any SQL Server configurations that may differ on the current boxes and also any login conflicts. Remember, also that future patches will be applied at the server level and both apps will need to be able to run on the same SQL version.

You are able to run multiple instances on one box which would allow you to allocate resources better to each application or could consider virtual servers which is becoming more and more popular these days.

HTH!

|||

Great advice - thanks!

What about the increase in network traffic. Is there something to do hardware wise? Like adding a second NIC card? Will that even make a difference?

Thanks

Databases on different storage

I am newbie in SQL server and have one, maybe dumb question.
I have SQL2000 cluster on Windows 2003 with shared storage on SAN.
Cluster operates with one database only.
I need to temporary attach second database to SQL server, but problem is
that I do not have enought free space on shared storage to place both
databases. It is possible to attach another database in cluster
environment from local one node drive ? No fail-over needed. Problem is
that SQL server in cluster see only shared drives. It should look like
one database in cluster environment and one in not.
Maybe with two instances or virtual servers ?
Thanx.
Short answer is no.
Longer explanation is that in a cluster, all SQL data files must be on a
cluster disk resource that the SQL server is dependant on. YOu cannot use
local storage in a SQL 2000 cluster implementation.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"zycha" <zycha@.NOT_FOR_SPAM.COM> wrote in message
news:OnDuY9v8EHA.2196@.TK2MSFTNGP11.phx.gbl...
> I am newbie in SQL server and have one, maybe dumb question.
> I have SQL2000 cluster on Windows 2003 with shared storage on SAN.
> Cluster operates with one database only.
> I need to temporary attach second database to SQL server, but problem is
> that I do not have enought free space on shared storage to place both
> databases. It is possible to attach another database in cluster
> environment from local one node drive ? No fail-over needed. Problem is
> that SQL server in cluster see only shared drives. It should look like
> one database in cluster environment and one in not.
> Maybe with two instances or virtual servers ?
> Thanx.
|||Hello.
It may be possible to use a mount point. I've done this with two shared physical disk resources that were in the same resource group. That is: I created a folder in a formatted partition on physical disk 1 (let's call it "I:\NDF") and mounted a formatted partition from physical disk 2 on I:\NDF.
I was able to create SQL server data files on the mounted volume, even though the physical disk resource (2) was not in the SQL server resource dependancy list. Apparently SQL server doesn't know that the filesystem has a mount point, but why would it care?
Now, I'm not sure if it will work with a "local" disk, but you may try if you are feeling adventurous. Also, this was on Win2KAS, not 2.003K
Interestingly, and despite warnings against doing this (warnings which I did not read until after it had been operational in a production environment for months), the SQL server worked fine and even went through failovers without a hitch.
It will definitely not survive a failover if you use a local disk, however.
Anyway, I would not normally "suggest" doing this, because it is not supported, but it may be a viable option if you just need a few rows out of a table somewhere.
Goog Luck
jg|||Geoff N. Hiten wrote:
> Short answer is no.
> Longer explanation is that in a cluster, all SQL data files must be on a
> cluster disk resource that the SQL server is dependant on. YOu cannot use
> local storage in a SQL 2000 cluster implementation.
>
thanx

Databases can only be backed up locally?

Dear all,
I have two windows 2003 servers, one is running arcserve 11.1 with sp2,
the
other is running MSSQL 2000 with SP4 with SAP application.
I have already installed the client agnet and sql agnet 11.1 sp2 to the
SQL
server.
However whenever I backup the SQL database arcserve will give me the
Error 1
326 saying that the username/password is incorrect.
I can browse thru the tree in arcserve manager and I can backup other
file o
n the sql server with no problem.
Then I tried to install the arcserve manager to the sql server and
tried to
backup the sql database with exactly the same username and password, it
work
s!
I confirm that there is no blocking for any network traffic between two
serv
er.
Would anyone help me on this to allow backup thru network from the sql
serve
r to the backup server?
Thanks a lot!
--
kevinling1
---
Posted via http://www.webservertalk.com
---
View this thread: http://www.webservertalk.com/message1564670.htmlkevinling1 wrote:
> Dear all,
> Would anyone help me on this to allow backup thru network from the sql
> serve
> r to the backup server?
> Thanks a lot!
>
I can't help you with the Arcserve problem, but I'd like to suggest
STRONGLY that you not perform your database backups using an agent like
this. Do your database backups using the native SQL BACKUP command,
backing up your data to a file on disk. Use Arcserve to backup that
disk file. These agent-based database backups tend to be not the most
reliable things.

Databases can only be backed up locally?

Dear all,
I have two windows 2003 servers, one is running arcserve 11.1 with sp2, the
other is running MSSQL 2000 with SP4 with SAP application.
I have already installed the client agnet and sql agnet 11.1 sp2 to the SQL
server.
However whenever I backup the SQL database arcserve will give me the Error 1
326 saying that the username/password is incorrect.
I can browse thru the tree in arcserve manager and I can backup other file o
n the sql server with no problem.
Then I tried to install the arcserve manager to the sql server and tried to
backup the sql database with exactly the same username and password, it work
s!
I confirm that there is no blocking for any network traffic between two serv
er.
Would anyone help me on this to allow backup thru network from the sql serve
r to the backup server?
Thanks a lot!kevinling1 wrote:
> Dear all,
> Would anyone help me on this to allow backup thru network from the sql
> serve
> r to the backup server?
> Thanks a lot!
>
I can't help you with the Arcserve problem, but I'd like to suggest
STRONGLY that you not perform your database backups using an agent like
this. Do your database backups using the native SQL BACKUP command,
backing up your data to a file on disk. Use Arcserve to backup that
disk file. These agent-based database backups tend to be not the most
reliable things.|||kevinling1 wrote:
> Dear all,
> Would anyone help me on this to allow backup thru network from the sql
> serve
> r to the backup server?
> Thanks a lot!
>
I can't help you with the Arcserve problem, but I'd like to suggest
STRONGLY that you not perform your database backups using an agent like
this. Do your database backups using the native SQL BACKUP command,
backing up your data to a file on disk. Use Arcserve to backup that
disk file. These agent-based database backups tend to be not the most
reliable things.

Database would not auto grow

SQL Server 2000 running on Windows NT4 Server, Database Data File on a disk
with a single NTFS Partition of 100Gb.
We have a database with the data file set to auto grow by 7% with
unrestricted file growth.
At the point that it reached 32Gb it ceased to auto grow, updates, inserts
were failing. There is 18GB free on the disk on which the associated data
file resides.
In the end we just associated another data file with the database because we
couldn't work out what was going on.
Anyone have any suggestions ?
If you increase the size of the data file manually with "alter database
modify file" command, does the file grow and consume the 18GB of free disk
space?
Wei Xiao
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Barry Shapiro" <BarryShapiro@.discussions.microsoft.com> wrote in message
news:8B63956F-86B8-470F-8388-015A140AE85C@.microsoft.com...
> SQL Server 2000 running on Windows NT4 Server, Database Data File on a
disk
> with a single NTFS Partition of 100Gb.
> We have a database with the data file set to auto grow by 7% with
> unrestricted file growth.
> At the point that it reached 32Gb it ceased to auto grow, updates, inserts
> were failing. There is 18GB free on the disk on which the associated data
> file resides.
> In the end we just associated another data file with the database because
we
> couldn't work out what was going on.
> Anyone have any suggestions ?
>
|||Check SQL Server error log to see if the 'auto grow' is resulting in any
errors. Can you post those errors here, if you see any?
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Barry Shapiro" <BarryShapiro@.discussions.microsoft.com> wrote in message
news:8B63956F-86B8-470F-8388-015A140AE85C@.microsoft.com...
SQL Server 2000 running on Windows NT4 Server, Database Data File on a disk
with a single NTFS Partition of 100Gb.
We have a database with the data file set to auto grow by 7% with
unrestricted file growth.
At the point that it reached 32Gb it ceased to auto grow, updates, inserts
were failing. There is 18GB free on the disk on which the associated data
file resides.
In the end we just associated another data file with the database because we
couldn't work out what was going on.
Anyone have any suggestions ?
|||Hello
This could be because the amount of space that autogrow needs to grow the
file by is large enough that the request times out while the newly
allocated portion of the file is still being zeroed out. Change the 7% to
500MB (from database file properties window in Enterprise Manager) and
check if autogrow works again.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Database would not auto grow

SQL Server 2000 running on Windows NT4 Server, Database Data File on a disk
with a single NTFS Partition of 100Gb.
We have a database with the data file set to auto grow by 7% with
unrestricted file growth.
At the point that it reached 32Gb it ceased to auto grow, updates, inserts
were failing. There is 18GB free on the disk on which the associated data
file resides.
In the end we just associated another data file with the database because we
couldn't work out what was going on.
Anyone have any suggestions ?If you increase the size of the data file manually with "alter database
modify file" command, does the file grow and consume the 18GB of free disk
space?
--
Wei Xiao
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Barry Shapiro" <BarryShapiro@.discussions.microsoft.com> wrote in message
news:8B63956F-86B8-470F-8388-015A140AE85C@.microsoft.com...
> SQL Server 2000 running on Windows NT4 Server, Database Data File on a
disk
> with a single NTFS Partition of 100Gb.
> We have a database with the data file set to auto grow by 7% with
> unrestricted file growth.
> At the point that it reached 32Gb it ceased to auto grow, updates, inserts
> were failing. There is 18GB free on the disk on which the associated data
> file resides.
> In the end we just associated another data file with the database because
we
> couldn't work out what was going on.
> Anyone have any suggestions ?
>|||Check SQL Server error log to see if the 'auto grow' is resulting in any
errors. Can you post those errors here, if you see any?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Barry Shapiro" <BarryShapiro@.discussions.microsoft.com> wrote in message
news:8B63956F-86B8-470F-8388-015A140AE85C@.microsoft.com...
SQL Server 2000 running on Windows NT4 Server, Database Data File on a disk
with a single NTFS Partition of 100Gb.
We have a database with the data file set to auto grow by 7% with
unrestricted file growth.
At the point that it reached 32Gb it ceased to auto grow, updates, inserts
were failing. There is 18GB free on the disk on which the associated data
file resides.
In the end we just associated another data file with the database because we
couldn't work out what was going on.
Anyone have any suggestions ?|||Hello
This could be because the amount of space that autogrow needs to grow the
file by is large enough that the request times out while the newly
allocated portion of the file is still being zeroed out. Change the 7% to
500MB (from database file properties window in Enterprise Manager) and
check if autogrow works again.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Database would not auto grow

SQL Server 2000 running on Windows NT4 Server, Database Data File on a disk
with a single NTFS Partition of 100Gb.
We have a database with the data file set to auto grow by 7% with
unrestricted file growth.
At the point that it reached 32Gb it ceased to auto grow, updates, inserts
were failing. There is 18GB free on the disk on which the associated data
file resides.
In the end we just associated another data file with the database because we
couldn't work out what was going on.
Anyone have any suggestions ?If you increase the size of the data file manually with "alter database
modify file" command, does the file grow and consume the 18GB of free disk
space?
Wei Xiao
SQL Server Storage Engine Development
This posting is provided "AS IS" with no warranties, and confers no rights.
"Barry Shapiro" <BarryShapiro@.discussions.microsoft.com> wrote in message
news:8B63956F-86B8-470F-8388-015A140AE85C@.microsoft.com...
> SQL Server 2000 running on Windows NT4 Server, Database Data File on a
disk
> with a single NTFS Partition of 100Gb.
> We have a database with the data file set to auto grow by 7% with
> unrestricted file growth.
> At the point that it reached 32Gb it ceased to auto grow, updates, inserts
> were failing. There is 18GB free on the disk on which the associated data
> file resides.
> In the end we just associated another data file with the database because
we
> couldn't work out what was going on.
> Anyone have any suggestions ?
>|||Check SQL Server error log to see if the 'auto grow' is resulting in any
errors. Can you post those errors here, if you see any?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Barry Shapiro" <BarryShapiro@.discussions.microsoft.com> wrote in message
news:8B63956F-86B8-470F-8388-015A140AE85C@.microsoft.com...
SQL Server 2000 running on Windows NT4 Server, Database Data File on a disk
with a single NTFS Partition of 100Gb.
We have a database with the data file set to auto grow by 7% with
unrestricted file growth.
At the point that it reached 32Gb it ceased to auto grow, updates, inserts
were failing. There is 18GB free on the disk on which the associated data
file resides.
In the end we just associated another data file with the database because we
couldn't work out what was going on.
Anyone have any suggestions ?|||Hello
This could be because the amount of space that autogrow needs to grow the
file by is large enough that the request times out while the newly
allocated portion of the file is still being zeroed out. Change the 7% to
500MB (from database file properties window in Enterprise Manager) and
check if autogrow works again.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Database Users Appear to be Corrupt

We had a hardware error on our production machine and had to replace it with
our backup machine. Both machines are running SQL Server 2000 on Windows
2000. I used the SQL Server database backup file from production to restore
the backup server.
I know about the sid's being out of sync between the logins and the database
users. I used our standard procedures to re-align them but must have done
something wrong. Now when I run sp_change_users_login 'Report', the list is
empty. I can see the users listed under the database using the enterprise
manager and the users can access the database but I fear that some table
somewhere pertaining to users is corrupted.You should be ok. The Report option of
sp_change_users_login only lists logins that are out of
sync. If you don't get any back from
sp_change_users_login 'Report', then they should all be in
sync.
This is taken directly from BOL pertaining to the Report
option:
"Lists the users, and their corresponding security
identifiers (SID), that are in the current database, not
linked to any login."
>--Original Message--
>We had a hardware error on our production machine and had
to replace it with
>our backup machine. Both machines are running SQL Server
2000 on Windows
>2000. I used the SQL Server database backup file from
production to restore
>the backup server.
>I know about the sid's being out of sync between the
logins and the database
>users. I used our standard procedures to re-align them
but must have done
>something wrong. Now when I run
sp_change_users_login 'Report', the list is
>empty. I can see the users listed under the database
using the enterprise
>manager and the users can access the database but I fear
that some table
>somewhere pertaining to users is corrupted.
>
>.
>|||Hi Robert,
Thank you for using MSDN Newsgroup! It's my pleasure to assist you with your issue.
As Van has pointed out, no report from sp_change_ueses_login means no sync problem of
the corresponding SID and everything seems fine on your side.
It is also recommended you try Database Consistency Checker (DBCC) statements after you
backup and restore your database.
You can use DBCC CHECKDB to check the allocation and structural integrity of the whole
database, or use DBCC CHECKALLOC / DBCC CHECKTABLE to check the individual objects
(including some suspicious tables).
For more information, please refer to Books Online on the topic "DBCC CHECKDB" and
"DBCC CHECKTABLE".
Robert, does this answer your question? If there is anything more we can do to assist you,
please feel free to post it in the group
Best regards,
Billy Yao
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.