Showing posts with label net. Show all posts
Showing posts with label net. Show all posts

Wednesday, March 28, 2012

microsoft sql database (*.mdf) using help ?

Hi

I use visual std. 2005 and I create a asp.net web page after >add item> sql database > I added my project *.mdf file when I make project my project is runnig with visual studio 2005 but I sent my hostting (internet server )I cant use this mdf file . Are we register this mdf file sqlserver ? can we use this mdf file like access file (mdb ) . What kind of thing I do to use this mdf file .

Thanks

I know some hosts don't support SQL 2005, FastHosts in the UK for exampe have no plans to allow the user of the SQL Express MDF files so it cannot work like an Access MDB file. They say that this is down to performance and security implications.|||

prokurs:

Are we register this mdf file sqlserver ? can we use this mdf file like access file (mdb ) . What kind of thing I do to use this mdf file .

No, you must have a SQL instance on the host to use mdf files. Although in VS2005 you can create mdf files and use them by attaching them to a SQL Express Instance (specified in the Data Source property in your connection string), you still need a SQL Instance to which you have access. So you must have a SQL2005/Express instance on the hosting machine, and then add proper permissions to your account.

|||

hi can you look my mistake this mistake's source ishttp://www.prokurs.com/e/loginana.aspx you can enter this page after write random user name and passwors after then I have got a this mistake please help ?

Server Error in '/' Application.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details:System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.


Stack Trace:

[SqlException (0x80131904): An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +735091 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +820 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84 System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197 System.Web.Security.SqlMembershipProvider.GetPasswordWithFormat(String username, Boolean updateLastLoginActivityDate, Int32& status, String& password, Int32& passwordFormat, String& passwordSalt, Int32& failedPasswordAttemptCount, Int32& failedPasswordAnswerAttemptCount, Boolean& isApproved, DateTime& lastLoginDate, DateTime& lastActivityDate) +1121 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved, String& salt, Int32& passwordFormat) +105 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved) +42 System.Web.Security.SqlMembershipProvider.ValidateUser(String username, String password) +83 System.Web.UI.WebControls.Login.OnAuthenticate(AuthenticateEventArgs e) +160 System.Web.UI.WebControls.Login.AttemptLogin() +105 System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e) +99 System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +35 System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) +115 System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +163 System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5102



Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

|||

It is a connection failure, if you're using SQL2000 you need to make sure TCP/IP and Named Pipes network libraries are enabled on the SQL2000 instance via Server Network Utility; in case of SQL2005/Express you can enable the remote connecitons using SQL Server Surface Area. Then rewrite your connection string to point to the correct SQL instance.

If you're using built-in Login Controls (membership provider) in .NET 2.0, you can customize the database connections as mentioned in this article:

http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx

sql

Microsoft SQL 2005 Licensing & ASP.NET applications

I am having a nightmare getting an answer about what type of licensing I will need for the standard addition of SQL Server 2005 for my asp.net application and wonder if anyone has any advice.

As I see it its very simple, I have a web app that makes a connection to SQL via a connection string using a single username and password, no impersonation just straight SQL authentication.

For this simple scenario I figured I would need to get a SQL 2005 license and then 1 Client access license (CAL), this being a nice affordable way of doing things BUT I am being told by different sources, that I may need to license on a per processor basis as any user of my web application, anonymous or otherwise needs a client access license and given that I don't know how many users are going to access my website I would need to go for the larger outlay and purchase two standard processor license (my sql server is a dual processor machine).

Can anyone tell me if this is the case, is a connection from a ASP.Net website to a SQL server for my website visitors regarded as a new client and therefore needs a client access license or the large investment of a per processor license?

I would stick with SQL Express but at 4gigs max it won't do the job.

Thanks in advance.

SQL Server license since 2000 is per processor not CAL and I cannot understand how you think you need just one CAL when you know Express 4gig is too small for your needs. Hope this helps.|||

No it doesn't help...

Microsoft advertise CAL as a licensing option along side the processor option and given its a web app with just one connection doing all the work why wouldn't I think I only need one CAL, do you have anything else to add?

|||The only way you can use one CAL is you have only one user, your other choice is to use the Smallbusiness Server SQL Server but I think you will get more from Express because the Smallbusiness Server comes with SQL Server 2000.|||

The small business server is overkill; it's a simple website using sql 2005 as the database.

Just to go over it again. I have a public internet facing website that creates a connection to SQL 2005, in my mind this is a single user, the website is the only user of the SQL server so in that case I need just one CAL, what do you think, that has to be correct doesn't it?

SQL 2005 isn't any use due to the 4gig limit.

|||

I have been in a shop with 68 SQL Servers trust me if 4gig is not enough for you, then you need a per processor license. And the Smallbusines server is not an over kill because you can choose to use only the SQL Server and it will cost you less than $1000 and 75 concurrent users.

|||

