Showing posts with label manager. Show all posts
Showing posts with label manager. Show all posts

Friday, March 30, 2012

problem with cascading parameters after CTP2

In the standard report manager I'm running a report with 5 parameter choices. The first 3 are determinants of the 4th, and the combined 1-4 determine the 5th.

Although this works fine in my VS BIDS (sp1) with SQL 2005 sp2 CTP, when I deploy it to my sp2 CTP Report server, it throws an error as soon as I select the 3rd parameter.

One or more data sources is missing credentials

I found this answer from MS in another thread (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=923684&SiteID=1) and since it deals with my problem, wanted to pass it along to anyone else that is dealing with this problem.

" This is a known regression with CTP2 that will be fixed before SP2 is released. The problem is not specific to multivalue parameters. It has to do with dependencies between parameters.

In some cases, you can work around the issue if you give the dependent parameter a default value. You can also work around the issue by removing the valid values dependency between the parameters, though this may not be possible for a given report."

The suggested workaround does work! I can get beyond the 3rd parameter now because I applied a default value!

The workaround is useless. It only alleviated the problem when I stayed with that default value for my 3rd parameter. As soon as I changed it I'm right back to the 'one or more data sources is missing credentials'

SP2 cannot be soon enough...

|||

The workaround suggested can work, but it's tricky, especially with nested parameters that are dependent on each other. I finally got a six parameter functional again but with some pain. I made all the dependent parameter lists 'multi-select' and gave them a functional default value. Only then do they populate correctly.

And this all because I was hoping to use these reports in WSS 3.0 with the report server addin. Got very close and now have stumbled across similar bug with multiple parameters in Sharepoint. Will post entry to Sharepoint forums.

sql

Friday, March 23, 2012

Problem with a server broker conversation between two instances

I have a problem with a server broker conversation between two instances on the same machine.

I have used Server Listning Manager to setup the communication between the instances.

When i a try to send a dialog it stops in sys.transmissin_queue and transmission_status is "The Service Broker protocol transport cannot listen on port 4022 because it is in use by another process."

Can someone help me

/ Dan Svensson

Are you trying to set up the communication between two instances on the same host? Then only one instance can listen on port 4022, the second instance must use a different port (say 4023). Use ALTER ENDPOINT to change the listenning port of one of the instances:

ALTER ENDPOINT [broker] AS TCP (LISTENER_PORT = 4023);

Now that you changed the listener port, you must also change the route used by the other instance to point to the new port (in the database where the service is):

ALTER ROUTE [routename] WITH ADDRESS = N'TCP://hostname:4023'

HTH,
~ Remus

|||

Tankyou

/Dan

sql

Tuesday, March 20, 2012

Problem while taking script

Hi all,
I have some stored procedures in my database.
When I take script of a stored procedure using Enterprise manager from a
client system, the alignment of IF, ELSE, END,etc... are changed. They are
not in a format that I typed in query analyzer.
When I take the same script from another client system they are in proper
alignment.
Please guide me to avoid this.
Should I change any of the settings?
Thanks,
SouraHi
You may want to check what service pack has been applied to the client i.e.
check the file version of (say) one of the exes ? Try scripting from the
Object Browser in Query Analyser.
John
"SouRa" wrote:
> Hi all,
> I have some stored procedures in my database.
> When I take script of a stored procedure using Enterprise manager from a
> client system, the alignment of IF, ELSE, END,etc... are changed. They are
> not in a format that I typed in query analyzer.
> When I take the same script from another client system they are in proper
> alignment.
> Please guide me to avoid this.
> Should I change any of the settings?
> Thanks,
> Soura

Problem while taking script

Hi all,
I have some stored procedures in my database.
When I take script of a stored procedure using Enterprise manager from a
client system, the alignment of IF, ELSE, END,etc... are changed. They are
not in a format that I typed in query analyzer.
When I take the same script from another client system they are in proper
alignment.
Please guide me to avoid this.
Should I change any of the settings?
Thanks,
SouraHi
You may want to check what service pack has been applied to the client i.e.
check the file version of (say) one of the exes ? Try scripting from the
Object Browser in Query Analyser.
John
"SouRa" wrote:

> Hi all,
> I have some stored procedures in my database.
> When I take script of a stored procedure using Enterprise manager from a
> client system, the alignment of IF, ELSE, END,etc... are changed. They ar
e
> not in a format that I typed in query analyzer.
> When I take the same script from another client system they are in proper
> alignment.
> Please guide me to avoid this.
> Should I change any of the settings?
> Thanks,
> Soura

Wednesday, March 7, 2012

Problem Viewing reports in Report Manager

