Closed not Answered - New Call with updates

ok here goes I uninstalled SQL Server Express and decided to Install the Standard Edition - Wow that was huge to do - lots of little things left

I have now installed SQL Server 2005 Standard.

But I cannot configure it properly.

(How I know this) I can open Business Intelligence Development Studio - can after some initial fiddling around

design a report/data/layout/preview - but cannot render a report to either

my local machine - nz3/reports

or to an external vmw server

My Report configuration is not complete and initialisation is not complete.

I am aware there are lots of instructions on books online , I have been reading them all as well.

But other than going round and round in circles I don't know how or in what order to tackle them.

I have a document with screen shots that may be much more helpful to explain

Is there anyone willing to jump in and see if they can guide me through this.

ok just an update here - but I still need some help! if someone would like to jump in

I have configured everything in Reporting Services configuration but initialisation is still not going.

All my services are running - my home page = localhost is showing this:

Your Web service is now running. You do not currently have a default Web page established for your users.

But on configuration my virtual report server is ticked?

What else could I check?

thanks

|||Re: SQL Server 2005 setup with Reporting Services Configuration

Clients connect via Named Pipes even though its disabled

We've got SQL 2000 clients (standard install, no sp) who are connecting
to our SQL 2000 Servers with Named Pipes even though we've disabled
named pipes in the client network utility. They should be connecting
via tcp/ip. Any ideas on what could be causing this?
Hi Gary,
How are you determining that the client is connecting using named pipes? Is
there a chance that your connection string is prefixed with "np:"? If so,
this will override any client network settings. Otherwise, this is probably
the result of the last connection being cached. One way around this would
be to force the connection to use tcp/ip and this will overwrite the cache.
Il-Sung
Il-Sung Lee
Program Manager -- SQL Server Protocols
Microsoft Corp.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Gary" <gary.noon@.tradeweb.com> wrote in message
news:1118352084.179815.156620@.g14g2000cwa.googlegr oups.com...
> We've got SQL 2000 clients (standard install, no sp) who are connecting
> to our SQL 2000 Servers with Named Pipes even though we've disabled
> named pipes in the client network utility. They should be connecting
> via tcp/ip. Any ideas on what could be causing this?
>

Clients connect via Named Pipes even though its disabled

We've got SQL 2000 clients (standard install, no sp) who are connecting
to our SQL 2000 Servers with Named Pipes even though we've disabled
named pipes in the client network utility. They should be connecting
via tcp/ip. Any ideas on what could be causing this?Hi Gary,
How are you determining that the client is connecting using named pipes? Is
there a chance that your connection string is prefixed with "np:"? If so,
this will override any client network settings. Otherwise, this is probably
the result of the last connection being cached. One way around this would
be to force the connection to use tcp/ip and this will overwrite the cache.
Il-Sung
Il-Sung Lee
Program Manager -- SQL Server Protocols
Microsoft Corp.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Gary" <gary.noon@.tradeweb.com> wrote in message
news:1118352084.179815.156620@.g14g2000cwa.googlegroups.com...
> We've got SQL 2000 clients (standard install, no sp) who are connecting
> to our SQL 2000 Servers with Named Pipes even though we've disabled
> named pipes in the client network utility. They should be connecting
> via tcp/ip. Any ideas on what could be causing this?
>

Client Render broken after upgrade to Win2K3 Enterprise from Standard

First off, any suggestions are welcome here as we're lost.

We have a farm of 2 Win2k3 (standard) servers that had a couple GB of RAM. We then installed 16GB of RAM and upgraded to Win2k3 Enterprise to handle the upgrade.

Prior to the OS upgrade our reports rendered as expected. Post upgrade, they do not.

Some background on how we render...we open a PDF rendering of a report in a popup via JavaScript.

Also, we have 3 environments running the same code base. The only difference between the 3 is that one environment is the one we upgraded to Win2k3 Enterprise.

Again, any suggestions are much appreciated!

Scott

It would probably be important to note that we're using SQL Server 2005 and SQL RS 2005.|||

Of course, I forgot to add what's probably the biggest key. Only clients have this problem. Let me break that down. We have servers behing a crazy amount of firewall protection. The DB server is NOT on the SQL RS server. The Web server is also a farm, only serving this application.

I think this is the key. I can call the popup report (via the Web app) on any Web server on the farm, and it renders. When I call the report from a client outside of the network, the popup opens and the little green graphic comes up with "Report is being generated". This happens for about 20 seconds, then the graphic and text go away, the status bar says "Done", and there is a solid line at the top of the page...but of course no report (the title of the popup is correct by the way).