SBS is not an ideal for a single N-Tier application so we can forget that. 4gig isnt enough so we can discount Express. Now given we have cut through the dead wood and are now look at the heart of the matter, i will reiterate it just one more time:

If i have an ASP.NET application connecting to an SQL Server via a single connection am I able to use a single CAL?

If you are unsure of the answer please dont mention SBS or Express again otherwise we could be here all night :-)

|||The answer is no.|||Why?|||The answer is your single connection is just for the Asp.net worker process not a live user, and if you send email that is another user. The best thing to do is call your local Microsoft office and have a SQL Server local resource contact you.|||

So what you are saying is you dont know?

If the .net worker process connects and returns data I agree that's one client access, the SQL server isn't sending email or doing anything other than being a database so hence I conclusion that I only need to purchase a single CAL. The reason for my posting is because my Microsoft Office here seems unsure themselves!

|||No I am not telling you I don't know the number of cal you use depends on your write users how many will write in the database. So count your INSERT and UPDATE users and you will have an idea of how many cals you need and I don't think it will be one.|||

Why would it not be one user? In web application development it would be foolhardy to develop an application that allowed for multiple read write accounts when a website traditionally allows anonymous access. If you read most Microsoft best practices you will find that they specify a web application user account that allows for the execution of stored procedures and that's it no other accounts, no insert account or update account or a special forgotten sa account that lets Mr foobar hacker traverse directories via a script injection.

So given we hope that most web applications have minimal sql accounts do you agree that I need the bare minimum CAL's or do you have any other thoughts?

|||

No I don't the shop with 68 SQL Servers and one Oracle was a bank and every account is a write user. SQL injection is not permission related my MCDBA was when there are no books on SQL Server 7.0. The link below is one of the oldest software retailers online most of your questions are answered. Stored proc execution through DBO(database owner) is not related to write permissions. And SQL Server permissions are implemented by Microsoft but defined by ANSI SQL.

http://www.provantage.com/sql-server-standard-edition-32-bit-windows~220152612.htm

|||

Ok we are off the topic now and you kind of asked for this so sorry in advance...

SQL injection can relate to permissions, if you don't have the correct permissions you are susceptible to all sorts of injection if your web application allows it. You clearly have no experience of SQL in the environment that I entitled my original post and without descending into the kind of flaming exercise I have seen on many other forums, can i just say that roaming around posting glib answers may give you a large number at the end of your screen name but it isn't helping anyone and its making you look a little silly.

Oh and if had wanted the advice of a retailer I would of gone to my local supermarket and asked on of the chaps behind the till the question.

There I said it and now that this post has sunk to this level i guess I will need to ask my question else where!

Monday, March 26, 2012

Microsoft Reporting Technologies

It seems there are several current reporting mechanisms related to .net and Visual Studio. There is Crystal Reports, an integrated reporting system in Visual Studio and a somewhat related reporting system in SQL Server. The last two seem to use similar .xml bases but it's unclear how or if they are related. This does not include (or maybe is does) the Sharepoint reporting system.

I have eliminated the Crystal Report for various reasons after trying it for awhile. Therefore is there some good introductions and/or comparisons between the Visual Studio reporting system and the SQL Server or BI reporting systems since they both seem to use .rdlc and .rdl type definitions. How or are they related?

Try this link where you can find the answers for your questions

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

sql

Microsoft Releases Synchronization Services CTP

The Microsoft Synchronization Services for ADO.NET v1.0 CTP release appeared without fanfare on January 22, 2006. The release contains "v1.0 early CTP" bits for the sync framework and SQL Server 2005 Compact Edition (SSCE) v3.5, the Orcas successor to the SSCE v3.1 RTM bits, which Microsoft released on January 11, 2006. The current code name for Sync Services is OCS (for Occasionally Connected Systems).

Seems to me to resemble a "stealth release."

For more, see http://oakleafblog.blogspot.com/2007/01/microsoft-releases-synchronization.html.

Oops. Make that January 11, 2007!

--rj

Monday, March 19, 2012

Microsoft Analysis Server 2005 and .NET 1.1

Hi,

Firstly, I had to post this query here since I did not find any other place relating to Microsoft SQL Analysis Server 2005 and that it is related to SQL server 2005.