I have successfully installed the sql server reporting services on a windows
2003 server. I have been able to deploy several reports to the report
server. I have even been able to schedule a report to execute and send out
via email every morning of the week.
Here's the problem. When I try to view a report using the report manager I
get a
The page cannot be found
HTTP 404 - File not found
Internet Explorer
error. I just don't get it. I can perform every other function using the
report manager except view the report online. Which of course is a problem
because I want to send my customers to the site to be able to view and run
reports.
Thanks for any help.
--
Jon Clayton
Regions Financial CorporationSounds like a security issue or a malformed URL. It's very difficult (from
here) to determine how you access report manager differently than the online
version, but could you post a URL that worked, and a URL that failed?
Dwayne|||Thanks for your help.
Here is a link that works
http://Servername/Reports/Pages/Folder.aspx
This link of course brings up the default folders page
Click on a folder and go to the following url, which work
http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
Click on a report in that folder to view the report using the following url
fail
http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
The failure only occurs within the frame below. The header frame is still
displayed, therefore I am able to:
Click on the properties tab with the failed page displayed is successful
using the following ur
http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
I have given full access permissions to the ASPNET account on the local
machine to the two RS folders.
I am convinced that it is a permissions issue. As a matter of fact I had an
instance installed in my test invironment which is Windows 2000 which worked
fine. But ever since the latest security updates that machine is having the
same issue.
Thanks again for your help.
--
Jon Clayton
Regions Financial Corporation
"Dwayne J. Baldwin" wrote:
> Sounds like a security issue or a malformed URL. It's very difficult (from
> here) to determine how you access report manager differently than the online
> version, but could you post a URL that worked, and a URL that failed?
> Dwayne
>
>|||"Jon" wrote:
> Thanks for your help.
> Here is a link that works
> http://Servername/Reports/Pages/Folder.aspx
> This link of course brings up the default folders page
> Click on a folder and go to the following url, which works
> http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
> Click on a report in that folder to view the report using the following url
> fails
> http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
> The failure only occurs within the frame below. The header frame is still
> displayed, therefore I am able to:
> Click on the properties tab with the failed page displayed is successful
> using the following url
> http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
> I have given full access permissions to the ASPNET account on the local
> machine to the two RS folders.
> I am convinced that it is a permissions issue. As a matter of fact I had an
> instance installed in my test invironment which is Windows 2000 which worked
> fine. But ever since the latest security updates that machine is having the
> same issue.
> Thanks again for your help.
> --
> Jon Clayton
> Regions Financial Corporation
>
> "Dwayne J. Baldwin" wrote:
> > Sounds like a security issue or a malformed URL. It's very difficult (from
> > here) to determine how you access report manager differently than the online
> > version, but could you post a URL that worked, and a URL that failed?
> >
> > Dwayne
> >
> >
> >
> > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.|||It appears that the entries in the config files are correct. Thanks for the
tip.
--
Jon Clayton
Regions Financial Corporation
"DLM" wrote:
>
> "Jon" wrote:
> > Thanks for your help.
> >
> > Here is a link that works
> > http://Servername/Reports/Pages/Folder.aspx
> > This link of course brings up the default folders page
> >
> > Click on a folder and go to the following url, which works
> > http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
> >
> > Click on a report in that folder to view the report using the following url
> > fails
> > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
> > The failure only occurs within the frame below. The header frame is still
> > displayed, therefore I am able to:
> >
> > Click on the properties tab with the failed page displayed is successful
> > using the following url
> > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
> >
> > I have given full access permissions to the ASPNET account on the local
> > machine to the two RS folders.
> >
> > I am convinced that it is a permissions issue. As a matter of fact I had an
> > instance installed in my test invironment which is Windows 2000 which worked
> > fine. But ever since the latest security updates that machine is having the
> > same issue.
> >
> > Thanks again for your help.
> >
> > --
> > Jon Clayton
> > Regions Financial Corporation
> >
> >
> > "Dwayne J. Baldwin" wrote:
> >
> > > Sounds like a security issue or a malformed URL. It's very difficult (from
> > > here) to determine how you access report manager differently than the online
> > > version, but could you post a URL that worked, and a URL that failed?
> > >
> > > Dwayne
> > >
> > >
> > >
> > > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.|||Hi Jon,
I have exactly the same problem. Please advise what I need to check/do?
Thanks very much
Khat.
"Jon" wrote:
> It appears that the entries in the config files are correct. Thanks for the
> tip.
> --
> Jon Clayton
> Regions Financial Corporation
>
> "DLM" wrote:
> >
> >
> > "Jon" wrote:
> >
> > > Thanks for your help.
> > >
> > > Here is a link that works
> > > http://Servername/Reports/Pages/Folder.aspx
> > > This link of course brings up the default folders page
> > >
> > > Click on a folder and go to the following url, which works
> > > http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
> > >
> > > Click on a report in that folder to view the report using the following url
> > > fails
> > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
> > > The failure only occurs within the frame below. The header frame is still
> > > displayed, therefore I am able to:
> > >
> > > Click on the properties tab with the failed page displayed is successful
> > > using the following url
> > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
> > >
> > > I have given full access permissions to the ASPNET account on the local
> > > machine to the two RS folders.
> > >
> > > I am convinced that it is a permissions issue. As a matter of fact I had an
> > > instance installed in my test invironment which is Windows 2000 which worked
> > > fine. But ever since the latest security updates that machine is having the
> > > same issue.
> > >
> > > Thanks again for your help.
> > >
> > > --
> > > Jon Clayton
> > > Regions Financial Corporation
> > >
> > >
> > > "Dwayne J. Baldwin" wrote:
> > >
> > > > Sounds like a security issue or a malformed URL. It's very difficult (from
> > > > here) to determine how you access report manager differently than the online
> > > > version, but could you post a URL that worked, and a URL that failed?
> > > >
> > > > Dwayne
> > > >
> > > >
> > > >
> > > > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.|||I am also having this same exact problem. I can run everything without issue
on our test server but production server is exhibiting this exact behavior?
I can do everything but view the report. I can even run the report on the
production server through code and through http://server/reportserver.
Navigate to the folder/report and viola. I can enter parameters and run it.
But not in the report manager gui' I get a 404 when I press the view
report button. If I press it a second time I then get an error in the lower
left hand corner of IE. If I open it up it states that on Line 50 permission
denied and url = http://server/reportserver...blah...blah...blah
Kevin
"Khat Liko" wrote:
> Hi Jon,
> I have exactly the same problem. Please advise what I need to check/do?
> Thanks very much
> Khat.
> "Jon" wrote:
> > It appears that the entries in the config files are correct. Thanks for the
> > tip.
> > --
> > Jon Clayton
> > Regions Financial Corporation
> >
> >
> > "DLM" wrote:
> >
> > >
> > >
> > > "Jon" wrote:
> > >
> > > > Thanks for your help.
> > > >
> > > > Here is a link that works
> > > > http://Servername/Reports/Pages/Folder.aspx
> > > > This link of course brings up the default folders page
> > > >
> > > > Click on a folder and go to the following url, which works
> > > > http://servername/Reports/Pages/Folder.aspx?ItemPath=%2fTeamWorkLoad&ViewMode=List
> > > >
> > > > Click on a report in that folder to view the report using the following url
> > > > fails
> > > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport
> > > > The failure only occurs within the frame below. The header frame is still
> > > > displayed, therefore I am able to:
> > > >
> > > > Click on the properties tab with the failed page displayed is successful
> > > > using the following url
> > > > http://servername/Reports/Pages/Report.aspx?ItemPath=%2fTeamWorkLoad%2fProblemReport&SelectedTabId=PropertiesTab
> > > >
> > > > I have given full access permissions to the ASPNET account on the local
> > > > machine to the two RS folders.
> > > >
> > > > I am convinced that it is a permissions issue. As a matter of fact I had an
> > > > instance installed in my test invironment which is Windows 2000 which worked
> > > > fine. But ever since the latest security updates that machine is having the
> > > > same issue.
> > > >
> > > > Thanks again for your help.
> > > >
> > > > --
> > > > Jon Clayton
> > > > Regions Financial Corporation
> > > >
> > > >
> > > > "Dwayne J. Baldwin" wrote:
> > > >
> > > > > Sounds like a security issue or a malformed URL. It's very difficult (from
> > > > > here) to determine how you access report manager differently than the online
> > > > > version, but could you post a URL that worked, and a URL that failed?
> > > > >
> > > > > Dwayne
> > > > >
> > > > >
> > > > >
> > > > > I had the same problem. The RSWebApplication.config file in the ReportServer bin folder has a URL setting which should be the same as your server.

