One thing I've noticed about the SQL Server Management Studio is that while
it allows you to create an alias for the server in the Registered Servers
window. That alias name is not propagated to the Object Browser. It seems
like it should be.
Michael Otey
Please ask this in the private SQL2005 group.
-Euan
Please reply only to the newsgroup so that others can benefit. When posting,
please state the version of SQL Server being used and the error number/exact
error message text received, if any.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Otey" <mikeo@.teca.com> wrote in message
news:#9xJG2abEHA.3716@.TK2MSFTNGP11.phx.gbl...
> One thing I've noticed about the SQL Server Management Studio is that
while
> it allows you to create an alias for the server in the Registered Servers
> window. That alias name is not propagated to the Object Browser. It seems
> like it should be.
> Michael Otey
>
|||Oops missed. Sorry about that.
"Euan Garden[MS]" <euang@.online.microsoft.com> wrote in message
news:u6T5IEebEHA.2340@.TK2MSFTNGP10.phx.gbl...
> Please ask this in the private SQL2005 group.
> --
> -Euan
> Please reply only to the newsgroup so that others can benefit. When
posting,
> please state the version of SQL Server being used and the error
number/exact
> error message text received, if any.
> This posting is provided "AS IS" with no warranties, and confers no
rights.[vbcol=seagreen]
> "Michael Otey" <mikeo@.teca.com> wrote in message
> news:#9xJG2abEHA.3716@.TK2MSFTNGP11.phx.gbl...
> while
Servers[vbcol=seagreen]
seems
>
Showing posts with label studio. Show all posts
Showing posts with label studio. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
Its the auto-hide - Re: microsoft visual studio cannot shut down because a modal dialog is activ
if i get this message one more time I am going to put my fist through my monitorWe are trying hard to get this to reliably reproduce. We think it is the dialog box that tells you that the data set needs to be released. Have you seen any patterns?|||I'm also having this annoying nag :(
I don't know if I have all the fetails but here it goes:
I'm developing useing:
visual studio 2005 (8.0.50727.42) and FW 2.0.50727
Microsoft sql server reporting services designers ver 9.00.1399.00
OS: windows XP professional, service pack 2
I'm useing a few parameters of type string and about 4-6 datasets.
Noting special about the report. just a table and textboxes.
I'm working with oracle database.
5 datasets, 7 parameter report
Didn't find any pattern but i think it my have something to do with source safe when it works with reporting services...|||
I get this a lot, we dont have sourcesafe..... Its a 3 button fix so far but would really appreciate a fix.
I get it everytime i try to debug a report using more than 1 param and the report has more than 1 dataset (2 used for Parameters)
|||Hi.I'm also working on report with more then one dataset and a few parameters.
What do you mean by "3 button fix"?
I'm just saving my work, check it in in vss and close the ssrs with ctrl+alt+del...
Ooo, did you mean ctrl+alt+del as the "3 button fix" ?
:)|||
:-) Yup!! 3 button being CTRL+ALT+DEL!!
I too am very close to losing a monitor out of the window!
|||For those of you reproing this issue, PLZ provide some info:
Build of RS Report Designer -- Shiloh, Yukon, Service Pack
OS -- Win2k, Win2k3, or XP
Report structure -- # and datatype of params, # of datasets, # and type of report items
Thanks!
|||Hello Mike,I don't know if I have all the fetails but here it goes:
I'm developing useing:
visual studio 2005 (8.0.50727.42) and FW 2.0.50727
Microsoft sql server reporting services designers ver 9.00.1399.00
OS: windows XP professional, service pack 2
I'm useing a few parameters of type string and about 4-6 datasets.
Noting special about the report. just a table and textboxes.
I'm working with oracle database.
Hope that helps,
Roy.|||
Thanks for the info.
So far all of the rep[ros I've seen have a common element which is Windows XP operating system. Does anyone have repro on some other OS?
Sorry for more questions than answers, but we're stumped on how to cause this to happen in our lab so we can debug it.
|||I am also getting this error on occassion.
I am developing a report with several subreports that use a string parameter (@.parameter | Fields!fieldname).
MS VS 2005 8.0.50727.42 (RTM.050727-4200)
MS .NET FRAMEWORK 2.0.50727
MS Windows XP Professional Version 2003 SP2
MS SQL Server Developer Edition 9.00.1399.06
|||I have received the error on both XP SP2 and the 6.0 release of Vista from MSDN.
I received it after running a report that runs two sub-reports with multiple parameters. I exported the report to Excel and then was unable to minimize the window. I realized then that it had occurred, so I saved my reports closed the solution and then received the message after trying to close the app.
It's hard to tell exactly when the problem occurs because you don't receive the error until you try to close the program (or when you notice a side-effect like it won't allow you to minimize the app anymore - at least in Vista).
|||I get it all the time too (less often now though), and had to CTRL-ALT-DELETE and kill the devenv.exe
Microsoft Windows XP Pro SP2
Microsoft SQL Server 2005 SP1 (on the servers, not locally)
MS Visual Studio 2005 Version 8.0.50727.42 (RTM.050727-4200)
MS .NET Framework Version 2.0.50727
Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00
Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00
Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00
I've been getting it often enough to find this thread.
Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00
XP SP2
No sourcesafe
I've gotten it on pretty simple reports, with just one dataset and a few string parameters. I just got it on a slightly more complex report with two datasets sharing a single string parameter. I also have windows (properties, output, etc) that refuse to autohide sometimes. I have to get rid of them by pinning and unpinning them. It may or may not be related, but this is certainly a tough bug to reproduce.
I have a feeling, likely incorrect, that it has something to do with switching to preview and then back to the layout without entering the parameter and viewing the preview.
|||I have this error on an almost daily basis. I also encounter the problem with windows autohiding correctly. Most of my reports have multiple parms and not all string based.
Running Visual Studio 2005 Version 8.0.50727.42
Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00
XP SP2
No sourcesafe
|||It just happened on me twice today5 datasets, 7 parameter report
One quick way to notice is when the keyboards stop working
CTRL+C, V, S just won't work (have to use to cut and paste, etc..)
Then I have to "close project", kill devenv.exe, then re-start the VS2005
Oh, I hate the often-not-working auto-hide (pin/unpin)
Its the auto-hide - Re: microsoft visual studio cannot shut down because a modal dialog is a
if i get this message one more time I am going to put my fist through my monitorWe are trying hard to get this to reliably reproduce. We think it is the dialog box that tells you that the data set needs to be released. Have you seen any patterns?|||I'm also having this annoying nag :(
I don't know if I have all the fetails but here it goes:
I'm developing useing:
visual studio 2005 (8.0.50727.42) and FW 2.0.50727
Microsoft sql server reporting services designers ver 9.00.1399.00
OS: windows XP professional, service pack 2
I'm useing a few parameters of type string and about 4-6 datasets.
Noting special about the report. just a table and textboxes.
I'm working with oracle database.
5 datasets, 7 parameter report
Didn't find any pattern but i think it my have something to do with source safe when it works with reporting services...|||
I get this a lot, we dont have sourcesafe..... Its a 3 button fix so far but would really appreciate a fix.
I get it everytime i try to debug a report using more than 1 param and the report has more than 1 dataset (2 used for Parameters)
|||Hi.I'm also working on report with more then one dataset and a few parameters.
What do you mean by "3 button fix"?
I'm just saving my work, check it in in vss and close the ssrs with ctrl+alt+del...
Ooo, did you mean ctrl+alt+del as the "3 button fix" ?
:)|||
:-) Yup!! 3 button being CTRL+ALT+DEL!!
I too am very close to losing a monitor out of the window!
|||For those of you reproing this issue, PLZ provide some info:
Build of RS Report Designer -- Shiloh, Yukon, Service Pack
OS -- Win2k, Win2k3, or XP
Report structure -- # and datatype of params, # of datasets, # and type of report items
Thanks!
|||Hello Mike,I don't know if I have all the fetails but here it goes:
I'm developing useing:
visual studio 2005 (8.0.50727.42) and FW 2.0.50727
Microsoft sql server reporting services designers ver 9.00.1399.00
OS: windows XP professional, service pack 2
I'm useing a few parameters of type string and about 4-6 datasets.
Noting special about the report. just a table and textboxes.
I'm working with oracle database.
Hope that helps,
Roy.|||
Thanks for the info.
So far all of the rep[ros I've seen have a common element which is Windows XP operating system. Does anyone have repro on some other OS?
Sorry for more questions than answers, but we're stumped on how to cause this to happen in our lab so we can debug it.
|||I am also getting this error on occassion.
I am developing a report with several subreports that use a string parameter (@.parameter | Fields!fieldname).
MS VS 2005 8.0.50727.42 (RTM.050727-4200)
MS .NET FRAMEWORK 2.0.50727
MS Windows XP Professional Version 2003 SP2
MS SQL Server Developer Edition 9.00.1399.06
|||I have received the error on both XP SP2 and the 6.0 release of Vista from MSDN.
I received it after running a report that runs two sub-reports with multiple parameters. I exported the report to Excel and then was unable to minimize the window. I realized then that it had occurred, so I saved my reports closed the solution and then received the message after trying to close the app.
It's hard to tell exactly when the problem occurs because you don't receive the error until you try to close the program (or when you notice a side-effect like it won't allow you to minimize the app anymore - at least in Vista).
|||I get it all the time too (less often now though), and had to CTRL-ALT-DELETE and kill the devenv.exe
Microsoft Windows XP Pro SP2
Microsoft SQL Server 2005 SP1 (on the servers, not locally)
MS Visual Studio 2005 Version 8.0.50727.42 (RTM.050727-4200)
MS .NET Framework Version 2.0.50727
Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00
Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00
Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00
I've been getting it often enough to find this thread.
Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00
XP SP2
No sourcesafe
I've gotten it on pretty simple reports, with just one dataset and a few string parameters. I just got it on a slightly more complex report with two datasets sharing a single string parameter. I also have windows (properties, output, etc) that refuse to autohide sometimes. I have to get rid of them by pinning and unpinning them. It may or may not be related, but this is certainly a tough bug to reproduce.
I have a feeling, likely incorrect, that it has something to do with switching to preview and then back to the layout without entering the parameter and viewing the preview.
|||I have this error on an almost daily basis. I also encounter the problem with windows autohiding correctly. Most of my reports have multiple parms and not all string based.
Running Visual Studio 2005 Version 8.0.50727.42
Microsoft SQL Server Reporting Services Designers
Version 9.00.1399.00
XP SP2
No sourcesafe
|||It just happened on me twice today5 datasets, 7 parameter report
One quick way to notice is when the keyboards stop working
CTRL+C, V, S just won't work (have to use to cut and paste, etc..)
Then I have to "close project", kill devenv.exe, then re-start the VS2005
Oh, I hate the often-not-working auto-hide (pin/unpin)sql
Friday, March 23, 2012
It seems a bug of SQL Server 2005.
I do the following steps:
1:Use Manage Studio login the server with Integrated security.
2:Create a dabase named testdb;
3:Create a SQL Server login named amber ,and set it to be dbowner of testdb;
4:Create a SQL Server login named guxiaobo ,set it's default databse to be testbd,and in the testdb databse map login guxiaobo to user guxiaobo;
5:Close Manage Studio and reopen it ,this time use login amber log to the server.
6:In database testbd create a databse role role1 owned by dbo;
7:In database testdb create a schema schema1 owned by dbo;
8:Set user guxiaobo to be member of role1,and set guxiaobo's default schema to be schema1;
9:In the schema properties-schema1 dialog choose permissions,in the users or roles listview I add role1 to it.in the explicit permissions for role1 listbox,I choose select /update/insert/delete/view definition grant checkboxes.and apply the selects.
10:In the schema1 schema I create a table:create table a(a int ,b varchar(10));
11:In the dabase role properties-role1 dialog choose securables panel ,int securable listview I add the schema1.a table,and in explicit permissions for schema1.a I choose all for grant ,then apply the selects.
12:Now I use login guxiaobo to log into dabase and issue "select * from a",but got a error msg saying guxiaobo has not enough permission to select form table a.
Does anyone has found anything I missed?
And in step 11 ,I choose all the columns of table a for all permissions.|||Anybody helps ?Wednesday, March 21, 2012
Issues with SourceSafe integration with Sql Server Management Stud
We have a Sql Server Manageent Studio Solution, that on loading gives the
following error:
[ Source Control ]
There appears to be a discrepancy between the solution's source control
information about some project(s) and the information in the project file(s)
.
To resolve this discrepency it will be necessary to check out the project
file(s) and update them. If the check out fails, however, and the solution i
s
closed without saving, you will see this warning again the next time you ope
n
the solution.
[ OK ] [ Help ]
After which it sucessfully checks out one of the projects within the
solution, but makes no changes to it. Is the user (i.e. me) expected to do
something to resolve the issue?
I've tried unbinding source control fro the project that gets checked out,
saved all, rebound, saved all, to no avail.
None of the projects are shared with any other solution files nor are they
shared within VSS.
My normal avenues of finding the cause for these things is coming up blank
-- possibly because the Ctrl+C to copy the text of the error message does no
t
work (presumeably the error dialog is not created with the MessageBox API,
per http://blogs.msdn.com/oldnewthing/a.../29/412577.aspx )Hi Rowland,
Thank you for your posting!
To keep the integrity of newsgroup, we encourage you post only one post in
the newsgroup so that other communities may also benefit from this. We will
reply the post in microsoft.public.vstudio.sourcesafe and follow up your
any questions there.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
following error:
[ Source Control ]
There appears to be a discrepancy between the solution's source control
information about some project(s) and the information in the project file(s)
.
To resolve this discrepency it will be necessary to check out the project
file(s) and update them. If the check out fails, however, and the solution i
s
closed without saving, you will see this warning again the next time you ope
n
the solution.
[ OK ] [ Help ]
After which it sucessfully checks out one of the projects within the
solution, but makes no changes to it. Is the user (i.e. me) expected to do
something to resolve the issue?
I've tried unbinding source control fro the project that gets checked out,
saved all, rebound, saved all, to no avail.
None of the projects are shared with any other solution files nor are they
shared within VSS.
My normal avenues of finding the cause for these things is coming up blank
-- possibly because the Ctrl+C to copy the text of the error message does no
t
work (presumeably the error dialog is not created with the MessageBox API,
per http://blogs.msdn.com/oldnewthing/a.../29/412577.aspx )Hi Rowland,
Thank you for your posting!
To keep the integrity of newsgroup, we encourage you post only one post in
the newsgroup so that other communities may also benefit from this. We will
reply the post in microsoft.public.vstudio.sourcesafe and follow up your
any questions there.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Monday, March 19, 2012
Issues with connecting from .NET to Sybase ASE 12
If anyone out there has been successful in connecting to Sybase ASE 12
from Visual Studio .NET 2003 either in a Windows Forms or Reporting
Services project, can you please help me.
...
In summary, I wish to:
(a) create a Windows Forms application using VB.NET (Visual Studio
.NET 2003 and .NET Framework 1.1) that will connect to Sybase ASE 12.0
to execute stored procedures.
(b) create a SQL Server Reporting Services report using Visual Studio
.NET 2003, .NET Framework 1.1 and SQL Server Reporting Services that
will connect to Sybase ASE 12.0 also via stored procedures.
I have Sybase 12 Client installed on my development machine and am
able to connect to a test server from this machine using SQL
Advantage.
My code for (a) is:
>>
Dim sybaseconn As System.Data.OleDb.OleDbConnection
Dim sybaseconnstring As String = "Provider=Sybase.ASEOLEDBProvider;Server Name=XXXXXX;Initial
Catalog=YYYYYY;User ID=UUUUUU;Password=PPPPPP;"
Try
sybaseconn = New System.Data.OleDb.OleDbConnection(sybaseconnstring)
sybaseconn.Open()
Catch ex As Exception
MsgBox(ex.Message)
Finally
Select Case sybaseconn.State
Case ConnectionState.Broken, ConnectionState.Closed
Case Else
sybaseconn.Close()
sybaseconn.Dispose()
End Select
sybaseconn = Nothing
End Try
>>
When I run this, I receive the following message on the Open() line:
"The 'Sybase.ASEOLEDBProvider' provider is not registered on the local
machine."
and this is the exception:
?ex
{System.InvalidOperationException}
[System.InvalidOperationException]:
{System.InvalidOperationException}
HelpLink: Nothing
InnerException: {System.Data.OleDb.OleDbException}
Message: "The 'Sybase.ASEOLEDBProvider' provider is not registered
on the local machine."
Source: "System.Data"
StackTrace: " at
System.Data.OleDb.OleDbConnection.CreateProviderError(Int32 hr)
at System.Data.OleDb.OleDbConnection.CreateProvider(OleDbConnectionString
constr)
at System.Data.OleDb.OleDbConnection.Open()
at Sybase_Stuff.Form1.Button1_Click(Object sender, EventArgs e) in
C:\Documents and Settings\allchini\My Documents\Visual Studio
Projects\Sybase Stuff\Form1.vb:line 98"
TargetSite: {System.Reflection.RuntimeMethodInfo}
My problem with (b) is as follows:
In my Reporting Services project in Visual Studio .NET 2003 I attempt
to set up a shared data source by selecting Add New Datasource. This
displays the Data Link Properties dialog. On the Provider tab, I
select "Sybase ASE OLE DB Provider". When I press Next or OK, I
receive the following message:
Microsoft Data Link Error
Provider is no longer available. Ensure that the provider is
installed properly.
Can you tell me how to achieve (a) and/ or (b)?
Thanks
Ian AllchinFurther to my earlier posting, I contacted Sybase who were helpful. I
have resolved the first issue. My Sybase installation was corrupted,
so I uninstalled completely. I then installed Sybase ASE 12.5.2 PC
Client which includes the ASE ADO .NET Provider. I have been able to
write a .NET Windows Forms application using this provider in very
much the same way as the SQL Server .NET Provider.
Information about the Sybase ASE .NET Data Provider can be found at:
http://sybooks.sybase.com/onlinebooks/group-adonet/asnetg0110e/adonet
I AM STILL LOOKING FOR HELP ON HOW TO CONNECT TO SYBASE ASE 12 FROM A
SQL SERVER REPORTING SERVICES PROJECT. PLEASE RESPOND IF YOU HAVE ANY
INFORMATION.
Ian Allchin
Alpha Ventures Limited, UK|||I have not done it myself, but this should get you started with using Sybase
ASE 12 in Reporting Services:
* First, you have to make sure the ASE data provider is installed correctly,
so that the report designer in VS.NET and report server inside ASP.NET are
able to load the dlls of the data provider at runtime. Note: there could be
file system permissions issues which prevent ASP.NET from accessing the ASE
data provider dlls. You might want to try to copy the dlls directly into the
report designer and report server installation directories.
* close down all VS.NET sessions before modifying rsReportDesigner.config
* backup the existing rsReportDesigner.config and rsReportServer.config
* Add these entries to rsReportDesigner.config in the Data section:
<Extension Name="Sybase"
Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
... and in the Designer section:
<Extension Name="Sybase"
Type="Microsoft.ReportDesigner.Design.GenericQueryDesigner,Microsoft.Reporti
ngServices.Designer"/>
* Stop the ReportServer Windows service
* Add this entry to rsReportServer.config in the Data section:
<Extension Name="Sybase"
Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
* Restart ReportServer Windows service
* Reset IIS/ASP.NET by running iisreset from the command line
There are several people on this newsgroups who have indicated they are
using Sybase. Not sure if they have tried the managed Sybase provider.
You might also want to read this thread:
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=f02812e9-65de-4007-a142-b689522d4c93&sloc=en-us
As indicated in the thread, it should work on the report server, but I'm not
sure about the report designer. It will depend on how the Sybase ASE
provider is implemented internally.
Documentation on the config files:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
Robert M. Bruckner
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ian Allchin" <ian.allchin@.talk21.com> wrote in message
news:1f2dd58b.0408050554.4a18275d@.posting.google.com...
> Further to my earlier posting, I contacted Sybase who were helpful. I
> have resolved the first issue. My Sybase installation was corrupted,
> so I uninstalled completely. I then installed Sybase ASE 12.5.2 PC
> Client which includes the ASE ADO .NET Provider. I have been able to
> write a .NET Windows Forms application using this provider in very
> much the same way as the SQL Server .NET Provider.
> Information about the Sybase ASE .NET Data Provider can be found at:
> http://sybooks.sybase.com/onlinebooks/group-adonet/asnetg0110e/adonet
> I AM STILL LOOKING FOR HELP ON HOW TO CONNECT TO SYBASE ASE 12 FROM A
> SQL SERVER REPORTING SERVICES PROJECT. PLEASE RESPOND IF YOU HAVE ANY
> INFORMATION.
> Ian Allchin
> Alpha Ventures Limited, UK|||I have used both the ODBC and OLEDB providers. I have not used the dotnet
managed provider. Correct me if I am wrong but it would only use the
provider if you used the generic designer. At runtime it would use it but
during development only the oledb provider?
Bruce L-C
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:%233M8BkweEHA.2028@.tk2msftngp13.phx.gbl...
> I have not done it myself, but this should get you started with using
Sybase
> ASE 12 in Reporting Services:
> * First, you have to make sure the ASE data provider is installed
correctly,
> so that the report designer in VS.NET and report server inside ASP.NET are
> able to load the dlls of the data provider at runtime. Note: there could
be
> file system permissions issues which prevent ASP.NET from accessing the
ASE
> data provider dlls. You might want to try to copy the dlls directly into
the
> report designer and report server installation directories.
> * close down all VS.NET sessions before modifying rsReportDesigner.config
> * backup the existing rsReportDesigner.config and rsReportServer.config
> * Add these entries to rsReportDesigner.config in the Data section:
> <Extension Name="Sybase"
> Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
> ... and in the Designer section:
> <Extension Name="Sybase"
>
Type="Microsoft.ReportDesigner.Design.GenericQueryDesigner,Microsoft.Reporti
> ngServices.Designer"/>
> * Stop the ReportServer Windows service
> * Add this entry to rsReportServer.config in the Data section:
> <Extension Name="Sybase"
> Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
> * Restart ReportServer Windows service
> * Reset IIS/ASP.NET by running iisreset from the command line
> There are several people on this newsgroups who have indicated they are
> using Sybase. Not sure if they have tried the managed Sybase provider.
> You might also want to read this thread:
>
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=f02812e9-65de-4007-a142-b689522d4c93&sloc=en-us
> As indicated in the thread, it should work on the report server, but I'm
not
> sure about the report designer. It will depend on how the Sybase ASE
> provider is implemented internally.
> Documentation on the config files:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
>
> --
> Robert M. Bruckner
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Ian Allchin" <ian.allchin@.talk21.com> wrote in message
> news:1f2dd58b.0408050554.4a18275d@.posting.google.com...
> > Further to my earlier posting, I contacted Sybase who were helpful. I
> > have resolved the first issue. My Sybase installation was corrupted,
> > so I uninstalled completely. I then installed Sybase ASE 12.5.2 PC
> > Client which includes the ASE ADO .NET Provider. I have been able to
> > write a .NET Windows Forms application using this provider in very
> > much the same way as the SQL Server .NET Provider.
> >
> > Information about the Sybase ASE .NET Data Provider can be found at:
> >
> > http://sybooks.sybase.com/onlinebooks/group-adonet/asnetg0110e/adonet
> >
> > I AM STILL LOOKING FOR HELP ON HOW TO CONNECT TO SYBASE ASE 12 FROM A
> > SQL SERVER REPORTING SERVICES PROJECT. PLEASE RESPOND IF YOU HAVE ANY
> > INFORMATION.
> >
> > Ian Allchin
> > Alpha Ventures Limited, UK
>|||If you register any managed data provider in report designer and select it
in the data source dialog, the designer will only enable the generic query
designer. The toggle icon for the visual query designer will be disabled
(because the visual query designer is not capable of working with managed
data providers right now as discussed in the referenced thread below).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:O$iOYRxeEHA.1356@.TK2MSFTNGP09.phx.gbl...
> I have used both the ODBC and OLEDB providers. I have not used the dotnet
> managed provider. Correct me if I am wrong but it would only use the
> provider if you used the generic designer. At runtime it would use it but
> during development only the oledb provider?
> Bruce L-C
> "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> news:%233M8BkweEHA.2028@.tk2msftngp13.phx.gbl...
> > I have not done it myself, but this should get you started with using
> Sybase
> > ASE 12 in Reporting Services:
> >
> > * First, you have to make sure the ASE data provider is installed
> correctly,
> > so that the report designer in VS.NET and report server inside ASP.NET
are
> > able to load the dlls of the data provider at runtime. Note: there could
> be
> > file system permissions issues which prevent ASP.NET from accessing the
> ASE
> > data provider dlls. You might want to try to copy the dlls directly into
> the
> > report designer and report server installation directories.
> >
> > * close down all VS.NET sessions before modifying
rsReportDesigner.config
> > * backup the existing rsReportDesigner.config and rsReportServer.config
> >
> > * Add these entries to rsReportDesigner.config in the Data section:
> > <Extension Name="Sybase"
> > Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
> > ... and in the Designer section:
> > <Extension Name="Sybase"
> >
>
Type="Microsoft.ReportDesigner.Design.GenericQueryDesigner,Microsoft.Reporti
> > ngServices.Designer"/>
> >
> > * Stop the ReportServer Windows service
> > * Add this entry to rsReportServer.config in the Data section:
> > <Extension Name="Sybase"
> > Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
> > * Restart ReportServer Windows service
> > * Reset IIS/ASP.NET by running iisreset from the command line
> >
> > There are several people on this newsgroups who have indicated they are
> > using Sybase. Not sure if they have tried the managed Sybase provider.
> >
> > You might also want to read this thread:
> >
>
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=f02812e9-65de-4007-a142-b689522d4c93&sloc=en-us
> > As indicated in the thread, it should work on the report server, but I'm
> not
> > sure about the report designer. It will depend on how the Sybase ASE
> > provider is implemented internally.
> >
> > Documentation on the config files:
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
> >
> >
> > --
> > Robert M. Bruckner
> > Microsoft SQL Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "Ian Allchin" <ian.allchin@.talk21.com> wrote in message
> > news:1f2dd58b.0408050554.4a18275d@.posting.google.com...
> > > Further to my earlier posting, I contacted Sybase who were helpful. I
> > > have resolved the first issue. My Sybase installation was corrupted,
> > > so I uninstalled completely. I then installed Sybase ASE 12.5.2 PC
> > > Client which includes the ASE ADO .NET Provider. I have been able to
> > > write a .NET Windows Forms application using this provider in very
> > > much the same way as the SQL Server .NET Provider.
> > >
> > > Information about the Sybase ASE .NET Data Provider can be found at:
> > >
> > > http://sybooks.sybase.com/onlinebooks/group-adonet/asnetg0110e/adonet
> > >
> > > I AM STILL LOOKING FOR HELP ON HOW TO CONNECT TO SYBASE ASE 12 FROM A
> > > SQL SERVER REPORTING SERVICES PROJECT. PLEASE RESPOND IF YOU HAVE ANY
> > > INFORMATION.
> > >
> > > Ian Allchin
> > > Alpha Ventures Limited, UK
> >
> >
>|||First of all thanks to Robert and Bruce for your comments. The DBA
and I have followed the instructions regarding modifying the designer
and server installations, have made some progress on this issue but
are still experiencing some problems ...
On the server, the Sybase .NET provider does not appear in the list of
available connection types within the New Data Source page. We still
just have: Microsoft SQL Server, OLE DB, Oracle and ODBC.
On the client, I have some mixed results:
Sybase IS available as a type in the shared datasource dialog. This
looked encouraging to start with.
I have set up a shared datasource using a connection that I know works
with the ASE .NET provider (tested in a Windows Forms project) and
then tried to used that shared datasource.
When I create a new dataset, with the shared dataset, the only command
type that is available is text (whereas for SQL Server there are 3
options including Stored Procedure).
Within the Generic Query Designer, the Stored Procedure command type
is available.
When I try to create a dataset using a simple text command such as
"SELECT field1 FROM dbo.table1", field1 appears in the field list and
if I press the exclamation mark button field1 is retrieved from the
database OK. However, if I add field1 into a table on the layout tab
and then try to switch to the preview tab, I receive the following
error message:
An error has occurred during report processing.
Operation is not valid due to the current state of the object.
I have also attempted various ways of executing a Sybase stored
procedure with a single integer parameter, using both text and stored
procedure command types, none of which will preview. The most common
message I receive is:
The procedure expected paramater <@.param_name> which was not provided.
Since it is recognising it is a procedure, and picking up the expected
parameter, this also seems promising, but there appear to be mapping
problems.
Ultimately, I want to re-use existing Sybase stored procedures (with
parameters of various data types) within reporting services, so I need
to resolve this.
Any help would be greatly appreciated.
Ian Allchin
Alpha Ventures Limited, UK|||Hi Santiago
Your posting sounds as if you are having some success as you say "it
works". I am also having some issues as described in my most recent
posting on 20 August 2004. For me, reports where the dataset is built
from even text commands and stored procedures with or without
parameters are not working (although if I press the exclamation mark
button, the rows are returned in the grid at the bottom of the generic
query designer). Are you experiencing the same problems or have you
managed to successfully preview or deploy any reports using the Sybase
.NET Provider? If you have, I would be really grateful if you would
describe exactly how you have done it.
If I have any more news, I will post back.
Many thanks
Ian Allchin
Alpha Ventures Limited, UK|||If you can't get the dotnet provider working then I suggest trying the ODBC
or the OLEDB provider. I had an issue with the OLEDB provider, if you setup
multiple OLEDB sources it always wants to use the first one. The Sybase site
had a workaround but it did not work for me (maybe I didn't implement the
workaround correctly). I didn't want to waste anymore time so I went with
the ODBC. The ODBC has worked well and consistantly for me. The only issue I
have had is with stored procedure with parameters. I am currently going
against 11.9.2 backend with a 12.5.2 client. I am upgrading the server to
12.5.2 shortly and hope that the stored procedure problem goes away (I
believe someone that had posted previously had stored procedures working
with ODBC against a 12.5 server). Anyway, I suggest giving the ODBC driver a
chance.
Wait a minute, I just re-read your posting there. You say you get rows
returned. Have you tried the refresh fields button (it looks like the
refresh a web page button in IE). Try that and see if you get your field
list. If you are returning rows then things should be OK.
Bruce L-C
"Ian Allchin" <ian.allchin@.talk21.com> wrote in message
news:1f2dd58b.0408212332.32a40752@.posting.google.com...
> Hi Santiago
> Your posting sounds as if you are having some success as you say "it
> works". I am also having some issues as described in my most recent
> posting on 20 August 2004. For me, reports where the dataset is built
> from even text commands and stored procedures with or without
> parameters are not working (although if I press the exclamation mark
> button, the rows are returned in the grid at the bottom of the generic
> query designer). Are you experiencing the same problems or have you
> managed to successfully preview or deploy any reports using the Sybase
> .NET Provider? If you have, I would be really grateful if you would
> describe exactly how you have done it.
> If I have any more news, I will post back.
> Many thanks
> Ian Allchin
> Alpha Ventures Limited, UK|||Bruce
Thanks for the information regarding ODBC and OLEDB. I have already
tried OLEDB with some success (ie I did manage to call stored
procedures and preview reports), although I had some minor issues with
using 12.5.2 client against 12.0 server. I will revisit this and ODBC
if I cannot resolve the current issues with the ADO .NET route, which
I what Sybase recommended.
My current situation with the ADO .NET provider is that I can connect
to a database and execute a non parameterised text command within the
generic query designer - eg SELECT * FROM tablename. My field list
appears without me pressing refresh fields and if I press the
exclamation mark button I see my rows returned to the grid. However,
when I add fields to a table control on the layout tab and then try to
switch to the preview tab, I receive an error message:
An error has occurred during report processing.
Operation is not valid due to the current state of the object.
I have also tried EXEC storedprocedurename 1 (where 1 is a hard coded
argument) as a text command. Reporting services brings back my
expected field list and returns rows in the grid. However, when I add
fields to a table control on the layout tab and then try to switch to
the preview tab, I receive the same error message.
The reason I am using text commands is that this appears to be the
only option that is fully available and other attempts to deal with
stored procedures have caused different error messages (see my posting
20 August 2004).
Stop Press:
I am able to build and deploy the report. When selecting the report
on the portal, I receive a more detailed error message:
An error has occurred during report processing. (rsProcessingAborted)
An attempt has been made to use a data extension 'Sybase' that is not
registered for this report server. (rsDataExtensionNotFound)
OK, so that may explain the "invalid state of the object".
Does anyone know what we have to do to register it correctly? Also,
should the stored procedure option be available as a command type like
with SQL Server?
Thanks
Ian Allchin
Alpha Ventures Limited UK|||Sorry I can't help anymore with this. I would like to use the dotnet
provider for Sybase as well if it can be made to work.
Bruce L-C
"Ian Allchin" <ian.allchin@.talk21.com> wrote in message
news:1f2dd58b.0408230016.50afd7ac@.posting.google.com...
> Bruce
> Thanks for the information regarding ODBC and OLEDB. I have already
> tried OLEDB with some success (ie I did manage to call stored
> procedures and preview reports), although I had some minor issues with
> using 12.5.2 client against 12.0 server. I will revisit this and ODBC
> if I cannot resolve the current issues with the ADO .NET route, which
> I what Sybase recommended.
> My current situation with the ADO .NET provider is that I can connect
> to a database and execute a non parameterised text command within the
> generic query designer - eg SELECT * FROM tablename. My field list
> appears without me pressing refresh fields and if I press the
> exclamation mark button I see my rows returned to the grid. However,
> when I add fields to a table control on the layout tab and then try to
> switch to the preview tab, I receive an error message:
> An error has occurred during report processing.
> Operation is not valid due to the current state of the object.
> I have also tried EXEC storedprocedurename 1 (where 1 is a hard coded
> argument) as a text command. Reporting services brings back my
> expected field list and returns rows in the grid. However, when I add
> fields to a table control on the layout tab and then try to switch to
> the preview tab, I receive the same error message.
> The reason I am using text commands is that this appears to be the
> only option that is fully available and other attempts to deal with
> stored procedures have caused different error messages (see my posting
> 20 August 2004).
> Stop Press:
> I am able to build and deploy the report. When selecting the report
> on the portal, I receive a more detailed error message:
> An error has occurred during report processing. (rsProcessingAborted)
> An attempt has been made to use a data extension 'Sybase' that is not
> registered for this report server. (rsDataExtensionNotFound)
> OK, so that may explain the "invalid state of the object".
> Does anyone know what we have to do to register it correctly? Also,
> should the stored procedure option be available as a command type like
> with SQL Server?
> Thanks
> Ian Allchin
> Alpha Ventures Limited UK|||I have now had a response from Microsoft technical support. They said
that the Sybase ADO .NET Provider is not a Reporting Services Data
Extension. These are two different things. Sybase would need to
provide a Reporting Services Data Extension.
The Microsoft technical support person recommended trying OLEDB and
only using ODBC if OLEDB was unsuccessful. I intend to follow this
advice, but I will also contact Sybase and ask if they have any plans
to provide a Reporting Services Data Extension and post back.
Ian Allchin
Alpha Ventures Limited, UK|||Interesting. I thought all that was needed was a dotnet data provider.
Didn't know that it was more than that. Thanks for posting back on this.
Bruce L-C
"Ian Allchin" <ian.allchin@.talk21.com> wrote in message
news:1f2dd58b.0408240942.262fd3a1@.posting.google.com...
> I have now had a response from Microsoft technical support. They said
> that the Sybase ADO .NET Provider is not a Reporting Services Data
> Extension. These are two different things. Sybase would need to
> provide a Reporting Services Data Extension.
> The Microsoft technical support person recommended trying OLEDB and
> only using ODBC if OLEDB was unsuccessful. I intend to follow this
> advice, but I will also contact Sybase and ask if they have any plans
> to provide a Reporting Services Data Extension and post back.
> Ian Allchin
> Alpha Ventures Limited, UK|||I have contacted Sybase. They are now considering whether to
implement a Reporting Services Data Extension. A decision is expected
within the next few months and I will post back if I receive any news
on this. In the meantime, I will be going back to try OLEDB and ODBC.
Ian Allchin
Alpha Ventures Limited, UK|||Thanks for the update. If you have any problems with either OLEDB or ODBC
post back here. I have used ODBC extensively with Sybase and am now
migrating to 12.5.2. Others have used OLEDB successfully (and I will be
giving that a try shortly as well).
Thanks again, now I won't waste any time with with the dotnet provider.
Bruce L-C
"Ian Allchin" <ian.allchin@.talk21.com> wrote in message
news:1f2dd58b.0409060212.3f64dffb@.posting.google.com...
>I have contacted Sybase. They are now considering whether to
> implement a Reporting Services Data Extension. A decision is expected
> within the next few months and I will post back if I receive any news
> on this. In the meantime, I will be going back to try OLEDB and ODBC.
> Ian Allchin
> Alpha Ventures Limited, UK
from Visual Studio .NET 2003 either in a Windows Forms or Reporting
Services project, can you please help me.
...
In summary, I wish to:
(a) create a Windows Forms application using VB.NET (Visual Studio
.NET 2003 and .NET Framework 1.1) that will connect to Sybase ASE 12.0
to execute stored procedures.
(b) create a SQL Server Reporting Services report using Visual Studio
.NET 2003, .NET Framework 1.1 and SQL Server Reporting Services that
will connect to Sybase ASE 12.0 also via stored procedures.
I have Sybase 12 Client installed on my development machine and am
able to connect to a test server from this machine using SQL
Advantage.
My code for (a) is:
>>
Dim sybaseconn As System.Data.OleDb.OleDbConnection
Dim sybaseconnstring As String = "Provider=Sybase.ASEOLEDBProvider;Server Name=XXXXXX;Initial
Catalog=YYYYYY;User ID=UUUUUU;Password=PPPPPP;"
Try
sybaseconn = New System.Data.OleDb.OleDbConnection(sybaseconnstring)
sybaseconn.Open()
Catch ex As Exception
MsgBox(ex.Message)
Finally
Select Case sybaseconn.State
Case ConnectionState.Broken, ConnectionState.Closed
Case Else
sybaseconn.Close()
sybaseconn.Dispose()
End Select
sybaseconn = Nothing
End Try
>>
When I run this, I receive the following message on the Open() line:
"The 'Sybase.ASEOLEDBProvider' provider is not registered on the local
machine."
and this is the exception:
?ex
{System.InvalidOperationException}
[System.InvalidOperationException]:
{System.InvalidOperationException}
HelpLink: Nothing
InnerException: {System.Data.OleDb.OleDbException}
Message: "The 'Sybase.ASEOLEDBProvider' provider is not registered
on the local machine."
Source: "System.Data"
StackTrace: " at
System.Data.OleDb.OleDbConnection.CreateProviderError(Int32 hr)
at System.Data.OleDb.OleDbConnection.CreateProvider(OleDbConnectionString
constr)
at System.Data.OleDb.OleDbConnection.Open()
at Sybase_Stuff.Form1.Button1_Click(Object sender, EventArgs e) in
C:\Documents and Settings\allchini\My Documents\Visual Studio
Projects\Sybase Stuff\Form1.vb:line 98"
TargetSite: {System.Reflection.RuntimeMethodInfo}
My problem with (b) is as follows:
In my Reporting Services project in Visual Studio .NET 2003 I attempt
to set up a shared data source by selecting Add New Datasource. This
displays the Data Link Properties dialog. On the Provider tab, I
select "Sybase ASE OLE DB Provider". When I press Next or OK, I
receive the following message:
Microsoft Data Link Error
Provider is no longer available. Ensure that the provider is
installed properly.
Can you tell me how to achieve (a) and/ or (b)?
Thanks
Ian AllchinFurther to my earlier posting, I contacted Sybase who were helpful. I
have resolved the first issue. My Sybase installation was corrupted,
so I uninstalled completely. I then installed Sybase ASE 12.5.2 PC
Client which includes the ASE ADO .NET Provider. I have been able to
write a .NET Windows Forms application using this provider in very
much the same way as the SQL Server .NET Provider.
Information about the Sybase ASE .NET Data Provider can be found at:
http://sybooks.sybase.com/onlinebooks/group-adonet/asnetg0110e/adonet
I AM STILL LOOKING FOR HELP ON HOW TO CONNECT TO SYBASE ASE 12 FROM A
SQL SERVER REPORTING SERVICES PROJECT. PLEASE RESPOND IF YOU HAVE ANY
INFORMATION.
Ian Allchin
Alpha Ventures Limited, UK|||I have not done it myself, but this should get you started with using Sybase
ASE 12 in Reporting Services:
* First, you have to make sure the ASE data provider is installed correctly,
so that the report designer in VS.NET and report server inside ASP.NET are
able to load the dlls of the data provider at runtime. Note: there could be
file system permissions issues which prevent ASP.NET from accessing the ASE
data provider dlls. You might want to try to copy the dlls directly into the
report designer and report server installation directories.
* close down all VS.NET sessions before modifying rsReportDesigner.config
* backup the existing rsReportDesigner.config and rsReportServer.config
* Add these entries to rsReportDesigner.config in the Data section:
<Extension Name="Sybase"
Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
... and in the Designer section:
<Extension Name="Sybase"
Type="Microsoft.ReportDesigner.Design.GenericQueryDesigner,Microsoft.Reporti
ngServices.Designer"/>
* Stop the ReportServer Windows service
* Add this entry to rsReportServer.config in the Data section:
<Extension Name="Sybase"
Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
* Restart ReportServer Windows service
* Reset IIS/ASP.NET by running iisreset from the command line
There are several people on this newsgroups who have indicated they are
using Sybase. Not sure if they have tried the managed Sybase provider.
You might also want to read this thread:
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=f02812e9-65de-4007-a142-b689522d4c93&sloc=en-us
As indicated in the thread, it should work on the report server, but I'm not
sure about the report designer. It will depend on how the Sybase ASE
provider is implemented internally.
Documentation on the config files:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
Robert M. Bruckner
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ian Allchin" <ian.allchin@.talk21.com> wrote in message
news:1f2dd58b.0408050554.4a18275d@.posting.google.com...
> Further to my earlier posting, I contacted Sybase who were helpful. I
> have resolved the first issue. My Sybase installation was corrupted,
> so I uninstalled completely. I then installed Sybase ASE 12.5.2 PC
> Client which includes the ASE ADO .NET Provider. I have been able to
> write a .NET Windows Forms application using this provider in very
> much the same way as the SQL Server .NET Provider.
> Information about the Sybase ASE .NET Data Provider can be found at:
> http://sybooks.sybase.com/onlinebooks/group-adonet/asnetg0110e/adonet
> I AM STILL LOOKING FOR HELP ON HOW TO CONNECT TO SYBASE ASE 12 FROM A
> SQL SERVER REPORTING SERVICES PROJECT. PLEASE RESPOND IF YOU HAVE ANY
> INFORMATION.
> Ian Allchin
> Alpha Ventures Limited, UK|||I have used both the ODBC and OLEDB providers. I have not used the dotnet
managed provider. Correct me if I am wrong but it would only use the
provider if you used the generic designer. At runtime it would use it but
during development only the oledb provider?
Bruce L-C
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:%233M8BkweEHA.2028@.tk2msftngp13.phx.gbl...
> I have not done it myself, but this should get you started with using
Sybase
> ASE 12 in Reporting Services:
> * First, you have to make sure the ASE data provider is installed
correctly,
> so that the report designer in VS.NET and report server inside ASP.NET are
> able to load the dlls of the data provider at runtime. Note: there could
be
> file system permissions issues which prevent ASP.NET from accessing the
ASE
> data provider dlls. You might want to try to copy the dlls directly into
the
> report designer and report server installation directories.
> * close down all VS.NET sessions before modifying rsReportDesigner.config
> * backup the existing rsReportDesigner.config and rsReportServer.config
> * Add these entries to rsReportDesigner.config in the Data section:
> <Extension Name="Sybase"
> Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
> ... and in the Designer section:
> <Extension Name="Sybase"
>
Type="Microsoft.ReportDesigner.Design.GenericQueryDesigner,Microsoft.Reporti
> ngServices.Designer"/>
> * Stop the ReportServer Windows service
> * Add this entry to rsReportServer.config in the Data section:
> <Extension Name="Sybase"
> Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
> * Restart ReportServer Windows service
> * Reset IIS/ASP.NET by running iisreset from the command line
> There are several people on this newsgroups who have indicated they are
> using Sybase. Not sure if they have tried the managed Sybase provider.
> You might also want to read this thread:
>
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=f02812e9-65de-4007-a142-b689522d4c93&sloc=en-us
> As indicated in the thread, it should work on the report server, but I'm
not
> sure about the report designer. It will depend on how the Sybase ASE
> provider is implemented internally.
> Documentation on the config files:
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
>
> --
> Robert M. Bruckner
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Ian Allchin" <ian.allchin@.talk21.com> wrote in message
> news:1f2dd58b.0408050554.4a18275d@.posting.google.com...
> > Further to my earlier posting, I contacted Sybase who were helpful. I
> > have resolved the first issue. My Sybase installation was corrupted,
> > so I uninstalled completely. I then installed Sybase ASE 12.5.2 PC
> > Client which includes the ASE ADO .NET Provider. I have been able to
> > write a .NET Windows Forms application using this provider in very
> > much the same way as the SQL Server .NET Provider.
> >
> > Information about the Sybase ASE .NET Data Provider can be found at:
> >
> > http://sybooks.sybase.com/onlinebooks/group-adonet/asnetg0110e/adonet
> >
> > I AM STILL LOOKING FOR HELP ON HOW TO CONNECT TO SYBASE ASE 12 FROM A
> > SQL SERVER REPORTING SERVICES PROJECT. PLEASE RESPOND IF YOU HAVE ANY
> > INFORMATION.
> >
> > Ian Allchin
> > Alpha Ventures Limited, UK
>|||If you register any managed data provider in report designer and select it
in the data source dialog, the designer will only enable the generic query
designer. The toggle icon for the visual query designer will be disabled
(because the visual query designer is not capable of working with managed
data providers right now as discussed in the referenced thread below).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bruce Loehle-Conger" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:O$iOYRxeEHA.1356@.TK2MSFTNGP09.phx.gbl...
> I have used both the ODBC and OLEDB providers. I have not used the dotnet
> managed provider. Correct me if I am wrong but it would only use the
> provider if you used the generic designer. At runtime it would use it but
> during development only the oledb provider?
> Bruce L-C
> "Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
> news:%233M8BkweEHA.2028@.tk2msftngp13.phx.gbl...
> > I have not done it myself, but this should get you started with using
> Sybase
> > ASE 12 in Reporting Services:
> >
> > * First, you have to make sure the ASE data provider is installed
> correctly,
> > so that the report designer in VS.NET and report server inside ASP.NET
are
> > able to load the dlls of the data provider at runtime. Note: there could
> be
> > file system permissions issues which prevent ASP.NET from accessing the
> ASE
> > data provider dlls. You might want to try to copy the dlls directly into
> the
> > report designer and report server installation directories.
> >
> > * close down all VS.NET sessions before modifying
rsReportDesigner.config
> > * backup the existing rsReportDesigner.config and rsReportServer.config
> >
> > * Add these entries to rsReportDesigner.config in the Data section:
> > <Extension Name="Sybase"
> > Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
> > ... and in the Designer section:
> > <Extension Name="Sybase"
> >
>
Type="Microsoft.ReportDesigner.Design.GenericQueryDesigner,Microsoft.Reporti
> > ngServices.Designer"/>
> >
> > * Stop the ReportServer Windows service
> > * Add this entry to rsReportServer.config in the Data section:
> > <Extension Name="Sybase"
> > Type="Sybase.Data.AseClient.AseConnection,Sybase.Data.AseClient"/>
> > * Restart ReportServer Windows service
> > * Reset IIS/ASP.NET by running iisreset from the command line
> >
> > There are several people on this newsgroups who have indicated they are
> > using Sybase. Not sure if they have tried the managed Sybase provider.
> >
> > You might also want to read this thread:
> >
>
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=f02812e9-65de-4007-a142-b689522d4c93&sloc=en-us
> > As indicated in the thread, it should work on the report server, but I'm
> not
> > sure about the report designer. It will depend on how the Sybase ASE
> > provider is implemented internally.
> >
> > Documentation on the config files:
> >
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_prog_extend_dataproc_8iqq.asp
> >
> >
> > --
> > Robert M. Bruckner
> > Microsoft SQL Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "Ian Allchin" <ian.allchin@.talk21.com> wrote in message
> > news:1f2dd58b.0408050554.4a18275d@.posting.google.com...
> > > Further to my earlier posting, I contacted Sybase who were helpful. I
> > > have resolved the first issue. My Sybase installation was corrupted,
> > > so I uninstalled completely. I then installed Sybase ASE 12.5.2 PC
> > > Client which includes the ASE ADO .NET Provider. I have been able to
> > > write a .NET Windows Forms application using this provider in very
> > > much the same way as the SQL Server .NET Provider.
> > >
> > > Information about the Sybase ASE .NET Data Provider can be found at:
> > >
> > > http://sybooks.sybase.com/onlinebooks/group-adonet/asnetg0110e/adonet
> > >
> > > I AM STILL LOOKING FOR HELP ON HOW TO CONNECT TO SYBASE ASE 12 FROM A
> > > SQL SERVER REPORTING SERVICES PROJECT. PLEASE RESPOND IF YOU HAVE ANY
> > > INFORMATION.
> > >
> > > Ian Allchin
> > > Alpha Ventures Limited, UK
> >
> >
>|||First of all thanks to Robert and Bruce for your comments. The DBA
and I have followed the instructions regarding modifying the designer
and server installations, have made some progress on this issue but
are still experiencing some problems ...
On the server, the Sybase .NET provider does not appear in the list of
available connection types within the New Data Source page. We still
just have: Microsoft SQL Server, OLE DB, Oracle and ODBC.
On the client, I have some mixed results:
Sybase IS available as a type in the shared datasource dialog. This
looked encouraging to start with.
I have set up a shared datasource using a connection that I know works
with the ASE .NET provider (tested in a Windows Forms project) and
then tried to used that shared datasource.
When I create a new dataset, with the shared dataset, the only command
type that is available is text (whereas for SQL Server there are 3
options including Stored Procedure).
Within the Generic Query Designer, the Stored Procedure command type
is available.
When I try to create a dataset using a simple text command such as
"SELECT field1 FROM dbo.table1", field1 appears in the field list and
if I press the exclamation mark button field1 is retrieved from the
database OK. However, if I add field1 into a table on the layout tab
and then try to switch to the preview tab, I receive the following
error message:
An error has occurred during report processing.
Operation is not valid due to the current state of the object.
I have also attempted various ways of executing a Sybase stored
procedure with a single integer parameter, using both text and stored
procedure command types, none of which will preview. The most common
message I receive is:
The procedure expected paramater <@.param_name> which was not provided.
Since it is recognising it is a procedure, and picking up the expected
parameter, this also seems promising, but there appear to be mapping
problems.
Ultimately, I want to re-use existing Sybase stored procedures (with
parameters of various data types) within reporting services, so I need
to resolve this.
Any help would be greatly appreciated.
Ian Allchin
Alpha Ventures Limited, UK|||Hi Santiago
Your posting sounds as if you are having some success as you say "it
works". I am also having some issues as described in my most recent
posting on 20 August 2004. For me, reports where the dataset is built
from even text commands and stored procedures with or without
parameters are not working (although if I press the exclamation mark
button, the rows are returned in the grid at the bottom of the generic
query designer). Are you experiencing the same problems or have you
managed to successfully preview or deploy any reports using the Sybase
.NET Provider? If you have, I would be really grateful if you would
describe exactly how you have done it.
If I have any more news, I will post back.
Many thanks
Ian Allchin
Alpha Ventures Limited, UK|||If you can't get the dotnet provider working then I suggest trying the ODBC
or the OLEDB provider. I had an issue with the OLEDB provider, if you setup
multiple OLEDB sources it always wants to use the first one. The Sybase site
had a workaround but it did not work for me (maybe I didn't implement the
workaround correctly). I didn't want to waste anymore time so I went with
the ODBC. The ODBC has worked well and consistantly for me. The only issue I
have had is with stored procedure with parameters. I am currently going
against 11.9.2 backend with a 12.5.2 client. I am upgrading the server to
12.5.2 shortly and hope that the stored procedure problem goes away (I
believe someone that had posted previously had stored procedures working
with ODBC against a 12.5 server). Anyway, I suggest giving the ODBC driver a
chance.
Wait a minute, I just re-read your posting there. You say you get rows
returned. Have you tried the refresh fields button (it looks like the
refresh a web page button in IE). Try that and see if you get your field
list. If you are returning rows then things should be OK.
Bruce L-C
"Ian Allchin" <ian.allchin@.talk21.com> wrote in message
news:1f2dd58b.0408212332.32a40752@.posting.google.com...
> Hi Santiago
> Your posting sounds as if you are having some success as you say "it
> works". I am also having some issues as described in my most recent
> posting on 20 August 2004. For me, reports where the dataset is built
> from even text commands and stored procedures with or without
> parameters are not working (although if I press the exclamation mark
> button, the rows are returned in the grid at the bottom of the generic
> query designer). Are you experiencing the same problems or have you
> managed to successfully preview or deploy any reports using the Sybase
> .NET Provider? If you have, I would be really grateful if you would
> describe exactly how you have done it.
> If I have any more news, I will post back.
> Many thanks
> Ian Allchin
> Alpha Ventures Limited, UK|||Bruce
Thanks for the information regarding ODBC and OLEDB. I have already
tried OLEDB with some success (ie I did manage to call stored
procedures and preview reports), although I had some minor issues with
using 12.5.2 client against 12.0 server. I will revisit this and ODBC
if I cannot resolve the current issues with the ADO .NET route, which
I what Sybase recommended.
My current situation with the ADO .NET provider is that I can connect
to a database and execute a non parameterised text command within the
generic query designer - eg SELECT * FROM tablename. My field list
appears without me pressing refresh fields and if I press the
exclamation mark button I see my rows returned to the grid. However,
when I add fields to a table control on the layout tab and then try to
switch to the preview tab, I receive an error message:
An error has occurred during report processing.
Operation is not valid due to the current state of the object.
I have also tried EXEC storedprocedurename 1 (where 1 is a hard coded
argument) as a text command. Reporting services brings back my
expected field list and returns rows in the grid. However, when I add
fields to a table control on the layout tab and then try to switch to
the preview tab, I receive the same error message.
The reason I am using text commands is that this appears to be the
only option that is fully available and other attempts to deal with
stored procedures have caused different error messages (see my posting
20 August 2004).
Stop Press:
I am able to build and deploy the report. When selecting the report
on the portal, I receive a more detailed error message:
An error has occurred during report processing. (rsProcessingAborted)
An attempt has been made to use a data extension 'Sybase' that is not
registered for this report server. (rsDataExtensionNotFound)
OK, so that may explain the "invalid state of the object".
Does anyone know what we have to do to register it correctly? Also,
should the stored procedure option be available as a command type like
with SQL Server?
Thanks
Ian Allchin
Alpha Ventures Limited UK|||Sorry I can't help anymore with this. I would like to use the dotnet
provider for Sybase as well if it can be made to work.
Bruce L-C
"Ian Allchin" <ian.allchin@.talk21.com> wrote in message
news:1f2dd58b.0408230016.50afd7ac@.posting.google.com...
> Bruce
> Thanks for the information regarding ODBC and OLEDB. I have already
> tried OLEDB with some success (ie I did manage to call stored
> procedures and preview reports), although I had some minor issues with
> using 12.5.2 client against 12.0 server. I will revisit this and ODBC
> if I cannot resolve the current issues with the ADO .NET route, which
> I what Sybase recommended.
> My current situation with the ADO .NET provider is that I can connect
> to a database and execute a non parameterised text command within the
> generic query designer - eg SELECT * FROM tablename. My field list
> appears without me pressing refresh fields and if I press the
> exclamation mark button I see my rows returned to the grid. However,
> when I add fields to a table control on the layout tab and then try to
> switch to the preview tab, I receive an error message:
> An error has occurred during report processing.
> Operation is not valid due to the current state of the object.
> I have also tried EXEC storedprocedurename 1 (where 1 is a hard coded
> argument) as a text command. Reporting services brings back my
> expected field list and returns rows in the grid. However, when I add
> fields to a table control on the layout tab and then try to switch to
> the preview tab, I receive the same error message.
> The reason I am using text commands is that this appears to be the
> only option that is fully available and other attempts to deal with
> stored procedures have caused different error messages (see my posting
> 20 August 2004).
> Stop Press:
> I am able to build and deploy the report. When selecting the report
> on the portal, I receive a more detailed error message:
> An error has occurred during report processing. (rsProcessingAborted)
> An attempt has been made to use a data extension 'Sybase' that is not
> registered for this report server. (rsDataExtensionNotFound)
> OK, so that may explain the "invalid state of the object".
> Does anyone know what we have to do to register it correctly? Also,
> should the stored procedure option be available as a command type like
> with SQL Server?
> Thanks
> Ian Allchin
> Alpha Ventures Limited UK|||I have now had a response from Microsoft technical support. They said
that the Sybase ADO .NET Provider is not a Reporting Services Data
Extension. These are two different things. Sybase would need to
provide a Reporting Services Data Extension.
The Microsoft technical support person recommended trying OLEDB and
only using ODBC if OLEDB was unsuccessful. I intend to follow this
advice, but I will also contact Sybase and ask if they have any plans
to provide a Reporting Services Data Extension and post back.
Ian Allchin
Alpha Ventures Limited, UK|||Interesting. I thought all that was needed was a dotnet data provider.
Didn't know that it was more than that. Thanks for posting back on this.
Bruce L-C
"Ian Allchin" <ian.allchin@.talk21.com> wrote in message
news:1f2dd58b.0408240942.262fd3a1@.posting.google.com...
> I have now had a response from Microsoft technical support. They said
> that the Sybase ADO .NET Provider is not a Reporting Services Data
> Extension. These are two different things. Sybase would need to
> provide a Reporting Services Data Extension.
> The Microsoft technical support person recommended trying OLEDB and
> only using ODBC if OLEDB was unsuccessful. I intend to follow this
> advice, but I will also contact Sybase and ask if they have any plans
> to provide a Reporting Services Data Extension and post back.
> Ian Allchin
> Alpha Ventures Limited, UK|||I have contacted Sybase. They are now considering whether to
implement a Reporting Services Data Extension. A decision is expected
within the next few months and I will post back if I receive any news
on this. In the meantime, I will be going back to try OLEDB and ODBC.
Ian Allchin
Alpha Ventures Limited, UK|||Thanks for the update. If you have any problems with either OLEDB or ODBC
post back here. I have used ODBC extensively with Sybase and am now
migrating to 12.5.2. Others have used OLEDB successfully (and I will be
giving that a try shortly as well).
Thanks again, now I won't waste any time with with the dotnet provider.
Bruce L-C
"Ian Allchin" <ian.allchin@.talk21.com> wrote in message
news:1f2dd58b.0409060212.3f64dffb@.posting.google.com...
>I have contacted Sybase. They are now considering whether to
> implement a Reporting Services Data Extension. A decision is expected
> within the next few months and I will post back if I receive any news
> on this. In the meantime, I will be going back to try OLEDB and ODBC.
> Ian Allchin
> Alpha Ventures Limited, UK
Issues connecting to SQL Server 2005 from SQL Server Mgmt Studio - Please help!!!
Hi Everyone,
I am running into a problem and have been browsing the web and reading nonstop for answers with no success. My company just installed SQL Server 2005 and I am trying to connect to it via SQL Server Management Studio from my network computer in the same office building.
When I browse for Local or Network Servers in the initial popup box at SQL Management Studio Startup, it doesn't show any servers at all. Is there something I need to enable on the Server using the Configuration Manager or one of the other tools to allow my network computer to "see" the SQL Server?
Any insight would be MUCH appreciated. Even a link to a how-to would suffice. Thank you.
Is your server and your computer on the same network? To enumerate SQL server on your network, you must turn on SQL Browser on your server machine. Make sure UDP port 1434 is not blocked by any firewall on your server. Keep in mind you are not guaranteed to see all network instance as the enumration is UDP based and is not realiable. So, in this case, you'd better type your server name into the box directly. such server1 or server1\inst1, etc.
|||
read these article
http://msdn2.microsoft.com/en-us/library/ms165724.aspx
http://support.microsoft.com/default.aspx/kb/914277
http://support.microsoft.com/kb/287932/en
Madhu
Friday, March 9, 2012
Issue with printing/exporting reports
Dear ppl,
I have designed a report in Visual Studio 2005. The report have a couple of data regions (table and list) + some free text boxes.. The problem is when i print or export the report to pdf etc, it prints/exports a blank page after every page. e.g. if a report is of 2 pages, it will be printed/exported as Page 1 + Blank Page + Page 2 + Blank Page...
Can any one please tell me what am i missing here?
Awaiting,
just changed the Report Page width to 22cm from 21cm and it started printing/exporting perfectly without any blank pages... I thought the A4 size page width was 21cm..strange innit?
Friday, February 24, 2012
Issue installing SQL Server Express on Visual Studio Beta 2
Hi,
I have installed VS 2005 Beta 2 (Team System) using a DVD available from MS TEch Ed. This also installs SQL Server 2005 Express edition along with other tools. This installation is done on a vpc.
However when I try to install SQL Server Express Manager over this installation, I get "The installer package could not be opened. Contact the vendor to make sure to verify that the Windows installer package is valid".
Is there a solution to get this resolved ?
Thanks in advance !
It likely that you need to download the file again. Also not that you may need to uninstall the .Net Framework and re-install the version that SQL Server shipped in its June CTP as the NetFx version between Vs Beta 2 and SQL CTP June is different.
-Euan
Subscribe to:
Posts (Atom)