Thanks for your time!

Client access to sql database

sql 2000 on 2003 server standard, only 2 out of 10 users (xp pro clients)
trying to access sql program are asked to login to database, server name,
database, login id, password to TableName: datatable.
Is this an xp client issue or sql issue.
Can you give more details? How exactly are they logging in? Are you using
Windows authentication or SQL? Windows won't prompt you to login to SQL
Server since you already logged in to the domain.
Andrew J. Kelly SQL MVP
"Billy" <Billy@.discussions.microsoft.com> wrote in message
news:FB02C0E3-2E67-4979-B809-C49BE0496BCA@.microsoft.com...
> sql 2000 on 2003 server standard, only 2 out of 10 users (xp pro clients)
> trying to access sql program are asked to login to database, server name,
> database, login id, password to TableName: datatable.
> Is this an xp client issue or sql issue.
|||Users logon to the domain, and from a shared drive the clients run an msi
file that installs a program on their local pc's, this uses a sql database.
They start the program and when they try to run a report they get a pop up
box asking for login info for "TableName datatable". I think it is Windows
Authentication, don't know how to check which one is being used.
Trying to determine if an xp client issue or sql issue.
"Andrew J. Kelly" wrote:

> Can you give more details? How exactly are they logging in? Are you using
> Windows authentication or SQL? Windows won't prompt you to login to SQL
> Server since you already logged in to the domain.
> --
> Andrew J. Kelly SQL MVP
>
> "Billy" <Billy@.discussions.microsoft.com> wrote in message
> news:FB02C0E3-2E67-4979-B809-C49BE0496BCA@.microsoft.com...
>
>
|||If it is windows authentication it should not need to ask. You really need
to see what the application is using for a connection string.
Andrew J. Kelly SQL MVP
"Billy" <Billy@.discussions.microsoft.com> wrote in message
news:BEF206D6-AA2F-4949-9D5C-95B13AE16D42@.microsoft.com...[vbcol=seagreen]
> Users logon to the domain, and from a shared drive the clients run an msi
> file that installs a program on their local pc's, this uses a sql
> database.
> They start the program and when they try to run a report they get a pop up
> box asking for login info for "TableName datatable". I think it is Windows
> Authentication, don't know how to check which one is being used.
> Trying to determine if an xp client issue or sql issue.
> "Andrew J. Kelly" wrote:
|||Unfortunately I'm not a sql guru, just a network admin. This program that
points to the database was created by an outside company. Of course they say
that because only 2 of clients have the login issue it must be an xp client
issue and has nothing to do with the program. But the users are already in
the program, it is only when they try to run a report from within the program
that the login box appears?
Got any opinions one way or another?
"Andrew J. Kelly" wrote:

> If it is windows authentication it should not need to ask. You really need
> to see what the application is using for a connection string.
> --
> Andrew J. Kelly SQL MVP
>
> "Billy" <Billy@.discussions.microsoft.com> wrote in message
> news:BEF206D6-AA2F-4949-9D5C-95B13AE16D42@.microsoft.com...
>
>
|||What ever it is that is attempting to run the report must be making a new
connection. But without knowing what or how it is attempting to do this it
is anyone's guess. The vendor must have a clue as to how they connect and
why this is happening. After all they wrote it<g>. You can try using
profiler to see what they are sending to sql server at the time it happens.
Other than that I don't have a clue as to what the app is really doing.
Andrew J. Kelly SQL MVP
"Billy" <Billy@.discussions.microsoft.com> wrote in message
news:A498DAFD-838E-466C-A03F-FC3102784162@.microsoft.com...[vbcol=seagreen]
> Unfortunately I'm not a sql guru, just a network admin. This program that
> points to the database was created by an outside company. Of course they
> say
> that because only 2 of clients have the login issue it must be an xp
> client
> issue and has nothing to do with the program. But the users are already in
> the program, it is only when they try to run a report from within the
> program
> that the login box appears?
> Got any opinions one way or another?
> "Andrew J. Kelly" wrote:

Client access licenses needed for sql express or not

we have a sql express - that comes standard with servers.I just wanted to know.....Is there any addition Client access licenses needed for this sql express or not.

Hi Monika,

No, you don't need a CAL to connect to SQL Express, it is free to deploy and free to use.

Mike