Problem Viewing Databases in Enterprise Manager

I am using SQL Server 7.0 desktop version. I have a remote server registered in SQL Enterprise Manager. I can see the server itself and the main folders under it such as Databases, Management, Data Transformation Services, Security, and Support Services. However, when I click on the plus sign next to databases or try to view the databases it comes up "(No Items)". I am set up as a owner of one of the databases on this machine and I think I have access to all databases in this machine. Is there anything I can do to solve this problem?
I am not having this problem with any other registered SQL servers.I made sure the Show system databases and system object box was checked. It is checked. I still can not see anything.
-- anonymous@.discussions.microsoft.com wrote: --
Not sure if this will solve your problem, but give it a
try:
Right click on server name, select Edit sql server
registration properties and check "Show system databases
and system objects" box.
This should atleast show you master and other system
databases, if nothing else is wrong.
>--Original Message--
>>I am using SQL Server 7.0 desktop version. I have a
remote server registered in SQL Enterprise Manager. I can
see the server itself and the main folders under it such
as Databases, Management, Data Transformation Services,
Security, and Support Services. However, when I click on
the plus sign next to databases or try to view the
databases it comes up "(No Items)". I am set up as a
owner of one of the databases on this machine and I think
I have access to all databases in this machine. Is there
anything I can do to solve this problem?
>>I am not having this problem with any other registered
SQL servers.
>.
>