I am using Microsoft SQL analysis server 2005 and .NET 1.1 for Asp.NET (C#)

I need to programmatically create Measures, Dimensions and Cubes using .Net 1.1 (C#) in an Asp.NET page, and then I need to access the measures, dimensions and cubes again from another Asp.Net page.

My querys are:

1. To create and manipulate the SQL Analysis server objects like Dimensions, Cubes what should I use? The documentation for Analysis server 2005 says we can use (Analysis Management Objects)AMO. but I am not sure if we can use it with .NET 1.1?

2. If AMO is possible, then what to use? There is one more technology we can use called as (Deciscion Suport Objects) DSO. but they are COM based and were for Analysis services 2000.

3. To query the data, what technology can I use? Microsoft says we can use ADOMD.NET. Microsoft also gives many other technologies that I think do similar work, like XMLA, ASSL.

Can somebody help me in this.

Also please do give me some links that have code samples for the same.

Thanks and Regards

Vijay R

Analysis service in SQL Server 2005 is on the calculus end of the relational model and Microsoft is compliant with all the Calculus algorithms. When I tested SQL Server 2005 in beta 2 there is a management studio for Analysis service if you don't have it installed I suggest you do so because you can get sample ADOMD.NET code from the templates. I dont think you can use DSO(decision support object) with your web application because your database must be Denormalized and the tables read only which was required in SQL Server 2000 because Microsoft had only two Calculus algorithms and one was flawed.

But SQL Server 2005 comes with something that let you strip the algebra and move to Calculus in one step called UDM(unified dimension modeling).
Try the links below for more info and the last link is the site of the person who created the Calculus end of the relational model. Hope this helps.

http://www.microsoft.com/sql/solutions/bi/default.mspx

http://www.mosha.com/msolap/yukon.htm

http://www.rkimball.com/

Microsoft .NET Framework: Unhandled Exception

Hi,
I built a very simple report that uses a shared data source to access
an SQL server. I wanted to select all columns from a table on a linked
server. My query is simply "select * from SERVER.DATABASE.USER.table"
and it works fine in Query Analyzer. However, when I enter this query
into the Report Designer (running SP1) and try to run it, I get the
error below.
Thanks in advance for any help you wonderful MSFT guys can give,
especially if there's a workaround!
--Adam Bliss
--TEXT OF ERROR MESSAGE--
Microsoft .NET Framework
An unhandled exception has occured in a component in your appliaction.
Click continue and application [sic] will ignore this error and attempt
to
continue.
Object reference not set to an instance of an object.
Details:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance
of an object.
at Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(Guid&
pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, Object[] pvaIn,
IntPtr pvaOut)
at
Microsoft.ReportDesigner.Design.VDTToolBar.SQLToolBar_ButtonClick(Object
sender, ToolBarButtonClickEventArgs e)
at
System.Windows.Forms.ToolBar.OnButtonClick(ToolBarButtonClickEventArgs
e)
at System.Windows.Forms.ToolBar.WmReflectCommand(Message& m)
at System.Windows.Forms.ToolBar.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32
msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
---
Microsoft.ReportingServices.Designer
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.Designer.dll
---
Microsoft.VisualStudio.Shell.Interop
Assembly Version: 7.0.3500.0
Win32 Version: 8.0.30310 (lab21.030309-2105)
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.VisualStudio.Shell.Interop.DLL
---
Microsoft.VisualStudio.OLE.Interop
Assembly Version: 7.0.3500.0
Win32 Version: 8.0.30310 (lab21.030309-2105)
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.VisualStudio.OLE.Interop.DLL
---
Microsoft.VisualStudio
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///C:/Program%20Files/Microsoft%20Visual%20Studio%20.NET%202003/Common7/IDE/Microsoft.VisualStudio.DLL
---
Microsoft.DataWarehouse.Interfaces
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.DataWarehouse.Interfaces.DLL
---
Microsoft.DataWarehouse.VsIntegration
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.DataWarehouse.VsIntegration.DLL
---
System
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
System.Xml
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
---
System.Web
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system.web/1.0.5000.0__b03f5f7f11d50a3a/system.web.dll
---
System.Drawing
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
---
Microsoft.DataWarehouse
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.DataWarehouse.DLL
---
EnvDTE
Assembly Version: 7.0.3300.0
Win32 Version: 7.00.9466
CodeBase:
file:///c:/windows/assembly/gac/envdte/7.0.3300.0__b03f5f7f11d50a3a/envdte.dll
---
System.Windows.Forms
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
---
Microsoft.VSDesigner
Assembly Version: 7.0.5000.0
Win32 Version: 7.10.3077
CodeBase:
file:///C:/Program%20Files/Microsoft%20Visual%20Studio%20.NET%202003/Common7/IDE/Microsoft.VSDesigner.DLL
---
Microsoft.VisualStudio.Designer.Interfaces
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///C:/Program%20Files/Microsoft%20Visual%20Studio%20.NET%202003/Common7/IDE/Microsoft.VisualStudio.Designer.Interfaces.DLL
---
RegexAssembly1_0
Assembly Version: 0.0.0.0
Win32 Version: n/a
CodeBase:
---
Microsoft.VisualStudio.TextManager.Interop
Assembly Version: 7.0.3500.0
Win32 Version: 8.0.30310 (lab21.030309-2105)
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.VisualStudio.TextManager.Interop.DLL
---
Microsoft.ReportingServices.ReportPreview
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.ReportPreview.DLL
---
Microsoft.ReportingServices.Processing
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.Processing.DLL
---
Microsoft.ReportingServices.Interfaces
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.Interfaces.DLL
---
Microsoft.ReportingServices.Diagnostics
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.Diagnostics.DLL
---
qcafn_1e
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
bz_nfjwh
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
yl9hu7fj
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
ilerz4wa
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
5jocxjac
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
jrfgwn5w
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
fxnv6itt
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
zg4sz4ni
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
ny4juciw
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
xlnic1xx
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
atmntgbj
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
imdmrqdn
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
-t4ubrdd
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
ogl20pjz
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
uzelzqkt
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
7gxa3lt5
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
zafsetv2
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
ttnoe-eu
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
zzdw1h6p
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
r9dhpvbw
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
qexy1od1
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
x5cdllnv
Assembly Version: 0.0.0.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
---
System.Design
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system.design/1.0.5000.0__b03f5f7f11d50a3a/system.design.dll
---
Accessibility
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
---
Microsoft.SqlServer.WizardFramework
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.SqlServer.WizardFramework.dll
---
Microsoft.ReportingServices.Designer.Wizards
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.Designer.Wizards.DLL
---
Microsoft.SqlServer.CustomControls
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.SqlServer.CustomControls.DLL
---
Microsoft.NetEnterpriseServers.ExceptionMessageBox
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.NetEnterpriseServers.ExceptionMessageBox.DLL
---
Microsoft.ReportingServices.DataExtensions
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.DataExtensions.DLL
---
System.Data
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll
---
System.Data.OracleClient
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system.data.oracleclient/1.0.5000.0__b77a5c561934e089/system.data.oracleclient.dll
---
System.EnterpriseServices
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system.enterpriseservices/1.0.5000.0__b03f5f7f11d50a3a/system.enterpriseservices.dll
---
Interop.Vdt70
Assembly Version: 8.0.242.0
Win32 Version: 8.0.242.0
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Interop.Vdt70.DLL
---
ReportingServicesLibrary
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/ReportingServicesLibrary.DLL
---
Microsoft.ReportingServices.XmlRendering
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.XmlRendering.DLL
---
Microsoft.ReportingServices.CsvRendering
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.CsvRendering.DLL
---
Microsoft.ReportingServices.ImageRendering
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.ImageRendering.DLL
---
Microsoft.ReportingServices.HtmlRendering
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.HtmlRendering.DLL
---
Microsoft.ReportingServices.ExcelRendering
Assembly Version: 8.0.242.0
Win32 Version: 8.00.878.00
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.ExcelRendering.DLL
---
ReportingServicesNativeClient
Assembly Version: 0.0.0.0
Win32 Version: 2000.080.0878.000
CodeBase:
file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/ReportingServicesNativeClient.DLL
---That looks like bug.
As workaround I suggest to use Generic Query Designer
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Adam Bliss" <abliss@.gmail.com> wrote in message
news:cdjf9k$vk4@.odak26.prod.google.com...
> Hi,
> I built a very simple report that uses a shared data source to access
> an SQL server. I wanted to select all columns from a table on a linked
> server. My query is simply "select * from SERVER.DATABASE.USER.table"
> and it works fine in Query Analyzer. However, when I enter this query
> into the Report Designer (running SP1) and try to run it, I get the
> error below.
> Thanks in advance for any help you wonderful MSFT guys can give,
> especially if there's a workaround!
> --Adam Bliss
> --TEXT OF ERROR MESSAGE--
> Microsoft .NET Framework
> An unhandled exception has occured in a component in your appliaction.
> Click continue and application [sic] will ignore this error and attempt
> to
> continue.
> Object reference not set to an instance of an object.
> Details:
> See the end of this message for details on invoking
> just-in-time (JIT) debugging instead of this dialog box.
> ************** Exception Text **************
> System.NullReferenceException: Object reference not set to an instance
> of an object.
> at Microsoft.VisualStudio.OLE.Interop.IOleCommandTarget.Exec(Guid&
> pguidCmdGroup, UInt32 nCmdID, UInt32 nCmdexecopt, Object[] pvaIn,
> IntPtr pvaOut)
> at
> Microsoft.ReportDesigner.Design.VDTToolBar.SQLToolBar_ButtonClick(Object
> sender, ToolBarButtonClickEventArgs e)
> at
> System.Windows.Forms.ToolBar.OnButtonClick(ToolBarButtonClickEventArgs
> e)
> at System.Windows.Forms.ToolBar.WmReflectCommand(Message& m)
> at System.Windows.Forms.ToolBar.WndProc(Message& m)
> at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
> at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
> at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32
> msg, IntPtr wparam, IntPtr lparam)
>
> ************** Loaded Assemblies **************
> mscorlib
> Assembly Version: 1.0.5000.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
> ---
> Microsoft.ReportingServices.Designer
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.Designer.dll
> ---
> Microsoft.VisualStudio.Shell.Interop
> Assembly Version: 7.0.3500.0
> Win32 Version: 8.0.30310 (lab21.030309-2105)
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.VisualStudio.Shell.Interop.DLL
> ---
> Microsoft.VisualStudio.OLE.Interop
> Assembly Version: 7.0.3500.0
> Win32 Version: 8.0.30310 (lab21.030309-2105)
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.VisualStudio.OLE.Interop.DLL
> ---
> Microsoft.VisualStudio
> Assembly Version: 1.0.5000.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20Visual%20Studio%20.NET%202003/Common7/IDE/Microsoft.VisualStudio.DLL
> ---
> Microsoft.DataWarehouse.Interfaces
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.DataWarehouse.Interfaces.DLL
> ---
> Microsoft.DataWarehouse.VsIntegration
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.DataWarehouse.VsIntegration.DLL
> ---
> System
> Assembly Version: 1.0.5000.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> System.Xml
> Assembly Version: 1.0.5000.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
> ---
> System.Web
> Assembly Version: 1.0.5000.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system.web/1.0.5000.0__b03f5f7f11d50a3a/system.web.dll
> ---
> System.Drawing
> Assembly Version: 1.0.5000.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
> ---
> Microsoft.DataWarehouse
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.DataWarehouse.DLL
> ---
> EnvDTE
> Assembly Version: 7.0.3300.0
> Win32 Version: 7.00.9466
> CodeBase:
> file:///c:/windows/assembly/gac/envdte/7.0.3300.0__b03f5f7f11d50a3a/envdte.dll
> ---
> System.Windows.Forms
> Assembly Version: 1.0.5000.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
> ---
> Microsoft.VSDesigner
> Assembly Version: 7.0.5000.0
> Win32 Version: 7.10.3077
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20Visual%20Studio%20.NET%202003/Common7/IDE/Microsoft.VSDesigner.DLL
> ---
> Microsoft.VisualStudio.Designer.Interfaces
> Assembly Version: 1.0.5000.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20Visual%20Studio%20.NET%202003/Common7/IDE/Microsoft.VisualStudio.Designer.Interfaces.DLL
> ---
> RegexAssembly1_0
> Assembly Version: 0.0.0.0
> Win32 Version: n/a
> CodeBase:
> ---
> Microsoft.VisualStudio.TextManager.Interop
> Assembly Version: 7.0.3500.0
> Win32 Version: 8.0.30310 (lab21.030309-2105)
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.VisualStudio.TextManager.Interop.DLL
> ---
> Microsoft.ReportingServices.ReportPreview
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.ReportPreview.DLL
> ---
> Microsoft.ReportingServices.Processing
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.Processing.DLL
> ---
> Microsoft.ReportingServices.Interfaces
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.Interfaces.DLL
> ---
> Microsoft.ReportingServices.Diagnostics
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.Diagnostics.DLL
> ---
> qcafn_1e
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> bz_nfjwh
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> yl9hu7fj
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> ilerz4wa
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> 5jocxjac
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> jrfgwn5w
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> fxnv6itt
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> zg4sz4ni
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> ny4juciw
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> xlnic1xx
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> atmntgbj
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> imdmrqdn
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> -t4ubrdd
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> ogl20pjz
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> uzelzqkt
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> 7gxa3lt5
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> zafsetv2
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> ttnoe-eu
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> zzdw1h6p
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> r9dhpvbw
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> qexy1od1
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> x5cdllnv
> Assembly Version: 0.0.0.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
> ---
> System.Design
> Assembly Version: 1.0.5000.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system.design/1.0.5000.0__b03f5f7f11d50a3a/system.design.dll
> ---
> Accessibility
> Assembly Version: 1.0.5000.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
> ---
> Microsoft.SqlServer.WizardFramework
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.SqlServer.WizardFramework.dll
> ---
> Microsoft.ReportingServices.Designer.Wizards
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.Designer.Wizards.DLL
> ---
> Microsoft.SqlServer.CustomControls
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.SqlServer.CustomControls.DLL
> ---
> Microsoft.NetEnterpriseServers.ExceptionMessageBox
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.NetEnterpriseServers.ExceptionMessageBox.DLL
> ---
> Microsoft.ReportingServices.DataExtensions
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.DataExtensions.DLL
> ---
> System.Data
> Assembly Version: 1.0.5000.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll
> ---
> System.Data.OracleClient
> Assembly Version: 1.0.5000.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system.data.oracleclient/1.0.5000.0__b77a5c561934e089/system.data.oracleclient.dll
> ---
> System.EnterpriseServices
> Assembly Version: 1.0.5000.0
> Win32 Version: 1.1.4322.573
> CodeBase:
> file:///c:/windows/assembly/gac/system.enterpriseservices/1.0.5000.0__b03f5f7f11d50a3a/system.enterpriseservices.dll
> ---
> Interop.Vdt70
> Assembly Version: 8.0.242.0
> Win32 Version: 8.0.242.0
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Interop.Vdt70.DLL
> ---
> ReportingServicesLibrary
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/ReportingServicesLibrary.DLL
> ---
> Microsoft.ReportingServices.XmlRendering
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.XmlRendering.DLL
> ---
> Microsoft.ReportingServices.CsvRendering
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.CsvRendering.DLL
> ---
> Microsoft.ReportingServices.ImageRendering
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.ImageRendering.DLL
> ---
> Microsoft.ReportingServices.HtmlRendering
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.HtmlRendering.DLL
> ---
> Microsoft.ReportingServices.ExcelRendering
> Assembly Version: 8.0.242.0
> Win32 Version: 8.00.878.00
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/Microsoft.ReportingServices.ExcelRendering.DLL
> ---
> ReportingServicesNativeClient
> Assembly Version: 0.0.0.0
> Win32 Version: 2000.080.0878.000
> CodeBase:
> file:///C:/Program%20Files/Microsoft%20SQL%20Server/80/Tools/Report%20Designer/ReportingServicesNativeClient.DLL
> ---
>

Monday, March 12, 2012

Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence

Hello,

I am using the Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence to connect to SAP BW queries. I have tried looking for documentation on the connection string arguments but have not had much success. My question is this: How do you specify the connection timeout in the connection string:

Connection string example: DataSource=http://mySAPNetweaverBIServer:8000/sap/bw/xml/soap/xmla?sap-client=020

Cheers

Hi MMuffett,

Can u provide me the URL to get evaluation software of Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence.

Or from where do i get this ?

Thanks,

Anil

|||

Hi MMuffett,

I am using the Microsoft .NET Data Provider v1.0 for SAP mySAP Business Intelligence to connect to SAP BW queries.

I am not getting a success browser with xml code while doing the "Test Service in XMLA", its showing Bad Gateway error in browser

The link which is displayed on the address bar of browser is http://sapmdm.wipro.com:8000/sap/bw/xml/soap/xmla?sap-client=800.

The above link is used for the connection datasoure in Reporting services.

Can u pls suggest me what to do? what may be the problem, do we need to made some Middleware cofiguration settings? if yes then how?

Thanks in Advance

Anil

Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence

Hello,

I am using the Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence to connect to SAP BW queries. I have tried looking for documentation on the connection string arguments but have not had much success. My question is this: How do you specify the connection timeout in the connection string:

Connection string example: DataSource=http://mySAPNetweaverBIServer:8000/sap/bw/xml/soap/xmla?sap-client=020

Cheers

Hi MMuffett,

Can u provide me the URL to get evaluation software of Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence.

Or from where do i get this ?

Thanks,

Anil

|||

Hi MMuffett,

I am using the Microsoft .NET Data Provider v1.0 for SAP mySAP Business Intelligence to connect to SAP BW queries.

I am not getting a success browser with xml code while doing the "Test Service in XMLA", its showing Bad Gateway error in browser

The link which is displayed on the address bar of browser is http://sapmdm.wipro.com:8000/sap/bw/xml/soap/xmla?sap-client=800.

The above link is used for the connection datasoure in Reporting services.

Can u pls suggest me what to do? what may be the problem, do we need to made some Middleware cofiguration settings? if yes then how?

Thanks in Advance

Anil

Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence

Hello,

I am using the Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence to connect to SAP BW queries. I have tried looking for documentation on the connection string arguments but have not had much success. My question is this: How do you specify the connection timeout in the connection string:

Connection string example: DataSource=http://mySAPNetweaverBIServer:8000/sap/bw/xml/soap/xmla?sap-client=020

Cheers

Hi MMuffett,

Can u provide me the URL to get evaluation software of Microsoft .NET Data Provider v1.0 for SAP NetWeaver? Business Intelligence.

Or from where do i get this ?

Thanks,

Anil

|||

Hi MMuffett,

I am using the Microsoft .NET Data Provider v1.0 for SAP mySAP Business Intelligence to connect to SAP BW queries.

I am not getting a success browser with xml code while doing the "Test Service in XMLA", its showing Bad Gateway error in browser

The link which is displayed on the address bar of browser is http://sapmdm.wipro.com:8000/sap/bw/xml/soap/xmla?sap-client=800.

The above link is used for the connection datasoure in Reporting services.

Can u pls suggest me what to do? what may be the problem, do we need to made some Middleware cofiguration settings? if yes then how?

Thanks in Advance

Anil

Microsoft .NET Data Provider for mySAP Business Suite Licence Implications?

Hello Everyone,

Does anyone know if there are any licence implications (SAP side) against Microsoft .NET Data Provider for mySAP Business Suite?

I heard from a colleague that if my SQL Server has (for example) 5 users, if SQL does connect to SAP, it would require the user license of 5 more users?

If there any implications similar to this one with SAP?

Regards,

Joseph

First, please note the provider you mentioned is in CTP (Preview) status and can't be used in a production environment. There is an upcoming BTS R2 Adapter Pack (currently in Beta2) that would RTW in Jan '08 - which might be used in Production.

To answer your specific question (example 5 users) : the SAP Provider can be installed and used from a SQL box with Enterprise SKU, AFAIK it doesn't need additional named users on the SQL side.

The customer has to check with SAP on their licensing terms for data access, we can't advise there.

Microsoft .NET Data Provider for mySAP Business Suite

Is this product SAP Certified?

I have read somewhere that any integration technology wrt SAP has to be SAP certified.

If no, what are the implications of using this in a project? will SAP refuse to support the customer because they are using a non-SAP certified product?

regards,

Abhishek.

I believe there could be issues with SAP support, but for a definitive answer, ask SAP themselves.|||

There are ongoing discussions between Microsoft and SAP at the highest levels, the provider for mySAP is not certified and there is no ETA at present.

A new adapter pack for SAP (also Siebel) is in development and expected for release in early CY08 with the Biztalk R2 adapter pack; it will include the functionality of the mySAP provider and access from SSIS through ADO but I wouldn’t count on the component to get certified. Other integration scenarios that the adapter pack will offer (IDOC and BAPI support) will be more likely to get certified.

Microsoft .NET Data Provider for mySAP Business Suite

Is this product SAP Certified?

I have read somewhere that any integration technology wrt SAP has to be SAP certified.

If no, what are the implications of using this in a project? will SAP refuse to support the customer because they are using a non-SAP certified product?

regards,

Abhishek.

I believe there could be issues with SAP support, but for a definitive answer, ask SAP themselves.|||

There are ongoing discussions between Microsoft and SAP at the highest levels, the provider for mySAP is not certified and there is no ETA at present.

A new adapter pack for SAP (also Siebel) is in development and expected for release in early CY08 with the Biztalk R2 adapter pack; it will include the functionality of the mySAP provider and access from SSIS through ADO but I wouldn’t count on the component to get certified. Other integration scenarios that the adapter pack will offer (IDOC and BAPI support) will be more likely to get certified.

Friday, March 9, 2012

method call works from .Net form and not from SQL CLR - EnterpriseLibrary used

Hello

I created a wrapper class for a function, and exposed it through CLR. However, if I call this function form SQL it blows up but if I call directly from a test Windows Form the call works fine.

The blow up is related to EnterpriseLibrary.Data, where my Queue class uses that library to do all data access call ops

Here's my wrapper class:

namespace inlineCLRsql{

public static class Wrapper{

public static void CallQueueEntry(int queueId, int deskNo, int missed){

inLineLib.Queue oQueue;

inLineLib.QueueEntry oQueueEntry;

oQueue = new inLineLib.Queue(queueId);

oQueueEntry = oQueue.callQueueEntry(deskNo, false);

Microsoft.SqlServer.Server.SqlContext.Pipe.Send(oQueueEntry.queueNum.ToString());

}

}

And this is my CLR SQL creation code:

CREATE PROC sp_CallQueueEntry

@.queueId int,

@.deskNo int,

@.missed int

AS

EXTERNAL NAME inLineLib.[inlineCLRsql.Wrapper].CallQueueEntry

GO

sp_CallQueueEntry 4,2,0

Here is what I get as a result

System.NullReferenceException: Object reference not set to an instance of an object.

System.NullReferenceException:

at Microsoft.Practices.EnterpriseLibrary.Data.DatabaseConfigurationView.get_DefaultName()

at Microsoft.Practices.EnterpriseLibrary.Data.DatabaseMapper.MapName(String name, IConfigurationSource configSource)

at Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ObjectBuilder.ConfigurationNameMappingStrategy.BuildUp(IBuilderContext context, Type t, Object existing, String id)

at Microsoft.Practices.ObjectBuilder.BuilderBase`1.DoBuildUp(IReadWriteLocator locator, Type typeToBuild, String idToBuild, Object existing, PolicyList[] transientPolicies)

at Microsoft.Practices.ObjectBuilder.BuilderBase`1.BuildUp(IReadWriteLocator locator, Type typeToBuild, String idToBuild, Object existing, PolicyList[] transientPolicies)

at Microsoft.Practices.ObjectBuilder.BuilderBase`1.BuildUp[TTypeToBuild](IReadWriteLocator locator, String idToBuild, Object existing, PolicyList[] transientPolicies)

at Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ObjectBuilder.EnterpriseLibraryFactory.BuildUp[T](IReadWriteLocator locator, IConfigurationSource configurationSource)

at Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ObjectBuilder.EnterpriseLibraryFactory.BuildUp[T](IConfigurationSource configurationSource)

at Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ObjectBuilder.NameTypeFactoryBase`1.CreateDefault()

at Microsoft.Practices.EnterpriseLibrary.Data.DatabaseFactory.CreateDatabase()

at inLineLib.Queue.getNextQueueEntry(Int32 servedBy)

at inLineLib.Queue.callQueueEntry(Int32 servedBy, Boolean callMissed)

at inlineCLRsql.Wrapper.CallQueueEntry(Int32 queueId, Int32 deskNo, Int32 missed)

What can I do to fix this?

Cheers

M

This is almost a total guess - I've never used EntLib. However, I found some one else hit this issue when EntLib was not able to find the database in the application config file: http://www.experts-exchange.com/Programming/Programming_Languages/C_Sharp/Q_21833370.html

This is likely to be the same problem you're facing. I believe you can solve this by running the Enterprise Library Config tool and specify your config file as sqlservr.exe.config in the same directory as sqlservr.exe. Or you can try copying and renaming the config file your Windows Form app is using.

Hope this works.

Steven

Saturday, February 25, 2012

Message: SQL Server does not exist or access denied.

Receiving the following error:
Message: SQL Server does not exist or access denied.
Source: .Net SqlClient Data Provider
at System.Data.SqlClient.ConnectionPool.GetConnection
(Boolean& isInTransaction)
at
System.Data.SqlClient.SqlConnectionPoolManager.Get PooledCon
nection(SqlConnectionString options, Boolean&
isInTransaction)
any clues please?
Check the Datasource property of the connection string to make sure the
server name /instance name is correct - you can check by creating a new text
document, renaming it to test.udl, opeing and setting the connection
properties, then closing it and open in notepad.
Make sure you can ping the server.
Make sure the DBA's or network dudes haven't closed port 1433
"Belinda" <anonymous@.discussions.microsoft.com> wrote in message
news:37a001c4a06d$7b5405c0$a501280a@.phx.gbl...
> Receiving the following error:
> Message: SQL Server does not exist or access denied.
> Source: .Net SqlClient Data Provider
> at System.Data.SqlClient.ConnectionPool.GetConnection
> (Boolean& isInTransaction)
> at
> System.Data.SqlClient.SqlConnectionPoolManager.Get PooledCon
> nection(SqlConnectionString options, Boolean&
> isInTransaction)
> any clues please?

Message Queue

Hi, I have a question, I don't know if it is possible but I have an
application (.NET) that executes queries against SQL Server 2000. I have an
scenario where the database maybe is offline. I have been working with MSMQ
to communicate between apps and send messages from SQL Server but my question
is if SQL Server can read from the queue.
I want to send the query to a queue and when SQL is up again read from the
queue and process the queries, is this possible?
Thanks
Hi
You need to do that in code. SQL Server 2000 does not process against
message queues.
Regards
Mike
"Salvador" wrote:

> Hi, I have a question, I don't know if it is possible but I have an
> application (.NET) that executes queries against SQL Server 2000. I have an
> scenario where the database maybe is offline. I have been working with MSMQ
> to communicate between apps and send messages from SQL Server but my question
> is if SQL Server can read from the queue.
> I want to send the query to a queue and when SQL is up again read from the
> queue and process the queries, is this possible?
> Thanks
>

Message Queue

Hi, I have a question, I don't know if it is possible but I have an
application (.NET) that executes queries against SQL Server 2000. I have an
scenario where the database maybe is offline. I have been working with MSMQ
to communicate between apps and send messages from SQL Server but my question
is if SQL Server can read from the queue.
I want to send the query to a queue and when SQL is up again read from the
queue and process the queries, is this possible?
ThanksHi
You need to do that in code. SQL Server 2000 does not process against
message queues.
Regards
Mike
"Salvador" wrote:
> Hi, I have a question, I don't know if it is possible but I have an
> application (.NET) that executes queries against SQL Server 2000. I have an
> scenario where the database maybe is offline. I have been working with MSMQ
> to communicate between apps and send messages from SQL Server but my question
> is if SQL Server can read from the queue.
> I want to send the query to a queue and when SQL is up again read from the
> queue and process the queries, is this possible?
> Thanks
>

Message Queue

Hi, I have a question, I don't know if it is possible but I have an
application (.NET) that executes queries against SQL Server 2000. I have an
scenario where the database maybe is offline. I have been working with MSMQ
to communicate between apps and send messages from SQL Server but my questio
n
is if SQL Server can read from the queue.
I want to send the query to a queue and when SQL is up again read from the
queue and process the queries, is this possible?
ThanksHi
You need to do that in code. SQL Server 2000 does not process against
message queues.
Regards
Mike
"Salvador" wrote:

> Hi, I have a question, I don't know if it is possible but I have an
> application (.NET) that executes queries against SQL Server 2000. I have a
n
> scenario where the database maybe is offline. I have been working with MSM
Q
> to communicate between apps and send messages from SQL Server but my quest
ion
> is if SQL Server can read from the queue.
> I want to send the query to a queue and when SQL is up again read from the
> queue and process the queries, is this possible?
> Thanks
>