Showing posts with label couple. Show all posts
Showing posts with label couple. Show all posts

Sunday, March 11, 2012

Datagram message

My app was working fine (no change in the last couple of years) until
recently.
Here is an example of my XML -
<root
xmlns:updg="urn:schemas-microsoft-com:xml-updategram"><updg:sync><updg:before><ProbePart
VFPID="28724"/></updg:before><updg:after><ProbePart
ReconSell="5520"/></updg:after></updg:sync></root>
which results in the Response -
<H3>ERROR: 400.100 Bad Request</H3><b>HResult:</b>
0x80004005<br><b>Source:</b> Microsoft SQL isapi
extension<br><b>Description:</b> Query not specified<br>
Not sure where to look for resolution - any pointers would be appreciated.
Could you please provide some more information? Like what your setup is and
a simple complete repro?
Thanks
Michael
"howard" <howard@.discussions.microsoft.com> wrote in message
news:1B14174A-7CC0-4B78-BB8E-15EC906834BE@.microsoft.com...
> My app was working fine (no change in the last couple of years) until
> recently.
> Here is an example of my XML -
> <root
> xmlns:updg="urn:schemas-microsoft-com:xml-updategram"><updg:sync><updg:before><ProbePart
> VFPID="28724"/></updg:before><updg:after><ProbePart
> ReconSell="5520"/></updg:after></updg:sync></root>
> which results in the Response -
> <H3>ERROR: 400.100 Bad Request</H3><b>HResult:</b>
> 0x80004005<br><b>Source:</b> Microsoft SQL isapi
> extension<br><b>Description:</b> Query not specified<br>
> Not sure where to look for resolution - any pointers would be appreciated.
>
>

Wednesday, March 7, 2012

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!!

Friday, February 17, 2012

Database versipn (C.0.8.40) does not match

When I click the "Upgrade" button while trying to configure reporting
services I get a couple of errors here are the two errors:
"Verify Database Version" First Yellow "!" Says :
The database version (C.0.8.40) does not match your reporting services
installation. You must upgrade your reporting services database.
"Create Upgrade Script for Database Version" Second Yellow "!" say:
Couldn't generate the upgrade script. There is no upgrade script available
for this version.
Has anyone seen these errors before. How to I get around these. Right now
my "Database Setup" in has a red "X" on the "Reporting Services Configuration
Manager" window.I have the same exact problem. Any fixes yet?
--
---
Yes, I searched first :)
"Greg Larsen" wrote:
> When I click the "Upgrade" button while trying to configure reporting
> services I get a couple of errors here are the two errors:
> "Verify Database Version" First Yellow "!" Says :
> The database version (C.0.8.40) does not match your reporting services
> installation. You must upgrade your reporting services database.
> "Create Upgrade Script for Database Version" Second Yellow "!" say:
> Couldn't generate the upgrade script. There is no upgrade script available
> for this version.
> Has anyone seen these errors before. How to I get around these. Right now
> my "Database Setup" in has a red "X" on the "Reporting Services Configuration
> Manager" window.
>|||Do you have a resolution to this issue? I ahve the exact same problem.
"Greg Larsen" wrote:
> When I click the "Upgrade" button while trying to configure reporting
> services I get a couple of errors here are the two errors:
> "Verify Database Version" First Yellow "!" Says :
> The database version (C.0.8.40) does not match your reporting services
> installation. You must upgrade your reporting services database.
> "Create Upgrade Script for Database Version" Second Yellow "!" say:
> Couldn't generate the upgrade script. There is no upgrade script available
> for this version.
> Has anyone seen these errors before. How to I get around these. Right now
> my "Database Setup" in has a red "X" on the "Reporting Services Configuration
> Manager" window.
>|||I had the same problem.
It was caused by that I had installed reporting services after I had run
SP1 on SQL Server 2005.
Solved it by runing SQL Server 2005 SP1 again.
Hope this helps!
"Rich" wrote:
> Do you have a resolution to this issue? I ahve the exact same problem.
> "Greg Larsen" wrote:
> > When I click the "Upgrade" button while trying to configure reporting
> > services I get a couple of errors here are the two errors:
> >
> > "Verify Database Version" First Yellow "!" Says :
> > The database version (C.0.8.40) does not match your reporting services
> > installation. You must upgrade your reporting services database.
> >
> > "Create Upgrade Script for Database Version" Second Yellow "!" say:
> > Couldn't generate the upgrade script. There is no upgrade script available
> > for this version.
> >
> > Has anyone seen these errors before. How to I get around these. Right now
> > my "Database Setup" in has a red "X" on the "Reporting Services Configuration
> > Manager" window.
> >