Monday, February 20, 2012

Problem using bcp with SQL MSDE

I successfully tested a bcp command similar to that below on a Small Business Manager database using SQL Enterprise Edition:
bcp "SELECT EMPLOYID FROM TWO..UPR00100" queryout testfile.txt -U login -P -C
I then tried using the same basic command for another Small Business Manager installation using SQL Desktop Edition. But I get the following:
SQLState = 08001, NativeError = 17
Error = [Microsoft][ODBC SQL Server Driver][DBNETLIB] SQL Server does not
exist or access denied.
The only other difference I'm aware of aside from the SQL edition is that an
'sa' password exists for the second environment. But I put the password in
the bcp command.
Does anyone have an idea why the bcp command works in the one
environment but not the other?
Thanks,
Tom
hi Tom,
"Tom Glasser" <Tom Glasser@.discussions.microsoft.com> ha scritto nel
messaggio news:3076FF6F-2708-4908-9149-6B0E148E6087@.microsoft.com...
> I successfully tested a bcp command similar to that below on a Small
Business Manager database using SQL Enterprise Edition:
> bcp "SELECT EMPLOYID FROM TWO..UPR00100" queryout testfile.txt -U
login -P -C
> I then tried using the same basic command for another Small Business
Manager installation using SQL Desktop Edition. But I get the following:
> SQLState = 08001, NativeError = 17
> Error = [Microsoft][ODBC SQL Server Driver][DBNETLIB] SQL Server does not
> exist or access denied.
> The only other difference I'm aware of aside from the SQL edition is that
an
> 'sa' password exists for the second environment. But I put the password
in
> the bcp command.
> Does anyone have an idea why the bcp command works in the one
> environment but not the other?
>
please have a look at
http://support.microsoft.com/default...B;EN-US;328306
it's possible that your 2nd environment does not accept SQL Server
authenticated connection... if this is the case, please have a look at
http://support.microsoft.com/default...b;en-us;285097 for further
info on how to hack the Windows Registry in order to allow SQL Server
quthenticated connections..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Problem using bcp with SQL MSDE

I successfully tested a bcp command similar to that below on a Small Business Manager database using SQL Enterprise Edition:
bcp "SELECT EMPLOYID FROM TWO..UPR00100" queryout testfile.txt -U login -P -C
I then tried using the same basic command for another Small Business Manager installation using SQL Desktop Edition. But I get the following:
SQLState = 08001, NativeError = 17
Error = [Microsoft][ODBC SQL Server Driver][DBNETLIB] SQL Server does not
exist or access denied.
The only other difference I'm aware of aside from the SQL edition is that an
'sa' password exists for the second environment. But I put the password in
the bcp command.
Does anyone have an idea why the bcp command works in the one
environment but not the other?
Thanks,
Tom
hi Tom,
"Tom Glasser" <Tom Glasser@.discussions.microsoft.com> ha scritto nel
messaggio news:3076FF6F-2708-4908-9149-6B0E148E6087@.microsoft.com...
> I successfully tested a bcp command similar to that below on a Small
Business Manager database using SQL Enterprise Edition:
> bcp "SELECT EMPLOYID FROM TWO..UPR00100" queryout testfile.txt -U
login -P -C
> I then tried using the same basic command for another Small Business
Manager installation using SQL Desktop Edition. But I get the following:
> SQLState = 08001, NativeError = 17
> Error = [Microsoft][ODBC SQL Server Driver][DBNETLIB] SQL Server does not
> exist or access denied.
> The only other difference I'm aware of aside from the SQL edition is that
an
> 'sa' password exists for the second environment. But I put the password
in
> the bcp command.
> Does anyone have an idea why the bcp command works in the one
> environment but not the other?
>
please have a look at
http://support.microsoft.com/default...B;EN-US;328306
it's possible that your 2nd environment does not accept SQL Server
authenticated connection... if this is the case, please have a look at
http://support.microsoft.com/default...b;en-us;285097 for further
info on how to hack the Windows Registry in order to allow SQL Server
quthenticated connections..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply