Microsoft Reporting Service

I have the following Question:

Is it possible to install a Reporting Service at IIS Webserver without
SQL Server 2000 on the same machine.

We have a Enterprise SQL Server at another machine and i don't want to
install another SQL Server at a IIS.

Thank you for all responses

Flecki"flecki" <thorsten.fleckenstein@.de.cpm-int.com> wrote in message
news:f2626ae2.0409222330.309f741f@.posting.google.c om...
>I have the following Question:
> Is it possible to install a Reporting Service at IIS Webserver without
> SQL Server 2000 on the same machine.
> We have a Enterprise SQL Server at another machine and i don't want to
> install another SQL Server at a IIS.
> Thank you for all responses
> Flecki

Yes - you can use a remote database:

http://msdn.microsoft.com/library/d...grs_v1_8k82.asp

Simon

Microsoft OLE DB Provider for SQL Server error '80004005'

Hello Group,

I need some help in the worst way. I had a program/database I was working on a particular machine. I took all the data from there and placed it on a another machine. Now I'm unable to navigate through the web pages on the new machine. I am getting the error...

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

......asp, line 19

Can you please help!!

Quote:

Originally Posted by ConfusedDeuce

Hello Group,

I need some help in the worst way. I had a program/database I was working on a particular machine. I took all the data from there and placed it on a another machine. Now I'm unable to navigate through the web pages on the new machine. I am getting the error...

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

......asp, line 19

Can you please help!!

On line 19, your connection to the database is failing. Are you on the same network segment/subnet as you previously were? What is the physical difference between the computers?|||

Quote:

Originally Posted by ConfusedDeuce

Hello Group,

I need some help in the worst way. I had a program/database I was working on a particular machine. I took all the data from there and placed it on a another machine. Now I'm unable to navigate through the web pages on the new machine. I am getting the error...

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

......asp, line 19

Can you please help!!

How are you now specifying the server name when connecting to this machine?
You'll need to allow the server port on that new machine if it's running a firewall.|||

Quote:

Originally Posted by Motoma

On line 19, your connection to the database is failing. Are you on the same network segment/subnet as you previously were? What is the physical difference between the computers?

The thing is that I'm not completely sure what the other machine had on it because they data was copied over from that machine and the machine was immediately taken away. Now I am using VMWare and virtually connected to new machine (which shouldnt be the problem). I'm not sure of any of the specs of the last machine : (|||

Quote:

Originally Posted by r035198x

How are you now specifying the server name when connecting to this machine?
You'll need to allow the server port on that new machine if it's running a firewall.

I'm not connecting to the old machine anymore. That machine is out of the office and no longer in physical reach.|||

Quote:

Originally Posted by ConfusedDeuce

The thing is that I'm not completely sure what the other machine had on it because they data was copied over from that machine and the machine was immediately taken away. Now I am using VMWare and virtually connected to new machine (which shouldnt be the problem). I'm not sure of any of the specs of the last machine : (

Do you have the SQL Server database up and running on the new machine? Have you added the appropriate accounts and permissions for the users?|||

Quote:

Originally Posted by Motoma

Do you have the SQL Server database up and running on the new machine? Have you added the appropriate accounts and permissions for the users?

Yes it is up and running. How do i add the accounts and permissions?|||

Quote:

Originally Posted by ConfusedDeuce

Yes it is up and running. How do i add the accounts and permissions?

Enterprise Manager -> Server -> Security -> Logins
Enterprise Manager -> Server -> Databases -> Database -> Users
Enterprise Manager -> Server -> Databases -> Database -> Roles|||

Quote:

Originally Posted by ConfusedDeuce

I'm not connecting to the old machine anymore. That machine is out of the office and no longer in physical reach.

Actually I was refering to that new machine. That error means that the connection to the database server was not done correctly. The reasons could be
wrong hostname being specified
firewall blocking connections
change of IP
wrong port being used or break in TCP/IP conection while accessing the database server
e.t.c

Microsoft iSCSI Initiator & SQL Server services

Hello all,
I have Microsoft iSCSI Initiator (SAN) installed on a SQL Server machine and has this drive acting as a local drive. All the database's data files are residing on this drive, attached with SAN.
It runs as a service "Microsoft iSCSI Initiator" on the SQL Server machine.

Now the question is, when we restart the SQL Server all the databases change their status to "Suspect" and we have to stop all the sqlserver services (all the SQL instances) and start them all up. This is the only temporary solution we came up with.
Could any one has any real solution or had encounter such a problem before?

Any help is appreciated.

Thanks bunch!
imransi.Looks like your SQL Service starts before your SAN is available.|||Originally posted by rdjabarov
Looks like your SQL Service starts before your SAN is available.

You are 100% right. So thats why we are restarting SQL services.
We can manually start sql services but thats not what we wnat and really thsi should not be the solutuion ;)|||See if you can "impose" a dependency on MSSQLSERVER service in regards to this SAN service.

Microsoft Client Utilities

Is there a separate installation or download that can be used to install the
Microsoft SQL Client Utilities on a machine to provide the ability for a
client application to communicate with the Microsoft SQL Server Database. I
know the Tools and Utilities are included on the SQL Server CD but we need
to give the utilities to our customer so that they can access our SQL Server
database (i.e. they do not own Microsoft SQL).
Regards,
Randall
Randall,
If all they need is connectivity, one option is the sqlredis
executable. It's on your SQL CD. There is more info on it in
books online but basically it's just an exe you can give to
the customers that will install the client connectivity
components.
-Sue
On Thu, 25 Mar 2004 15:24:02 -0800, "Microsoft Newsreader"
<newsreader@.ivr.com> wrote:

>Is there a separate installation or download that can be used to install the
>Microsoft SQL Client Utilities on a machine to provide the ability for a
>client application to communicate with the Microsoft SQL Server Database. I
>know the Tools and Utilities are included on the SQL Server CD but we need
>to give the utilities to our customer so that they can access our SQL Server
>database (i.e. they do not own Microsoft SQL).
>Regards,
>Randall
>
|||Thank you very much for the information and the prompt response.
Regards,
Randall
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:rns660ljcpppteh9hponhc5ha0khgv3v44@.4ax.com...
> Randall,
> If all they need is connectivity, one option is the sqlredis
> executable. It's on your SQL CD. There is more info on it in
> books online but basically it's just an exe you can give to
> the customers that will install the client connectivity
> components.
> -Sue
> On Thu, 25 Mar 2004 15:24:02 -0800, "Microsoft Newsreader"
> <newsreader@.ivr.com> wrote:
the
I
need
Server
>

Mgs 8650:

When I switched to a multiple processor SQL Server 2000 machine, some of the
more complex queries produced this error
(http://support.microsoft.com/?kbid=837983):
Msg 8650:
Intra-query parallelism caused your server command (process ID #50) to
deadlock. Rerun the query without intra-query parallelism by using the query
hint option (maxdop 1).
I had SP3a but the error still occured even with the MAXDOP 1 hint on the
query. The only resolution that worked was to set the "Use" processors = 1
on the properties. Does anyone know if SP4 has the resolution for this in
in?
DabHi David
There are 6 options to try in this article, did you try any of the others?
John
"David A. Beck" wrote:
> When I switched to a multiple processor SQL Server 2000 machine, some of the
> more complex queries produced this error
> (http://support.microsoft.com/?kbid=837983):
> Msg 8650:
> Intra-query parallelism caused your server command (process ID #50) to
> deadlock. Rerun the query without intra-query parallelism by using the query
> hint option (maxdop 1).
> I had SP3a but the error still occured even with the MAXDOP 1 hint on the
> query. The only resolution that worked was to set the "Use" processors = 1
> on the properties. Does anyone know if SP4 has the resolution for this in
> in?
> Dab
>
>
>|||John,
All except re-writing the query. The hints (2 options) did not do anything.
The reason for my question is that I thought SP4 might negate the need for
option 1 (crippling the SP3+ parallel scan behavior). Running the query
again (as if I hadn't run it a zillion times) never works.General
performance tuning is just hit and miss.
MS has know about this problem for some time so I ask this question again,
does SP4 resolve the intra-query parallelism deadlock problem?
Dab
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:D95D94BC-2149-4B32-9224-3A9DCDF6E0A3@.microsoft.com...
> Hi David
> There are 6 options to try in this article, did you try any of the others?
> John
> "David A. Beck" wrote:
>> When I switched to a multiple processor SQL Server 2000 machine, some of
>> the
>> more complex queries produced this error
>> (http://support.microsoft.com/?kbid=837983):
>> Msg 8650:
>> Intra-query parallelism caused your server command (process ID #50) to
>> deadlock. Rerun the query without intra-query parallelism by using the
>> query
>> hint option (maxdop 1).
>> I had SP3a but the error still occured even with the MAXDOP 1 hint on the
>> query. The only resolution that worked was to set the "Use" processors =>> 1
>> on the properties. Does anyone know if SP4 has the resolution for this in
>> in?
>> Dab
>>
>>

Mgs 8650:

When I switched to a multiple processor SQL Server 2000 machine, some of the
more complex queries produced this error
(http://support.microsoft.com/?kbid=837983):
Msg 8650:
Intra-query parallelism caused your server command (process ID #50) to
deadlock. Rerun the query without intra-query parallelism by using the query
hint option (maxdop 1).
I had SP3a but the error still occured even with the MAXDOP 1 hint on the
query. The only resolution that worked was to set the "Use" processors = 1
on the properties. Does anyone know if SP4 has the resolution for this in
in?
DabHi David
There are 6 options to try in this article, did you try any of the others?
John
"David A. Beck" wrote:

> When I switched to a multiple processor SQL Server 2000 machine, some of t
he
> more complex queries produced this error
> (http://support.microsoft.com/?kbid=837983):
> Msg 8650:
> Intra-query parallelism caused your server command (process ID #50) to
> deadlock. Rerun the query without intra-query parallelism by using the que
ry
> hint option (maxdop 1).
> I had SP3a but the error still occured even with the MAXDOP 1 hint on the
> query. The only resolution that worked was to set the "Use" processors = 1
> on the properties. Does anyone know if SP4 has the resolution for this in
> in?
> Dab
>
>
>|||John,
All except re-writing the query. The hints (2 options) did not do anything.
The reason for my question is that I thought SP4 might negate the need for
option 1 (crippling the SP3+ parallel scan behavior). Running the query
again (as if I hadn't run it a zillion times) never works.General
performance tuning is just hit and miss.
MS has know about this problem for some time so I ask this question again,
does SP4 resolve the intra-query parallelism deadlock problem?
Dab
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:D95D94BC-2149-4B32-9224-3A9DCDF6E0A3@.microsoft.com...[vbcol=seagreen]
> Hi David
> There are 6 options to try in this article, did you try any of the others?
> John
> "David A. Beck" wrote:
>

Mgs 8650:

When I switched to a multiple processor SQL Server 2000 machine, some of the
more complex queries produced this error
(http://support.microsoft.com/?kbid=837983):
Msg 8650:
Intra-query parallelism caused your server command (process ID #50) to
deadlock. Rerun the query without intra-query parallelism by using the query
hint option (maxdop 1).
I had SP3a but the error still occured even with the MAXDOP 1 hint on the
query. The only resolution that worked was to set the "Use" processors = 1
on the properties. Does anyone know if SP4 has the resolution for this in
in?
Dab
Hi David
There are 6 options to try in this article, did you try any of the others?
John
"David A. Beck" wrote:

> When I switched to a multiple processor SQL Server 2000 machine, some of the
> more complex queries produced this error
> (http://support.microsoft.com/?kbid=837983):
> Msg 8650:
> Intra-query parallelism caused your server command (process ID #50) to
> deadlock. Rerun the query without intra-query parallelism by using the query
> hint option (maxdop 1).
> I had SP3a but the error still occured even with the MAXDOP 1 hint on the
> query. The only resolution that worked was to set the "Use" processors = 1
> on the properties. Does anyone know if SP4 has the resolution for this in
> in?
> Dab
>
>
>
|||John,
All except re-writing the query. The hints (2 options) did not do anything.
The reason for my question is that I thought SP4 might negate the need for
option 1 (crippling the SP3+ parallel scan behavior). Running the query
again (as if I hadn't run it a zillion times) never works.General
performance tuning is just hit and miss.
MS has know about this problem for some time so I ask this question again,
does SP4 resolve the intra-query parallelism deadlock problem?
Dab
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:D95D94BC-2149-4B32-9224-3A9DCDF6E0A3@.microsoft.com...[vbcol=seagreen]
> Hi David
> There are 6 options to try in this article, did you try any of the others?
> John
> "David A. Beck" wrote:

Method to check the connection status of any Machine on Network

Hello All:
I need to know the connection status of any machine on domain i.e. I want to
check that whether the machine is on or off(alive/dead).
If anyone can tell then I shall be highly grateful
Sincerely,
Adnan KudiyaHi
Try sp_who 'active'
"adnankudiya" <adnankudiya.1nq9tv@.mail.codecomments.com> wrote in message
news:adnankudiya.1nq9tv@.mail.codecomments.com...
> Hello All:
> I need to know the connection status of any machine on domain i.e. I
> want to check that whether the machine is on or off(alive/dead).
> If anyone can tell then I shall be highly grateful
> Sincerely,
> Adnan Kudiya
>
> --
> adnankudiya
> ---
> Posted via http://www.codecomments.com
> ---
>|||Hi
I assume you mean database connection status and not just something like
pinging the client periodically to see if you get a reply? This may be
difficult as you can gather information about when a connection last did
something sysprocesses, but you don't know if they are connected or have
died. If your application has a set timeout and any activity has not happene
d
in that time, I guess you can assume they are dead.
John
"adnankudiya" wrote:

> Hello All:
> I need to know the connection status of any machine on domain i.e. I
> want to check that whether the machine is on or off(alive/dead).
> If anyone can tell then I shall be highly grateful
> Sincerely,
> Adnan Kudiya
>
> --
> adnankudiya
> ---
> Posted via http://www.codecomments.com
> ---
>|||I thought about this a while back and did not come up with a good solution.
One idea was to write a stored procedure - sp_ping and execute that on the
connection:
create proc sp_ping
as
return 0
go
or something trivial and similar - EG
SELECT DateNow = GetDate()
You could run that SP with a timeout that is quite low say 2 seconds.
- Tim
BTW: I do realise sp_ is not a good prefix.
"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:F32C6F92-2896-4F96-9FC5-49D846A434FF@.microsoft.com...
> Hi
> I assume you mean database connection status and not just something like
> pinging the client periodically to see if you get a reply? This may be
> difficult as you can gather information about when a connection last did
> something sysprocesses, but you don't know if they are connected or have
> died. If your application has a set timeout and any activity has not
> happened
> in that time, I guess you can assume they are dead.
> John
> "adnankudiya" wrote:
>

Method of connect machine?

I work with sql server 2000 and I want to make remote access with another computer .

I want to know what is method

This link will provide you the various ways to connect to SQL Server and access data for your .NET application.

Data -.NET Tutorials for SQL Data
http://dotnetjunkies.com/QuickStartv20/howto/doc/adoplus/xmlfromsqlsrv.aspx

|||I don't mean that I connect machine with sql server2000 by another|||

Please help us understand what you are attempting to accomplish -because it is confusing what you want.

I work with sql server 2000 and I want to make remote access with another computer .

|||

I will explan by another way:

I program database application with sql server 2000 Engine and want to publish it . how can I connect all other machine throw my application with database .

|||

The 'Tutorials' I offered above have a lot of good information about how to connect an Application to SQL Server.

Also, perhaps www.connectionstrings.com may be helpful.

|||

These links should get you started:

http://msdn.microsoft.com/vstudio/express/beginner/

http://msdn2.microsoft.com/en-us/library/ms345332.aspx

http://support.microsoft.com/kb/914277

Method of connect machine?

I work with sql server 2000 and I want to make remote access with another computer .

I want to know what is method

This link will provide you the various ways to connect to SQL Server and access data for your .NET application.

Data -.NET Tutorials for SQL Data
http://dotnetjunkies.com/QuickStartv20/howto/doc/adoplus/xmlfromsqlsrv.aspx

|||I don't mean that I connect machine with sql server2000 by another|||

Please help us understand what you are attempting to accomplish -because it is confusing what you want.

I work with sql server 2000 and I want to make remote access with another computer .

|||

I will explan by another way:

I program database application with sql server 2000 Engine and want to publish it . how can I connect all other machine throw my application with database .

|||

The 'Tutorials' I offered above have a lot of good information about how to connect an Application to SQL Server.

Also, perhaps www.connectionstrings.com may be helpful.

|||

These links should get you started:

http://msdn.microsoft.com/vstudio/express/beginner/

http://msdn2.microsoft.com/en-us/library/ms345332.aspx

http://support.microsoft.com/kb/914277

Messages stuck in sys.transmission_queue

Hi,

At my company, we're trying to use service broker to create a client-server system where there is a head office machine and multiple outlets registered with that head office. My problem is that sometimes when a branch sends a message to the head office, it just seems to sit in the transmission queue and never gets sent. If I run a script that forcibly ends the conversations on the client machine (with cleanup), storing the message bodies and then resend them, they seem to get through fine.

The way that we send messages is by calling a t-sql stored procedure from a c# application using SqlCommand (don't know if this should make any difference).

If I monitor the Head Office machine and one of the Outlets while this is happening, on the HO I get three events in a row:

Broker: Message Classify (1 - Local) Audit Broker Conversation (2 - No Certificate) Broker: Message Undeliverable (1 - Sequenced Message)
The TextData contained in the third event is: This message could not be delivered because the security context could not be retrieved.

The RoleName of the server is Initiator, and the TargetUserName is the name of the service on the Outlet.

On the Outlet I get the following event repeatedly (presumably as it continues to try sending the message) - Broker: Remote Message Acknowledgement (1 - Message With Acknowledgement Sent).

On the client the RoleName also appears to be Initiator, and the TargetUserName is blank.

This would make me suspect that certificates were missing or something, except that if I remove messages from the queue and resend them they seem to get through, and also I've checked both databases and they have the correct certificates.

Any ideas?

Thanks in advance,

AdamThanks for the detailed info, it is always helpfull to have the full details when trying to diagnose an issue.
The most likely culprit in such cases is an account that has more certificates to be picked from when encrypting/signing a message. Whenever SSB has more than one certificates 'valid' to be used for a particular database principal, it will pick the one with the latest expiration date. So sometimes even though the configuration 'seems' correct, SSB will pick the 'wrong' certificate simply because it has multiple choices. The typical account prone to this problems is 'dbo', as certs are being created for dbo for various reasons and by default they are all valid for SSB to pick.
To confirm this problem, the 2nd event in your post (the Audit Broker Conversation one) actually tells which certificate was not found: it has the issuer name and serial number of the cert 'not found' on two of the columns (I can't remember now which ones and the BOL 'ommits' this detail). You can then look into the message sender's database to see why that particular cert was picked.
Certs can actualy be controled whether they are available for SSB to 'pick' by turning off the ACTIVE_FOR_BEGIN_DIALOG option on them (the option refers to certs used for the reverse path from target to initiator as well, despite the name 'begin_dalog'...)|||Thanks for the reply. What you're saying makes sense, and seems possible to me (we re-registered one of the outlets recently which could have caused this). The only problem is that the Audit Broker Conversation event doesn't appear to have the issuer or serial number in any of the columns. Maybe I'm using profiler wrong or something, but I would have thought that just selecting the event would have been enough. Any idea what I'm doing wrong?

Adam

|||

IssuerName is DBUserName and SerialNumber is in TargetLoginName.

Make sure the columns above are selected when defining the trace.

|||I had worked out that the IssuerName was DBUserName, but hadn't noticed the serial number. Thanks for explaining that. The thing is that the IssuerName isn't much use to me because the way I generated the certificates, they all have the same name .

But anyhow, I found a solution to the problem. Basically we had an old database on the same server that had broker enabled as well, and I'm guessing that since they both have the same service names in them, that was causing the problems. I disabled service broker on the old db and everything seems to be working again. The only thing I'm worried about now is how the broker became enabled on the database - but that's not really a service broker issue.

Thanks for the help.

Adam
|||

Whenever SSB finds multiple instances of the same service it assumes a load balancing scenario and will hash the incomming conversations to the available service instances. Specifying a broker_instance in the begin dialog from the initiator would make the application stick to a specific service (database), even if more instances of the service show up on the target.

Message size limitations on Service Broker?

Hi Everyone
Does anyone know if there is/isn't a size limitation on the Service
Broker. I have a remote machine running with express 2005 and I would
like to send message to/from the machine in Head Office running SQL
Server Enteprise 2005.
Thanks in advance
EricThe max message size of the service broker is 2 gigabytes (one billion
Unicode characters) if I am not mistaken.
--
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
<ricolee99@.gmail.com> wrote in message
news:1158184604.504436.77770@.m73g2000cwd.googlegroups.com...
> Hi Everyone
> Does anyone know if there is/isn't a size limitation on the Service
> Broker. I have a remote machine running with express 2005 and I would
> like to send message to/from the machine in Head Office running SQL
> Server Enteprise 2005.
> Thanks in advance
> Eric
>

Message size limitations on Service Broker?

Hi Everyone
Does anyone know if there is/isn't a size limitation on the Service
Broker. I have a remote machine running with express 2005 and I would
like to send message to/from the machine in Head Office running SQL
Server Enteprise 2005.
Thanks in advance
Eric
The max message size of the service broker is 2 gigabytes (one billion
Unicode characters) if I am not mistaken.
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
<ricolee99@.gmail.com> wrote in message
news:1158184604.504436.77770@.m73g2000cwd.googlegro ups.com...
> Hi Everyone
> Does anyone know if there is/isn't a size limitation on the Service
> Broker. I have a remote machine running with express 2005 and I would
> like to send message to/from the machine in Head Office running SQL
> Server Enteprise 2005.
> Thanks in advance
> Eric
>

Message size limitations on Service Broker?

Hi Everyone
Does anyone know if there is/isn't a size limitation on the Service
Broker. I have a remote machine running with express 2005 and I would
like to send message to/from the machine in Head Office running SQL
Server Enteprise 2005.
Thanks in advance
EricThe max message size of the service broker is 2 gigabytes (one billion
Unicode characters) if I am not mistaken.
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
<ricolee99@.gmail.com> wrote in message
news:1158184604.504436.77770@.m73g2000cwd.googlegroups.com...
> Hi Everyone
> Does anyone know if there is/isn't a size limitation on the Service
> Broker. I have a remote machine running with express 2005 and I would
> like to send message to/from the machine in Head Office running SQL
> Server Enteprise 2005.
> Thanks in advance
> Eric
>

Message Queue Task 64 bit Cluster issue

Hello,

I'm using the Message Queuing task to create a local private queue message. Everything works great on a 32 bit machine. When I try this on a 64 bit Itanium Cluster I keep getting the message "Message queue service is not available" in my SSIS log. I've using this string as my path "ClusterName\private$\QueueName". Does anyone know of any issues with the Message Queue task on 64 bit or a cluster? The Message Queue service is up and running, it doesn't make sense.

Thanks,

Andy

I found out that you must install MSMS on each node of the cluster separately. Then set up your Message Queue using the Cluster Administrator. See this document for help.

http://download.microsoft.com/download/4/f/5/4f518f76-c1ce-431b-b79f-71caf9e27578/MSMQ3incluster.doc

Also, it's easier if you use the utility mmcv.exe to set up the cluster:

http://support.microsoft.com/?kbid=898701&SD=tech

Andy