Showing posts with label error. Show all posts
Showing posts with label error. Show all posts

Tuesday, March 27, 2012

binding textbox with SqlDataSource

Hi,

I wants to bind textbox with sqldatasource in c#.net so I am using following code and has following error...

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

Source Error:

Line 22:
Line 23: System.Data.DataView dv = (DataView) SqlDataSource1.Select(System.Web.UI.DataSourceSelectArguments.Empty);
Line 24: TextBox1.Text = dv[0]["Proid"].ToString();
Line 25:
Line 26: }


Please, anybody knows solution tell me

Show all your code here, please. Do you have the column "Proid" in your datasource and a TextBox1 in your ASPX page?

Binding error

Hi all

I have a form view which uses a SQL data source control to retrieve it's data from the sql express database

the form view is used for view,edit,delete and insert data into the database

in the insert mode I have two dropdownlists, where the second one is depending on the first one to retrieve the correct data from the data baseBUT

when selecting a value in the first dropdownlist it give me the following erro:

Databinding methods such as Eval(), XPath(), and Bind() can only be used in the context of a databound control.

Please How can do this

any help is appriciated

bye

You cannt do this using this method. There are many work arrounds out there, but the easiest I believe is the CascadingDropDown control which is part of the AJAX.NET Control Toolkit.

http://www.asp.net/ajax/ -- Install the AJAX.NET FRAMEWORK AND configure your site to use it.

You will need to:

1.) First Create a Web Service Class like as followed:

using System;using System.Web;using System.Collections;using System.Configuration;using System.Web.Services;using System.Web.Services.Protocols;using System.Collections.Generic;using AjaxControlToolkit;using System.Data;using System.Data.SqlClient;using System.Web.Script.Services;/// <summary>/// Cascading DropDownList AjaxControlToolkit Web Service/// </summary>[WebService(Namespace ="http://tempuri.org/")][WebServiceBinding(ConformsTo = WsiProfiles.BasicProfile1_1)][System.Web.Script.Services.ScriptService]public class DataService : System.Web.Services.WebService { private string connectionString =ConfigurationManager.ConnectionStrings["CarrierDBConnectionString"].ConnectionString; public DataService () {} [WebMethod] [System.Web.Script.Services.ScriptMethod()] public CascadingDropDownNameValue[] GetCarriers(string knownCategoryValues, string category) { List<CascadingDropDownNameValue> values = new List<CascadingDropDownNameValue>(); using (SqlConnection conn = new SqlConnection(connectionString)) { using (SqlCommand cmd = new SqlCommand("CARRIER_SELECT_ALL", conn)) { cmd.CommandType = CommandType.StoredProcedure; conn.Open(); SqlDataReader dr = cmd.ExecuteReader(CommandBehavior.CloseConnection); while (dr.Read()) { values.Add(new CascadingDropDownNameValue((string)dr["NAME"], dr["ID"].ToString())); } } } return values.ToArray(); } [WebMethod] [System.Web.Script.Services.ScriptMethod()] public CascadingDropDownNameValue[] GetSubsidiariesByCarrierID(string knownCategoryValues, string category) { List<CascadingDropDownNameValue> values = new List<CascadingDropDownNameValue>(); using (SqlConnection conn = new SqlConnection(connectionString)) { using (SqlCommand cmd = new SqlCommand("CARRIER_SELECT_SUBSIDIARY_BYID", conn)) { string[] categoryValues = knownCategoryValues.Split(':', ';'); int id = Convert.ToInt32(categoryValues[1]); cmd.CommandType = CommandType.StoredProcedure; cmd.Parameters.AddWithValue("@.id",id); conn.Open(); using (SqlDataReader dr = cmd.ExecuteReader(CommandBehavior.CloseConnection)) { if (dr.HasRows) { while (dr.Read()) { values.Add(new CascadingDropDownNameValue((string)dr["NAME"], dr["ID"].ToString())); } } } } }return values.ToArray(); }}

2.) Create the Actual Web Service

Click on the Project in the 'Solution Explorer' and 'Add New Item' and then select Web Service (for instance in this example: DataService.asmx)

3.) Hook up your ajax controls and dropdownlist


<asp:UpdatePanel ID="updatePnlInsert" runat="server">
<ContentTemplate>
<asp:DropDownList ID="ddlCarrierInsert" runat="server" AutoPostBack="True" Width="100%" DataSourceID="sqldsCarriersInsert" DataTextField="NAME" DataValueField="ID" SelectedValue='<%# Eval("CARRIER_ID") %>' AppendDataBoundItems="true">
<asp:ListItem Value="" Text="<select carrier>" />
</asp:DropDownList>
<br />
<asp:SqlDataSource ID="sqldsCarriersInsert" runat="server" ConnectionString="<%$ ConnectionStrings:CarrierDBConnectionString %>"
SelectCommand="CARRIER_SELECT_ALL" SelectCommandType="StoredProcedure" />

<asp:DropDownList ID="ddlSubInsert" runat="server" Width="100%" /><br />
<cc1:CascadingDropDown ID="cddCarrierInsert" runat="server"
TargetControlID="ddlSubInsert"
ParentControlID="ddlCarrierInsert"
Category="CARRIER"
LoadingText="[Loading Subsidiaries...]"
PromptText="<select subsidary>"
ServiceMethod="GetSubsidiariesByCarrierID"
ServicePath="DataService.asmx"
SelectedValue='<%# Eval("SUBSIDIARY_ID") %>'>
</cc1:CascadingDropDown>
</ContentTemplate>
<Triggers>
<asp:AsyncPostBackTrigger ControlID="ddlCarrierInsert" EventName="SelectedIndexChanged" />
</Triggers>
</asp:UpdatePanel>

Hope this helps.

Binding data to text box

I want to bind some data to a text box from sql server db. but when i run the page i get an error. here is my code.

<formid="form1"runat="server"><div><asp:SqlDataSourceID="SqlDataSource1"runat="server"ConnectionString="<%$ ConnectionStrings:imacsConn %>"SelectCommand="SELECT Reportnumber FROM [SummaryBlue] WHERE REPORTNUMBER = @.REPORTNUMBER"><SelectParameters><asp:QueryStringParameterName="REPORTNUMBER"QueryStringField="REPORTNo"Type="String"/>

</SelectParameters></asp:SqlDataSource><asp:TextBoxID="TextBox1"runat="server"Columns="<%$ ConnectionStrings:imacsConn %>"></asp:TextBox></div></form>

Error:

Exception Details:System.FormatException: Input string was not in a correct format.

Source Error:

Line 25: </SelectParameters>Line 26: </asp:SqlDataSource>Line 27: <asp:TextBox ID="TextBox1" runat="server" Columns="<%$ ConnectionStrings:imacsConn %>"></asp:TextBox></div>Line 28: </form>

The Columns property of a text box is how many characters wide it should be (an integer property). You are trying to assign it a string.

<asp:TextBoxID="TextBox1"runat="server"Columns="<%$ ConnectionStrings:imacsConn %>">

|||

Hi xbhavesh,

From your description, I understand you want to bind data to single TextBox. Base on my experience and research, SqlDataSource can be binded to List data-bound controls, but TextBox is not belong to them. So I think we cannot simply bind data to TextBox from SqlDataSource.

I find two solutions and hope they are helpful to you.

1. Bind the DataSource to a GridView, and then bind the GridView cell value to TextBox. Don't forget set GridView to not visible and call DataBind method when Page Load. Here is the sample code:

<asp:TextBoxID="TextBox1"runat="server"Text='<% #GridView1.Rows[0].Cells[0].Text%>'></asp:TextBox>

<asp:SqlDataSourceID="SqlDataSource1"runat="server"ConnectionString="<%$ ConnectionStrings:testConnectionString%>"

SelectCommand="SELECT [id] FROM [Table1] WHERE ([id] = 2)">

</asp:SqlDataSource>

<asp:GridViewID="GridView1"Visible="false"runat="server"DataSourceID="SqlDataSource1">

</asp:GridView>

protectedvoid Page_Load(object sender,EventArgs e)

{

TextBox1.DataBind();

}

2. Create your custom control to inherit DataBoundControl:

http://msdn2.microsoft.com/en-us/library/system.web.ui.webcontrols.databoundcontrol.aspx

P.S. We should bind to the Text property, not Columns.

Sunday, March 25, 2012

Bind failed on TCP port 1433

I installed SP3a and now I am getting this error message in the application
event log. Also, I can only connect to my server using namepipes. But
TCP/IP won't connect, even using 127.0.0.1 or the IP of my machine. The
event logs says that SQL is listening on 127.0.0.1:1433.
Can someone please help. I have not seen the answer and I have been
searching for 2 days now.
Log:
SQL server listening on 127.0.0.1: 1433.
SuperSocket Info: Bind failed on TCP port 1433.
SuperSocket info: (SpnRegister) : Error 1355.
Thanks in advance!
Dolph,
There are two scenarios that I can think of that will cause this situation.
1) You have bounced the SQL Server service programmatically (probably in
C++) and the service has been stopped and restarted too quickly. SQL
Server does not release the port quickly enough before it is restarted
and thinks that another service is using port 1433. The bind, then fails.
2) Another application is using port 1433.
You can check your ports using this on the commandline:
netstat -a
Look at the local address column for <machinename>:ms-sql-s or
<machinename>:1433
On my Inspiron laptop I get these results:
Active Connections
Proto Local Address Foreign Address State
TCP inspiron4100:ftp inspiron4100:0 LISTENING
TCP inspiron4100:http inspiron4100:0 LISTENING
TCP inspiron4100:epmap inspiron4100:0 LISTENING
TCP inspiron4100:https inspiron4100:0 LISTENING
TCP inspiron4100:microsoft-ds inspiron4100:0 LISTENING
TCP inspiron4100:1025 inspiron4100:0 LISTENING
TCP inspiron4100:ms-sql-s inspiron4100:0 LISTENING
TCP inspiron4100:2869 inspiron4100:0 LISTENING
TCP inspiron4100:3389 inspiron4100:0 LISTENING
TCP inspiron4100:1028 inspiron4100:0 LISTENING
TCP inspiron4100:1061 inspiron4100:0 LISTENING
TCP inspiron4100:1134 localhost:1135 ESTABLISHED
TCP inspiron4100:1135 localhost:1134 ESTABLISHED
TCP inspiron4100:netbios-ssn inspiron4100:0 LISTENING
TCP inspiron4100:1056 baym-cs91.msgr.hotmail.com:1863
ESTABLISHED
TCP inspiron4100:1130 82.152.34.166:50002 ESTABLISHED
TCP inspiron4100:1173 msnews.microsoft.com:nntp ESTABLISHED
TCP inspiron4100:1205 64.233.161.107:http ESTABLISHED
UDP inspiron4100:microsoft-ds *:*
UDP inspiron4100:isakmp *:*
UDP inspiron4100:1026 *:*
UDP inspiron4100:1069 *:*
UDP inspiron4100:1070 *:*
UDP inspiron4100:1131 *:*
UDP inspiron4100:ms-sql-m *:*
UDP inspiron4100:3456 *:*
UDP inspiron4100:4500 *:*
UDP inspiron4100:ntp *:*
UDP inspiron4100:1050 *:*
UDP inspiron4100:1057 *:*
UDP inspiron4100:1156 *:*
UDP inspiron4100:1900 *:*
UDP inspiron4100:ntp *:*
UDP inspiron4100:netbios-ns *:*
UDP inspiron4100:netbios-dgm *:*
UDP inspiron4100:1900 *:*
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Dolph Larson wrote:
> I installed SP3a and now I am getting this error message in the application
> event log. Also, I can only connect to my server using namepipes. But
> TCP/IP won't connect, even using 127.0.0.1 or the IP of my machine. The
> event logs says that SQL is listening on 127.0.0.1:1433.
> Can someone please help. I have not seen the answer and I have been
> searching for 2 days now.
> Log:
> SQL server listening on 127.0.0.1: 1433.
> SuperSocket Info: Bind failed on TCP port 1433.
> SuperSocket info: (SpnRegister) : Error 1355.
> Thanks in advance!
|||I didn't finish. :-/
If you still cannot find the cause of the problem, I suggest that you
reboot the server.
In the case of 1) the solution is to put a small pause in your code
before starting the MSSQLServer service again.
In the case of 2) you will need to ensure that your application uses
another port - perhaps there is a setting somewhere (maybe the registry)
where you can tweak this.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Mark Allison wrote:
> Dolph,
> There are two scenarios that I can think of that will cause this situation.
> 1) You have bounced the SQL Server service programmatically (probably in
> C++) and the service has been stopped and restarted too quickly. SQL
> Server does not release the port quickly enough before it is restarted
> and thinks that another service is using port 1433. The bind, then fails.
> 2) Another application is using port 1433.
> You can check your ports using this on the commandline:
> netstat -a
> Look at the local address column for <machinename>:ms-sql-s or
> <machinename>:1433
> On my Inspiron laptop I get these results:
>
> Active Connections
> Proto Local Address Foreign Address State
> TCP inspiron4100:ftp inspiron4100:0 LISTENING
> TCP inspiron4100:http inspiron4100:0 LISTENING
> TCP inspiron4100:epmap inspiron4100:0 LISTENING
> TCP inspiron4100:https inspiron4100:0 LISTENING
> TCP inspiron4100:microsoft-ds inspiron4100:0 LISTENING
> TCP inspiron4100:1025 inspiron4100:0 LISTENING
> TCP inspiron4100:ms-sql-s inspiron4100:0 LISTENING
> TCP inspiron4100:2869 inspiron4100:0 LISTENING
> TCP inspiron4100:3389 inspiron4100:0 LISTENING
> TCP inspiron4100:1028 inspiron4100:0 LISTENING
> TCP inspiron4100:1061 inspiron4100:0 LISTENING
> TCP inspiron4100:1134 localhost:1135 ESTABLISHED
> TCP inspiron4100:1135 localhost:1134 ESTABLISHED
> TCP inspiron4100:netbios-ssn inspiron4100:0 LISTENING
> TCP inspiron4100:1056 baym-cs91.msgr.hotmail.com:1863 ESTABLISHED
> TCP inspiron4100:1130 82.152.34.166:50002 ESTABLISHED
> TCP inspiron4100:1173 msnews.microsoft.com:nntp ESTABLISHED
> TCP inspiron4100:1205 64.233.161.107:http ESTABLISHED
> UDP inspiron4100:microsoft-ds *:*
> UDP inspiron4100:isakmp *:*
> UDP inspiron4100:1026 *:*
> UDP inspiron4100:1069 *:*
> UDP inspiron4100:1070 *:*
> UDP inspiron4100:1131 *:*
> UDP inspiron4100:ms-sql-m *:*
> UDP inspiron4100:3456 *:*
> UDP inspiron4100:4500 *:*
> UDP inspiron4100:ntp *:*
> UDP inspiron4100:1050 *:*
> UDP inspiron4100:1057 *:*
> UDP inspiron4100:1156 *:*
> UDP inspiron4100:1900 *:*
> UDP inspiron4100:ntp *:*
> UDP inspiron4100:netbios-ns *:*
> UDP inspiron4100:netbios-dgm *:*
> UDP inspiron4100:1900 *:*
>
>
>
|||Thanks for trying to help. Sadly, it can not be either case. I am not
doing anything with C++ and I have not downloaded any application lately that
is build on it. Esp. working with SQL server. I looked at the ports with
netstat -an and I see the port being listened by SQL Server. The server just
wont bind to that port. If I can't find a solution soon, I will be left to
do a re-install.
Dolph
"Mark Allison" wrote:

> I didn't finish. :-/
> If you still cannot find the cause of the problem, I suggest that you
> reboot the server.
> In the case of 1) the solution is to put a small pause in your code
> before starting the MSSQLServer service again.
> In the case of 2) you will need to ensure that your application uses
> another port - perhaps there is a setting somewhere (maybe the registry)
> where you can tweak this.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Mark Allison wrote:
>
|||Dolph Larson wrote:
> Can someone please help. I have not seen the answer and I have been
> searching for 2 days now.
For the benefit of any other poor ***s trying to work this one out,
here's what I just found...
We got the "SuperSocket Info: Bind failed on TCP port 1433" error, yet
netstat says the socket _is_ listening. TCPView (from the excellent
sysinternals site) confirms that it's listening, and that it's SQL
server that doing it.
Stumped despite much googling, I suddenly realised we'd recently
installed a new remote access _client_ on this server, Windows Secure
Application Manager from netscreen. This seems to work by hooking the
TCP stack with an LSP. Needless to say, it was this that was messing
up SQL server - using the diagnostics tool to remove the LSP sorted it
out straight away.
Thinking back, I've seen problems with an LSP before: some weird
problem with Norton Antivirus left a machine in a state where ipconfig
said it was dialled up OK, it could ping, but it couldn't do email or
http... Zapping the LSP sorted it (not that I can remember how I
removed it!)
Cheers,
Martin.

Bind failed on TCP port 1433

I installed SP3a and now I am getting this error message in the application
event log. Also, I can only connect to my server using namepipes. But
TCP/IP won't connect, even using 127.0.0.1 or the IP of my machine. The
event logs says that SQL is listening on 127.0.0.1:1433.
Can someone please help. I have not seen the answer and I have been
searching for 2 days now.
Log:
SQL server listening on 127.0.0.1: 1433.
SuperSocket Info: Bind failed on TCP port 1433.
SuperSocket info: (SpnRegister) : Error 1355.
Thanks in advance!Dolph,
There are two scenarios that I can think of that will cause this situation.
1) You have bounced the SQL Server service programmatically (probably in
C++) and the service has been stopped and restarted too quickly. SQL
Server does not release the port quickly enough before it is restarted
and thinks that another service is using port 1433. The bind, then fails.
2) Another application is using port 1433.
You can check your ports using this on the commandline:
netstat -a
Look at the local address column for <machinename>:ms-sql-s or
<machinename>:1433
On my Inspiron laptop I get these results:
Active Connections
Proto Local Address Foreign Address State
TCP inspiron4100:ftp inspiron4100:0 LISTENING
TCP inspiron4100:http inspiron4100:0 LISTENING
TCP inspiron4100:epmap inspiron4100:0 LISTENING
TCP inspiron4100:https inspiron4100:0 LISTENING
TCP inspiron4100:microsoft-ds inspiron4100:0 LISTENING
TCP inspiron4100:1025 inspiron4100:0 LISTENING
TCP inspiron4100:ms-sql-s inspiron4100:0 LISTENING
TCP inspiron4100:2869 inspiron4100:0 LISTENING
TCP inspiron4100:3389 inspiron4100:0 LISTENING
TCP inspiron4100:1028 inspiron4100:0 LISTENING
TCP inspiron4100:1061 inspiron4100:0 LISTENING
TCP inspiron4100:1134 localhost:1135 ESTABLISHED
TCP inspiron4100:1135 localhost:1134 ESTABLISHED
TCP inspiron4100:netbios-ssn inspiron4100:0 LISTENING
TCP inspiron4100:1056 baym-cs91.msgr.hotmail.com:1863
ESTABLISHED
TCP inspiron4100:1130 82.152.34.166:50002 ESTABLISHED
TCP inspiron4100:1173 msnews.microsoft.com:nntp ESTABLISHED
TCP inspiron4100:1205 64.233.161.107:http ESTABLISHED
UDP inspiron4100:microsoft-ds *:*
UDP inspiron4100:isakmp *:*
UDP inspiron4100:1026 *:*
UDP inspiron4100:1069 *:*
UDP inspiron4100:1070 *:*
UDP inspiron4100:1131 *:*
UDP inspiron4100:ms-sql-m *:*
UDP inspiron4100:3456 *:*
UDP inspiron4100:4500 *:*
UDP inspiron4100:ntp *:*
UDP inspiron4100:1050 *:*
UDP inspiron4100:1057 *:*
UDP inspiron4100:1156 *:*
UDP inspiron4100:1900 *:*
UDP inspiron4100:ntp *:*
UDP inspiron4100:netbios-ns *:*
UDP inspiron4100:netbios-dgm *:*
UDP inspiron4100:1900 *:*
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Dolph Larson wrote:
> I installed SP3a and now I am getting this error message in the applicatio
n
> event log. Also, I can only connect to my server using namepipes. But
> TCP/IP won't connect, even using 127.0.0.1 or the IP of my machine. The
> event logs says that SQL is listening on 127.0.0.1:1433.
> Can someone please help. I have not seen the answer and I have been
> searching for 2 days now.
> Log:
> SQL server listening on 127.0.0.1: 1433.
> SuperSocket Info: Bind failed on TCP port 1433.
> SuperSocket info: (SpnRegister) : Error 1355.
> Thanks in advance!|||I didn't finish. :-/
If you still cannot find the cause of the problem, I suggest that you
reboot the server.
In the case of 1) the solution is to put a small pause in your code
before starting the MSSQLServer service again.
In the case of 2) you will need to ensure that your application uses
another port - perhaps there is a setting somewhere (maybe the registry)
where you can tweak this.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Mark Allison wrote:
> Dolph,
> There are two scenarios that I can think of that will cause this situation
.
> 1) You have bounced the SQL Server service programmatically (probably in
> C++) and the service has been stopped and restarted too quickly. SQL
> Server does not release the port quickly enough before it is restarted
> and thinks that another service is using port 1433. The bind, then fails.
> 2) Another application is using port 1433.
> You can check your ports using this on the commandline:
> netstat -a
> Look at the local address column for <machinename>:ms-sql-s or
> <machinename>:1433
> On my Inspiron laptop I get these results:
>
> Active Connections
> Proto Local Address Foreign Address State
> TCP inspiron4100:ftp inspiron4100:0 LISTENING
> TCP inspiron4100:http inspiron4100:0 LISTENING
> TCP inspiron4100:epmap inspiron4100:0 LISTENING
> TCP inspiron4100:https inspiron4100:0 LISTENING
> TCP inspiron4100:microsoft-ds inspiron4100:0 LISTENING
> TCP inspiron4100:1025 inspiron4100:0 LISTENING
> TCP inspiron4100:ms-sql-s inspiron4100:0 LISTENING
> TCP inspiron4100:2869 inspiron4100:0 LISTENING
> TCP inspiron4100:3389 inspiron4100:0 LISTENING
> TCP inspiron4100:1028 inspiron4100:0 LISTENING
> TCP inspiron4100:1061 inspiron4100:0 LISTENING
> TCP inspiron4100:1134 localhost:1135 ESTABLISHED
> TCP inspiron4100:1135 localhost:1134 ESTABLISHED
> TCP inspiron4100:netbios-ssn inspiron4100:0 LISTENING
> TCP inspiron4100:1056 baym-cs91.msgr.hotmail.com:1863 ESTABLISHE
D
> TCP inspiron4100:1130 82.152.34.166:50002 ESTABLISHED
> TCP inspiron4100:1173 msnews.microsoft.com:nntp ESTABLISHED
> TCP inspiron4100:1205 64.233.161.107:http ESTABLISHED
> UDP inspiron4100:microsoft-ds *:*
> UDP inspiron4100:isakmp *:*
> UDP inspiron4100:1026 *:*
> UDP inspiron4100:1069 *:*
> UDP inspiron4100:1070 *:*
> UDP inspiron4100:1131 *:*
> UDP inspiron4100:ms-sql-m *:*
> UDP inspiron4100:3456 *:*
> UDP inspiron4100:4500 *:*
> UDP inspiron4100:ntp *:*
> UDP inspiron4100:1050 *:*
> UDP inspiron4100:1057 *:*
> UDP inspiron4100:1156 *:*
> UDP inspiron4100:1900 *:*
> UDP inspiron4100:ntp *:*
> UDP inspiron4100:netbios-ns *:*
> UDP inspiron4100:netbios-dgm *:*
> UDP inspiron4100:1900 *:*
>
>
>|||Thanks for trying to help. Sadly, it can not be either case. I am not
doing anything with C++ and I have not downloaded any application lately tha
t
is build on it. Esp. working with SQL server. I looked at the ports with
netstat -an and I see the port being listened by SQL Server. The server jus
t
wont bind to that port. If I can't find a solution soon, I will be left to
do a re-install.
Dolph
"Mark Allison" wrote:

> I didn't finish. :-/
> If you still cannot find the cause of the problem, I suggest that you
> reboot the server.
> In the case of 1) the solution is to put a small pause in your code
> before starting the MSSQLServer service again.
> In the case of 2) you will need to ensure that your application uses
> another port - perhaps there is a setting somewhere (maybe the registry)
> where you can tweak this.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Mark Allison wrote:
>|||Dolph Larson wrote:
> Can someone please help. I have not seen the answer and I have been
> searching for 2 days now.
For the benefit of any other poor ***s trying to work this one out,
here's what I just found...
We got the "SuperSocket Info: Bind failed on TCP port 1433" error, yet
netstat says the socket _is_ listening. TCPView (from the excellent
sysinternals site) confirms that it's listening, and that it's SQL
server that doing it.
Stumped despite much googling, I suddenly realised we'd recently
installed a new remote access _client_ on this server, Windows Secure
Application Manager from netscreen. This seems to work by hooking the
TCP stack with an LSP. Needless to say, it was this that was messing
up SQL server - using the diagnostics tool to remove the LSP sorted it
out straight away.
Thinking back, I've seen problems with an LSP before: some weird
problem with Norton Antivirus left a machine in a state where ipconfig
said it was dialled up OK, it could ping, but it couldn't do email or
http... Zapping the LSP sorted it (not that I can remember how I
removed it!)
Cheers,
Martin.

Bind failed on TCP port 1433

I installed SP3a and now I am getting this error message in the application
event log. Also, I can only connect to my server using namepipes. But
TCP/IP won't connect, even using 127.0.0.1 or the IP of my machine. The
event logs says that SQL is listening on 127.0.0.1:1433.
Can someone please help. I have not seen the answer and I have been
searching for 2 days now.
Log:
SQL server listening on 127.0.0.1: 1433.
SuperSocket Info: Bind failed on TCP port 1433.
SuperSocket info: (SpnRegister) : Error 1355.
Thanks in advance!Dolph,
There are two scenarios that I can think of that will cause this situation.
1) You have bounced the SQL Server service programmatically (probably in
C++) and the service has been stopped and restarted too quickly. SQL
Server does not release the port quickly enough before it is restarted
and thinks that another service is using port 1433. The bind, then fails.
2) Another application is using port 1433.
You can check your ports using this on the commandline:
netstat -a
Look at the local address column for <machinename>:ms-sql-s or
<machinename>:1433
On my Inspiron laptop I get these results:
Active Connections
Proto Local Address Foreign Address State
TCP inspiron4100:ftp inspiron4100:0 LISTENING
TCP inspiron4100:http inspiron4100:0 LISTENING
TCP inspiron4100:epmap inspiron4100:0 LISTENING
TCP inspiron4100:https inspiron4100:0 LISTENING
TCP inspiron4100:microsoft-ds inspiron4100:0 LISTENING
TCP inspiron4100:1025 inspiron4100:0 LISTENING
TCP inspiron4100:ms-sql-s inspiron4100:0 LISTENING
TCP inspiron4100:2869 inspiron4100:0 LISTENING
TCP inspiron4100:3389 inspiron4100:0 LISTENING
TCP inspiron4100:1028 inspiron4100:0 LISTENING
TCP inspiron4100:1061 inspiron4100:0 LISTENING
TCP inspiron4100:1134 localhost:1135 ESTABLISHED
TCP inspiron4100:1135 localhost:1134 ESTABLISHED
TCP inspiron4100:netbios-ssn inspiron4100:0 LISTENING
TCP inspiron4100:1056 baym-cs91.msgr.hotmail.com:1863
ESTABLISHED
TCP inspiron4100:1130 82.152.34.166:50002 ESTABLISHED
TCP inspiron4100:1173 msnews.microsoft.com:nntp ESTABLISHED
TCP inspiron4100:1205 64.233.161.107:http ESTABLISHED
UDP inspiron4100:microsoft-ds *:*
UDP inspiron4100:isakmp *:*
UDP inspiron4100:1026 *:*
UDP inspiron4100:1069 *:*
UDP inspiron4100:1070 *:*
UDP inspiron4100:1131 *:*
UDP inspiron4100:ms-sql-m *:*
UDP inspiron4100:3456 *:*
UDP inspiron4100:4500 *:*
UDP inspiron4100:ntp *:*
UDP inspiron4100:1050 *:*
UDP inspiron4100:1057 *:*
UDP inspiron4100:1156 *:*
UDP inspiron4100:1900 *:*
UDP inspiron4100:ntp *:*
UDP inspiron4100:netbios-ns *:*
UDP inspiron4100:netbios-dgm *:*
UDP inspiron4100:1900 *:*
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Dolph Larson wrote:
> I installed SP3a and now I am getting this error message in the application
> event log. Also, I can only connect to my server using namepipes. But
> TCP/IP won't connect, even using 127.0.0.1 or the IP of my machine. The
> event logs says that SQL is listening on 127.0.0.1:1433.
> Can someone please help. I have not seen the answer and I have been
> searching for 2 days now.
> Log:
> SQL server listening on 127.0.0.1: 1433.
> SuperSocket Info: Bind failed on TCP port 1433.
> SuperSocket info: (SpnRegister) : Error 1355.
> Thanks in advance!|||I didn't finish. :-/
If you still cannot find the cause of the problem, I suggest that you
reboot the server.
In the case of 1) the solution is to put a small pause in your code
before starting the MSSQLServer service again.
In the case of 2) you will need to ensure that your application uses
another port - perhaps there is a setting somewhere (maybe the registry)
where you can tweak this.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Mark Allison wrote:
> Dolph,
> There are two scenarios that I can think of that will cause this situation.
> 1) You have bounced the SQL Server service programmatically (probably in
> C++) and the service has been stopped and restarted too quickly. SQL
> Server does not release the port quickly enough before it is restarted
> and thinks that another service is using port 1433. The bind, then fails.
> 2) Another application is using port 1433.
> You can check your ports using this on the commandline:
> netstat -a
> Look at the local address column for <machinename>:ms-sql-s or
> <machinename>:1433
> On my Inspiron laptop I get these results:
>
> Active Connections
> Proto Local Address Foreign Address State
> TCP inspiron4100:ftp inspiron4100:0 LISTENING
> TCP inspiron4100:http inspiron4100:0 LISTENING
> TCP inspiron4100:epmap inspiron4100:0 LISTENING
> TCP inspiron4100:https inspiron4100:0 LISTENING
> TCP inspiron4100:microsoft-ds inspiron4100:0 LISTENING
> TCP inspiron4100:1025 inspiron4100:0 LISTENING
> TCP inspiron4100:ms-sql-s inspiron4100:0 LISTENING
> TCP inspiron4100:2869 inspiron4100:0 LISTENING
> TCP inspiron4100:3389 inspiron4100:0 LISTENING
> TCP inspiron4100:1028 inspiron4100:0 LISTENING
> TCP inspiron4100:1061 inspiron4100:0 LISTENING
> TCP inspiron4100:1134 localhost:1135 ESTABLISHED
> TCP inspiron4100:1135 localhost:1134 ESTABLISHED
> TCP inspiron4100:netbios-ssn inspiron4100:0 LISTENING
> TCP inspiron4100:1056 baym-cs91.msgr.hotmail.com:1863 ESTABLISHED
> TCP inspiron4100:1130 82.152.34.166:50002 ESTABLISHED
> TCP inspiron4100:1173 msnews.microsoft.com:nntp ESTABLISHED
> TCP inspiron4100:1205 64.233.161.107:http ESTABLISHED
> UDP inspiron4100:microsoft-ds *:*
> UDP inspiron4100:isakmp *:*
> UDP inspiron4100:1026 *:*
> UDP inspiron4100:1069 *:*
> UDP inspiron4100:1070 *:*
> UDP inspiron4100:1131 *:*
> UDP inspiron4100:ms-sql-m *:*
> UDP inspiron4100:3456 *:*
> UDP inspiron4100:4500 *:*
> UDP inspiron4100:ntp *:*
> UDP inspiron4100:1050 *:*
> UDP inspiron4100:1057 *:*
> UDP inspiron4100:1156 *:*
> UDP inspiron4100:1900 *:*
> UDP inspiron4100:ntp *:*
> UDP inspiron4100:netbios-ns *:*
> UDP inspiron4100:netbios-dgm *:*
> UDP inspiron4100:1900 *:*
>
>
>|||Thanks for trying to help. Sadly, it can not be either case. I am not
doing anything with C++ and I have not downloaded any application lately that
is build on it. Esp. working with SQL server. I looked at the ports with
netstat -an and I see the port being listened by SQL Server. The server just
wont bind to that port. If I can't find a solution soon, I will be left to
do a re-install. :(
Dolph
"Mark Allison" wrote:
> I didn't finish. :-/
> If you still cannot find the cause of the problem, I suggest that you
> reboot the server.
> In the case of 1) the solution is to put a small pause in your code
> before starting the MSSQLServer service again.
> In the case of 2) you will need to ensure that your application uses
> another port - perhaps there is a setting somewhere (maybe the registry)
> where you can tweak this.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Mark Allison wrote:
> > Dolph,
> >
> > There are two scenarios that I can think of that will cause this situation.
> >
> > 1) You have bounced the SQL Server service programmatically (probably in
> > C++) and the service has been stopped and restarted too quickly. SQL
> > Server does not release the port quickly enough before it is restarted
> > and thinks that another service is using port 1433. The bind, then fails.
> >
> > 2) Another application is using port 1433.
> >
> > You can check your ports using this on the commandline:
> >
> > netstat -a
> >
> > Look at the local address column for <machinename>:ms-sql-s or
> > <machinename>:1433
> >
> > On my Inspiron laptop I get these results:
> >
> >
> > Active Connections
> >
> > Proto Local Address Foreign Address State
> > TCP inspiron4100:ftp inspiron4100:0 LISTENING
> > TCP inspiron4100:http inspiron4100:0 LISTENING
> > TCP inspiron4100:epmap inspiron4100:0 LISTENING
> > TCP inspiron4100:https inspiron4100:0 LISTENING
> > TCP inspiron4100:microsoft-ds inspiron4100:0 LISTENING
> > TCP inspiron4100:1025 inspiron4100:0 LISTENING
> > TCP inspiron4100:ms-sql-s inspiron4100:0 LISTENING
> > TCP inspiron4100:2869 inspiron4100:0 LISTENING
> > TCP inspiron4100:3389 inspiron4100:0 LISTENING
> > TCP inspiron4100:1028 inspiron4100:0 LISTENING
> > TCP inspiron4100:1061 inspiron4100:0 LISTENING
> > TCP inspiron4100:1134 localhost:1135 ESTABLISHED
> > TCP inspiron4100:1135 localhost:1134 ESTABLISHED
> > TCP inspiron4100:netbios-ssn inspiron4100:0 LISTENING
> > TCP inspiron4100:1056 baym-cs91.msgr.hotmail.com:1863 ESTABLISHED
> > TCP inspiron4100:1130 82.152.34.166:50002 ESTABLISHED
> > TCP inspiron4100:1173 msnews.microsoft.com:nntp ESTABLISHED
> > TCP inspiron4100:1205 64.233.161.107:http ESTABLISHED
> > UDP inspiron4100:microsoft-ds *:*
> > UDP inspiron4100:isakmp *:*
> > UDP inspiron4100:1026 *:*
> > UDP inspiron4100:1069 *:*
> > UDP inspiron4100:1070 *:*
> > UDP inspiron4100:1131 *:*
> > UDP inspiron4100:ms-sql-m *:*
> > UDP inspiron4100:3456 *:*
> > UDP inspiron4100:4500 *:*
> > UDP inspiron4100:ntp *:*
> > UDP inspiron4100:1050 *:*
> > UDP inspiron4100:1057 *:*
> > UDP inspiron4100:1156 *:*
> > UDP inspiron4100:1900 *:*
> > UDP inspiron4100:ntp *:*
> > UDP inspiron4100:netbios-ns *:*
> > UDP inspiron4100:netbios-dgm *:*
> > UDP inspiron4100:1900 *:*
> >
> >
> >
> >
> >
>|||Dolph Larson wrote:
> Can someone please help. I have not seen the answer and I have been
> searching for 2 days now.
For the benefit of any other poor ***s trying to work this one out,
here's what I just found...
We got the "SuperSocket Info: Bind failed on TCP port 1433" error, yet
netstat says the socket _is_ listening. TCPView (from the excellent
sysinternals site) confirms that it's listening, and that it's SQL
server that doing it.
Stumped despite much googling, I suddenly realised we'd recently
installed a new remote access _client_ on this server, Windows Secure
Application Manager from netscreen. This seems to work by hooking the
TCP stack with an LSP. Needless to say, it was this that was messing
up SQL server - using the diagnostics tool to remove the LSP sorted it
out straight away.
Thinking back, I've seen problems with an LSP before: some weird
problem with Norton Antivirus left a machine in a state where ipconfig
said it was dialled up OK, it could ping, but it couldn't do email or
http... Zapping the LSP sorted it (not that I can remember how I
removed it!)
Cheers,
Martin.

Bind failed on TCP port 1044.

I am getting this error in the Event Viewer and the clients are unable to
connect to the SQL server. What is wrong?
PLEASE HELP!!
ScottHi
You SQL Server is configured not to use the standard 1433 port, but this is
not a problem in itself.
By the time SQL Server starts, there is another application that is using
the port 1044. This results in SQL Server not being able to use it. You need
to either stop that application or configure SQL Server to use a different
port. Configure the port though Server Network Utility in the SQL Server men
u.
Regards
Mike
"scottdog129" wrote:

> I am getting this error in the Event Viewer and the clients are unable to
> connect to the SQL server. What is wrong?
> PLEASE HELP!!
> Scottsql

Bind failed on TCP port 1044.

I am getting this error in the Event Viewer and the clients are unable to
connect to the SQL server. What is wrong?
PLEASE HELP!!
Scott
Hi
You SQL Server is configured not to use the standard 1433 port, but this is
not a problem in itself.
By the time SQL Server starts, there is another application that is using
the port 1044. This results in SQL Server not being able to use it. You need
to either stop that application or configure SQL Server to use a different
port. Configure the port though Server Network Utility in the SQL Server menu.
Regards
Mike
"scottdog129" wrote:

> I am getting this error in the Event Viewer and the clients are unable to
> connect to the SQL server. What is wrong?
> PLEASE HELP!!
> Scott

Binary_double Oracle data type support

I'm using RS 2000 and I'm getting an "unsupported Oracle data type 101 encountered" error when attempting to retrieve data from a dataset based on a plsql stored procedure. I'm assuming this is related to a recent update on our Oracle 10g database to convert columns from number to binary_double.

Can anyone confirm if this is the case, and suggest a work-around? Is binary_double supported in RS 2005?

Thanks

RS uses MS .NET provider for Oracle which currently does not support binary_float/double.

The possible workaround is to cast binary_float columns to number in your SQL statement

select cast(my_bin_float_col as number) from ...

binary_checksum and rowsize error?

Hi,
I can see that by using the object ID rather that the object name, the
following SQL query works. Has anybody got any idea what is causing the
error?
-- Works OK
select o.id
,checksum_agg(binary_checksum(=ADm.text))
from sysobjects o
,syscomments m
where o.id =3D m.id
and o.xtype in ('FN','IF','P','TF','TR','V')
group by o.id
-- Error
-- Server: Msg 1540, Level 16, State 1, Line 1
-- Cannot sort a row of size 8096, which is greater than the
-- allowable maximum of 8094.
select object_name(o.id)
,checksum_agg(binary_checksum(=ADm.text))
from sysobjects o
,syscomments m
where o.id =3D m.id
and o.xtype in ('FN','IF','P','TF','TR','V')
group by object_name(o.id)
-- Error
-- Server: Msg 1540, Level 16, State 1, Line 1
-- Cannot sort a row of size 8096, which is greater than the
-- allowable maximum of 8094.
select o.name
,checksum_agg(binary_checksum(=ADm.text))
from sysobjects o
,syscomments m
where o.id =3D m.id
and o.xtype in ('FN','IF','P','TF','TR','V')
group by o.name
-- Workaround
select getdate()
,object_name(x.id)
,check_sum
from (select m.id
,checksum_agg(binary_checksum(=ADm.text)) as check_sum
from syscomments m
inner join
sysobjects o
on m.id =3D o.id
where o.xtype in ('FN','IF','P','TF','TR','V')
group by m.id) as x=20
Regards=20
LiamIt works at my database. The cause is that there is a row in syscomments
that has a rather long value in the text column, and that pushes the rowsize
of an intermediate result set over the maximum row size. SQL Server uses
only an estimate from the statistics to determine how large the largest row
can be in any intermediate result sets, so it can create an execution plan
that might fail with very long rows, especially when the very long rows are
rare. You can avoid this by using OPTION(ROBUST PLAN).
Jacco Schalkwijk
SQL Server MVP
<liam.caffrey@.gmail.com> wrote in message
news:1117784150.912579.240300@.g14g2000cwa.googlegroups.com...
Hi,
I can see that by using the object ID rather that the object name, the
following SQL query works. Has anybody got any idea what is causing the
error?
-- Works OK
select o.id
,checksum_agg(binary_checksum(_m.text))
from sysobjects o
,syscomments m
where o.id = m.id
and o.xtype in ('FN','IF','P','TF','TR','V')
group by o.id
-- Error
-- Server: Msg 1540, Level 16, State 1, Line 1
-- Cannot sort a row of size 8096, which is greater than the
-- allowable maximum of 8094.
select object_name(o.id)
,checksum_agg(binary_checksum(_m.text))
from sysobjects o
,syscomments m
where o.id = m.id
and o.xtype in ('FN','IF','P','TF','TR','V')
group by object_name(o.id)
-- Error
-- Server: Msg 1540, Level 16, State 1, Line 1
-- Cannot sort a row of size 8096, which is greater than the
-- allowable maximum of 8094.
select o.name
,checksum_agg(binary_checksum(_m.text))
from sysobjects o
,syscomments m
where o.id = m.id
and o.xtype in ('FN','IF','P','TF','TR','V')
group by o.name
-- Workaround
select getdate()
,object_name(x.id)
,check_sum
from (select m.id
,checksum_agg(binary_checksum(_m.text)) as check_sum
from syscomments m
inner join
sysobjects o
on m.id = o.id
where o.xtype in ('FN','IF','P','TF','TR','V')
group by m.id) as x
Regards
Liam

Tuesday, March 20, 2012

Bigint handling

I have a subreport that gives me the error :
An error occurred while executing the subreport
â'PlanLocationbyItemNumberLocations_subreportâ': Error during processing of
â'item_idâ' report parameter.
Preview complete -- 0 errors, 1 warnings
This problem only occurs when the value of the bigint in field "item_id"
(which is passed as a parmater to the subreport) is very large. Since I
can't find a report parameter option of bigint, only integer, what options do
I have?You can use Float instead of Integer.
--
| Thread-Topic: Bigint handling
| thread-index: AcS7okSK6UOq2ghATlGlwu+m0Ima4g==| X-WBNR-Posting-Host: 65.207.30.6
| From: "=?Utf-8?B?S0I=?=" <KB@.discussions.microsoft.com>
| Subject: Bigint handling
| Date: Tue, 26 Oct 2004 14:25:08 -0700
| Lines: 12
| Message-ID: <384D7CB6-0F38-4BCC-B8A7-DC550E2EE13C@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 8bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.reportingsvcs:33239
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
|
|
| I have a subreport that gives me the error :
| An error occurred while executing the subreport
| â'PlanLocationbyItemNumberLocations_subreportâ': Error during
processing of
| â'item_idâ' report parameter.
| Preview complete -- 0 errors, 1 warnings
|
| This problem only occurs when the value of the bigint in field "item_id"
| (which is passed as a parmater to the subreport) is very large. Since I
| can't find a report parameter option of bigint, only integer, what
options do
| I have?
|

bigint - Arithmetic overflow

Hi,

I am getting

Server: Msg 232, Level 16, State 3, Line 1
Arithmetic overflow error for type int, value =
1152921504606847000.000000.

when I do

select power(2,60) in query analyzer

then I tried

declare @.b bigint
select @.b = power(2,60)

same error.

I tried

select convert(bigint,power(2,60)) no luck

Is there any way to tell sql server to use bigint when it
calculate power(2,60)

Ram.This worked:

declare @.b bigint
select @.b = power(cast(2 as bigint),60)
select @.b

-------
1152921504606846976

(1 row(s) affected)|||Originally posted by rdjabarov
This worked:

declare @.b bigint
select @.b = power(cast(2 as bigint),60)
select @.b

-------
1152921504606846976

(1 row(s) affected)

much thanks !!!!!

bigint - Arithmetic overflow

Hi,
I am getting
Server: Msg 232, Level 16, State 3, Line 1
Arithmetic overflow error for type int, value = 1152921504606847000.000000.
when I do
select power(2,60) in query analyzer
then I tried
declare @.b bigint
select @.b = power(2,60)
same error.
I tried
select convert(bigint,power(2,60)) no luck
Is there any way to tell sql server to use bigint when it
calculate power(2,60)
Ram.declare @.t bigint
select @.t = 2
select power(@.t,60)
>--Original Message--
>Hi,
>I am getting
>Server: Msg 232, Level 16, State 3, Line 1
>Arithmetic overflow error for type int, value =>1152921504606847000.000000.
>when I do
>select power(2,60) in query analyzer
>then I tried
>declare @.b bigint
>select @.b = power(2,60)
>same error.
>I tried
>select convert(bigint,power(2,60)) no luck
>Is there any way to tell sql server to use bigint when it
>calculate power(2,60)
>Ram.
>
>
>.
>|||power function will return value of same type as input
type, so instead of constant 2 (which is integer) use a
variable defined as bigint, try following:
declare @.a bigint, @.b bigint
select @.a = 2
select @.b = power(@.a,60)
print @.b
hope this helps.
>--Original Message--
>Hi,
>I am getting
>Server: Msg 232, Level 16, State 3, Line 1
>Arithmetic overflow error for type int, value =>1152921504606847000.000000.
>when I do
>select power(2,60) in query analyzer
>then I tried
>declare @.b bigint
>select @.b = power(2,60)
>same error.
>I tried
>select convert(bigint,power(2,60)) no luck
>Is there any way to tell sql server to use bigint when it
>calculate power(2,60)
>Ram.
>
>
>.
>

Monday, March 19, 2012

BIDS error for data task

Does anybody know what this means? I have a SQL source (OLEDB) going to a script transformation as a destination:
[DTS.Pipeline] Warning: Component "Add Schemas" (32) has been removed from the Data Flow task because its output is not used and its inputs have no side effects. If the component is required, then the HasSideEffects property on at least one of its inputs should be set to true, or its output should be connected to something.
Add Schemas is the script transformation destination. I can't find a HasSideEffects property, and have no idea why this would be a problem.ETL(extraction transformation and loading) related, try this link for more info. Hope this helps.
http://www.sqlis.com/

BIDS (VS 2005 Professional) Hangs

Occasionally, when I try to edit a package I get an error. Visual studio is busyfound VS hanged.

It is specific to my machine or a common problem.

You are not the only person. For me, VS usually hangs for only a minute or so.

|||I hope it will be corrected in 2008 version.

BIDS (VS 2005 Professional) Hangs

Occasionally, when I try to edit a package I get an error. Visual studio is busyfound VS hanged.

It is specific to my machine or a common problem.

You are not the only person. For me, VS usually hangs for only a minute or so.

|||I hope it will be corrected in 2008 version.

Sunday, March 11, 2012

BIDS - Error on design surface of Calculation tab in Cube

Has anyone seen this?

Within 'Business Intelligence Development Studio' (BIDS) with a cube opened and the calculations tab selected, the design surface displays a message that reads:

Unexpected error occurred: 'Error in the application.'

This occurs in any project I open and it still occurs when I restart BIDS or the computer itself.

Any ideas? Can anyone suggest a remedy?

hello,

this might be caused by version mismatch between some binaries. i'd suggest checking the versions of msmdlocal.dll and msmgdsrv.dll and making sure that the ones installed into %ProgramFiles%\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\ are the same as those in %ProgramFiles%\Common Files\System\Ole DB\ (if they are not then try updating the ones in the PrivateAssemblies with the ones from ole db; you might want to save the original ones as to be able to get back to original state just in case...)

hope this helps,

|||

I had already seen a similar post noting this as the possible cause so I checked the file versions in the appropriate folders an found no missmatch.

From there I went on to install the latest hotfix (2153) to see if that would clear up the problem. It did not.

After consulting with a friend I decided do a complete reinstall of SQL Server 2005 and related tools and such.

After the complete reinstall (and before a SP1 update) the problem still existed. I still recieve the error on the design surface of the Calculation tab for any cube I open.

I am currently trying to install SP1 and encounterring problems.

With my first attempt the 'Installation Progress' window for Service Pack 1 Setup showed product 'Analysis Services' status as "Failed". Here are the contents of the log file after it completed.

09/27/2006 09:26:44.282 ================================================================================
09/27/2006 09:26:44.314 Hotfix package launched
09/27/2006 09:31:58.503 Attempting to install instance: SQL Server Native Client
09/27/2006 09:31:58.534 Attempting to install target: L-0960
09/27/2006 09:31:58.581 Attempting to install file: sqlncli.msi
09/27/2006 09:31:58.675 Attempting to install file: \\L-0960\c$\06f6082a049155a5f4e3ece3b75f69\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 09:31:58.722 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
09/27/2006 09:31:58.737 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 09:31:58.753 Failed to read registry key: Debug
09/27/2006 09:32:01.329 MSP returned 0: The action completed successfully.
09/27/2006 09:32:01.501 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 09:32:01.689 Failed to read registry key: Debug
09/27/2006 09:32:01.704 Successfully installed file: \\L-0960\c$\06f6082a049155a5f4e3ece3b75f69\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 09:32:01.720 Successfully installed target: L-0960
09/27/2006 09:32:01.735 Successfully installed instance: SQL Server Native Client
09/27/2006 09:32:01.751
09/27/2006 09:32:01.751 Product Status Summary:
09/27/2006 09:32:01.767 Product: SQL Server Native Client
09/27/2006 09:32:01.782 SQL Server Native Client (RTM ) - Success
09/27/2006 09:32:01.782
09/27/2006 09:32:01.798 Product: Setup Support Files
09/27/2006 09:32:01.814 Setup Support Files (RTM ) - Not Applied
09/27/2006 09:32:01.829
09/27/2006 09:32:01.829 Product: Database Services
09/27/2006 09:32:01.845 Database Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:01.892 Analysis Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:01.923 Reporting Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:01.970
09/27/2006 09:32:01.985 Product: Notification Services
09/27/2006 09:32:02.017 Notification Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:02.048
09/27/2006 09:32:02.110 Product: Integration Services
09/27/2006 09:32:02.141 Integration Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:02.173
09/27/2006 09:32:02.204 Product: Client Components
09/27/2006 09:32:02.251 Client Components (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:02.282
09/27/2006 09:32:02.313 Product: MSXML 6.0 Parser
09/27/2006 09:32:02.360 MSXML 6.0 Parser (RTM ) - Not Applied
09/27/2006 09:32:02.391
09/27/2006 09:32:02.547 Product: SQLXML4
09/27/2006 09:32:02.641 SQLXML4 (RTM ) - Not Applied
09/27/2006 09:32:02.704
09/27/2006 09:32:02.735 Product: Backward Compatibility
09/27/2006 09:32:02.782 Backward Compatibility (RTM ) - Not Applied
09/27/2006 09:32:02.813
09/27/2006 09:32:02.844 Product: Microsoft SQL Server VSS Writer
09/27/2006 09:32:02.875 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
09/27/2006 09:32:02.907

After a restart I tried the Service Pack 1 installation again.

On this second attempt the 'Installation Progress' window for Service Pack 1 Setup showed product 'Analysis Services' status as "Warning".

Here are the contents of the log file after it completed.

09/27/2006 10:55:37.182 ================================================================================
09/27/2006 10:55:37.260 Hotfix package launched
09/27/2006 11:01:04.649 Attempting to install instance: SQL Server Native Client
09/27/2006 11:01:04.696 Attempting to install target: L-0960
09/27/2006 11:01:04.727 Attempting to install file: sqlncli.msi
09/27/2006 11:01:04.805 Attempting to install file: \\L-0960\c$\c13f3012d4415b5c63bc\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 11:01:04.868 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
09/27/2006 11:01:04.868 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 11:01:04.884 Failed to read registry key: Debug
09/27/2006 11:01:10.185 MSP returned 0: The action completed successfully.
09/27/2006 11:01:10.498 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 11:01:10.545 Failed to read registry key: Debug
09/27/2006 11:01:10.576 Successfully installed file: \\L-0960\c$\c13f3012d4415b5c63bc\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 11:01:10.608 Successfully installed target: L-0960
09/27/2006 11:01:10.608 Successfully installed instance: SQL Server Native Client
09/27/2006 11:01:10.623
09/27/2006 11:01:10.639 Product Status Summary:
09/27/2006 11:01:10.639 Product: SQL Server Native Client
09/27/2006 11:01:10.655 SQL Server Native Client (RTM ) - Success
09/27/2006 11:01:10.670
09/27/2006 11:01:10.686 Product: Setup Support Files
09/27/2006 11:01:10.686 Setup Support Files (RTM ) - Not Applied
09/27/2006 11:01:10.701
09/27/2006 11:01:10.717 Product: Database Services
09/27/2006 11:01:10.717 Database Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.733 Analysis Services (RTM 1399 ENU) - Not Applied
09/27/2006 11:01:10.748 Reporting Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.764
09/27/2006 11:01:10.764 Product: Notification Services
09/27/2006 11:01:10.780 Notification Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.795
09/27/2006 11:01:10.795 Product: Integration Services
09/27/2006 11:01:10.811 Integration Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.827
09/27/2006 11:01:10.842 Product: Client Components
09/27/2006 11:01:10.842 Client Components (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.858
09/27/2006 11:01:10.873 Product: MSXML 6.0 Parser
09/27/2006 11:01:10.873 MSXML 6.0 Parser (RTM ) - Not Applied
09/27/2006 11:01:10.889
09/27/2006 11:01:10.905 Product: SQLXML4
09/27/2006 11:01:10.920 SQLXML4 (RTM ) - Not Applied
09/27/2006 11:01:10.920
09/27/2006 11:01:10.936 Product: Backward Compatibility
09/27/2006 11:01:10.952 Backward Compatibility (RTM ) - Not Applied
09/27/2006 11:01:10.952
09/27/2006 11:01:10.967 Product: Microsoft SQL Server VSS Writer
09/27/2006 11:01:10.983 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
09/27/2006 11:01:10.983

What doe all this mean? How do I fix the Business Intelligence Development Studio (BIDS) in its working with Analysis Services cubes?

|||

By the way the files noted earlier "msmgdsrv.dll" and "msmdlocal.dll" are still consistant in date betwee tne two folders.

Within BIDS I can make a connection to the database server. I know this because on the Browser tab of the cube I can drag different measures and dimensions onto the design surface and get results returned but I cannot view the cube's calculations. The design surface tells me;

"Unexpected error occurred: 'Error in the application.'"

At the bottom of the design window starts out with a message that says:

Unable to query the 'Adventure Works DW' cube: 'A connection cannot be made. Ensure that he server is running.'. The cube must be queried for you to browse data or meta data. Click here to retry the connection.

When I click the message at the bottom of the screen goes away, but the message on the design surface remains.

It appears that the needed connection for the calucations tabe is made because the Metadata tab, is populated with the proper measures and dimensions of the cube.

What is the cause of all this?

|||

hello,

the symptoms of the error definitely suggest files got mismatched... so, if the 2 files are consistent between PrivateAssemblies and the Ole Db folder, then perhaps the 2 files are inconsistent between themselves in both places. what are the file versions/modification dates on msmgdsrv.dll and msmdlocal.dll (in both places) ?

i'm not sure why setup fails for you...

thanks,

|||

> what are the file versions/modification dates on msmgdsrv.dll and msmdlocal.dll (in both places) ?

Here are the locations, filenames, versions, and date\time

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\

Filename: msmgdsrv.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM

Filename: msmdlocal.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\

Filename: msmgdsrv.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM

Filename: msmdlocal.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM

Before the complete Re-load of SQLS2k5 I had updated to the most recent hotfix (9.0.2153.0). At that time these files were also consistent in version and date and the same problem I now experience was there.

|||

hello,

actually, as i mentioned before, it's important to check the versions compared to: %ProgramFiles%\Common Files\System\Ole DB\ (and not %ProgramFiles%\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\). i.e. can you please check the files in that (Ole Db) directory?

thanks,

|||

Here it is:

C:\Program Files\Common Files\System\Ole DB\

Filename: msmgdsrv.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM

Filename: msmdlocal.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM

So what action do I take? Do I rename the existing (older) files (to something like msmgdsrv.dll.old and msmdlocal.dll.old) and copy the above files into both following locations?

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\

Then when install any new hotfixes (such as 2153) do make sure I review these three folders again with the newest of all files?

Thank you.

|||

hello,

here is what i would try:

- save out old files that you will replace (possibly rename just as you suggested), so that you can get back to original state if needed.

- copy both dlls from C:\Program Files\Common Files\System\Ole DB\ to the other folders (PrivateAssemblies, IDE)

start new BIDS and see if this helped solve the issue with the tab.

as of now, if you see an issue like this, it would usually mean files got mismatched and to fix this you'd need to make sure they are all consistent again. i guess, you could also proactivelly monitor the versions and update if needed. just be careful, and make sure you can get to the previous good state if something.

hope this helps,

|||

Hello,

Not resolved - Crashes Now.

1.) I have mad the recommended changes, reviewed and confirmed the file changes I made;

In all of these locations;

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\

C:\Program Files\Common Files\System\Ole DB\

I have these files;

Filename: msmgdsrv.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM

Filename: msmdlocal.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM

2.) I created a new project, and deployed it. Then to test it I went to the calculations page.

Now what I encounter are crashes! I receive an error that says;

========================

Microsoft Visual Studio

========================

Microsoft Visual Studio has encountered a problem and needs to close.

--

If you had files open....

[x] Restart Microsoft Visual Studio

Send an error report to Microsoft

A report has been created that includes more information about the cause of this error. Submitting this report helps Microsoft improve Visual Studio.

What information is contained in this report?

========================

[Debug] [Send Error Report]

========================

3.) I have tried many times and encoutered the crashes repeatedly. This includes restarting Windows.

What is my next step?

|||Hi,

I have the same problem on 1 machine. A fresh install of SQL 2005 SP1 (no hotfixes). and Office 2007 Beta 2 TR. I don't know, mayby this has something to do with Office?

Frederik|||

I have the same exact problem, and SQL 2005 SP1 & Office 2007 Beta TR. I didnt have this problem with office 2007 Beta.

Also I tried updating the dll's as advised in the two locations and visual studio crashes when I go to calculations tab, so I have rolled back to the old versions, but this comes with the error message on calculations tab and wont let me create any new calcs on a exisiting or any new cubes. It loads the existing calcs when I refresh the cube data, but just wont let me see it or edit it in design.

Any advise on how to fix this might help ?

|||Yes, my system too has has Office 2007 Beta 2 TR installed. Is there a pattern here? |||Seems like it because it worked perfectly fine before I refreshed it with Office 2007 TR, that must have upgraded the dll's on the oledb folder to the 3009 release making it out of sync with the dll's on the tools / SQL Server.|||I wonder if it will help, if Office 2007 Beta TR is uninstalled and Office 2007 beta is installed again.....(No TR) since it was working before?

BIDS - Error on design surface of Calculation tab in Cube

Has anyone seen this?

Within 'Business Intelligence Development Studio' (BIDS) with a cube opened and the calculations tab selected, the design surface displays a message that reads:

Unexpected error occurred: 'Error in the application.'

This occurs in any project I open and it still occurs when I restart BIDS or the computer itself.

Any ideas? Can anyone suggest a remedy?

hello,

this might be caused by version mismatch between some binaries. i'd suggest checking the versions of msmdlocal.dll and msmgdsrv.dll and making sure that the ones installed into %ProgramFiles%\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\ are the same as those in %ProgramFiles%\Common Files\System\Ole DB\ (if they are not then try updating the ones in the PrivateAssemblies with the ones from ole db; you might want to save the original ones as to be able to get back to original state just in case...)

hope this helps,

|||

I had already seen a similar post noting this as the possible cause so I checked the file versions in the appropriate folders an found no missmatch.

From there I went on to install the latest hotfix (2153) to see if that would clear up the problem. It did not.

After consulting with a friend I decided do a complete reinstall of SQL Server 2005 and related tools and such.

After the complete reinstall (and before a SP1 update) the problem still existed. I still recieve the error on the design surface of the Calculation tab for any cube I open.

I am currently trying to install SP1 and encounterring problems.

With my first attempt the 'Installation Progress' window for Service Pack 1 Setup showed product 'Analysis Services' status as "Failed". Here are the contents of the log file after it completed.

09/27/2006 09:26:44.282 ================================================================================
09/27/2006 09:26:44.314 Hotfix package launched
09/27/2006 09:31:58.503 Attempting to install instance: SQL Server Native Client
09/27/2006 09:31:58.534 Attempting to install target: L-0960
09/27/2006 09:31:58.581 Attempting to install file: sqlncli.msi
09/27/2006 09:31:58.675 Attempting to install file: \\L-0960\c$\06f6082a049155a5f4e3ece3b75f69\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 09:31:58.722 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
09/27/2006 09:31:58.737 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 09:31:58.753 Failed to read registry key: Debug
09/27/2006 09:32:01.329 MSP returned 0: The action completed successfully.
09/27/2006 09:32:01.501 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 09:32:01.689 Failed to read registry key: Debug
09/27/2006 09:32:01.704 Successfully installed file: \\L-0960\c$\06f6082a049155a5f4e3ece3b75f69\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 09:32:01.720 Successfully installed target: L-0960
09/27/2006 09:32:01.735 Successfully installed instance: SQL Server Native Client
09/27/2006 09:32:01.751
09/27/2006 09:32:01.751 Product Status Summary:
09/27/2006 09:32:01.767 Product: SQL Server Native Client
09/27/2006 09:32:01.782 SQL Server Native Client (RTM ) - Success
09/27/2006 09:32:01.782
09/27/2006 09:32:01.798 Product: Setup Support Files
09/27/2006 09:32:01.814 Setup Support Files (RTM ) - Not Applied
09/27/2006 09:32:01.829
09/27/2006 09:32:01.829 Product: Database Services
09/27/2006 09:32:01.845 Database Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:01.892 Analysis Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:01.923 Reporting Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:01.970
09/27/2006 09:32:01.985 Product: Notification Services
09/27/2006 09:32:02.017 Notification Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:02.048
09/27/2006 09:32:02.110 Product: Integration Services
09/27/2006 09:32:02.141 Integration Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:02.173
09/27/2006 09:32:02.204 Product: Client Components
09/27/2006 09:32:02.251 Client Components (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:02.282
09/27/2006 09:32:02.313 Product: MSXML 6.0 Parser
09/27/2006 09:32:02.360 MSXML 6.0 Parser (RTM ) - Not Applied
09/27/2006 09:32:02.391
09/27/2006 09:32:02.547 Product: SQLXML4
09/27/2006 09:32:02.641 SQLXML4 (RTM ) - Not Applied
09/27/2006 09:32:02.704
09/27/2006 09:32:02.735 Product: Backward Compatibility
09/27/2006 09:32:02.782 Backward Compatibility (RTM ) - Not Applied
09/27/2006 09:32:02.813
09/27/2006 09:32:02.844 Product: Microsoft SQL Server VSS Writer
09/27/2006 09:32:02.875 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
09/27/2006 09:32:02.907

After a restart I tried the Service Pack 1 installation again.

On this second attempt the 'Installation Progress' window for Service Pack 1 Setup showed product 'Analysis Services' status as "Warning".

Here are the contents of the log file after it completed.

09/27/2006 10:55:37.182 ================================================================================
09/27/2006 10:55:37.260 Hotfix package launched
09/27/2006 11:01:04.649 Attempting to install instance: SQL Server Native Client
09/27/2006 11:01:04.696 Attempting to install target: L-0960
09/27/2006 11:01:04.727 Attempting to install file: sqlncli.msi
09/27/2006 11:01:04.805 Attempting to install file: \\L-0960\c$\c13f3012d4415b5c63bc\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 11:01:04.868 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
09/27/2006 11:01:04.868 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 11:01:04.884 Failed to read registry key: Debug
09/27/2006 11:01:10.185 MSP returned 0: The action completed successfully.
09/27/2006 11:01:10.498 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 11:01:10.545 Failed to read registry key: Debug
09/27/2006 11:01:10.576 Successfully installed file: \\L-0960\c$\c13f3012d4415b5c63bc\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 11:01:10.608 Successfully installed target: L-0960
09/27/2006 11:01:10.608 Successfully installed instance: SQL Server Native Client
09/27/2006 11:01:10.623
09/27/2006 11:01:10.639 Product Status Summary:
09/27/2006 11:01:10.639 Product: SQL Server Native Client
09/27/2006 11:01:10.655 SQL Server Native Client (RTM ) - Success
09/27/2006 11:01:10.670
09/27/2006 11:01:10.686 Product: Setup Support Files
09/27/2006 11:01:10.686 Setup Support Files (RTM ) - Not Applied
09/27/2006 11:01:10.701
09/27/2006 11:01:10.717 Product: Database Services
09/27/2006 11:01:10.717 Database Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.733 Analysis Services (RTM 1399 ENU) - Not Applied
09/27/2006 11:01:10.748 Reporting Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.764
09/27/2006 11:01:10.764 Product: Notification Services
09/27/2006 11:01:10.780 Notification Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.795
09/27/2006 11:01:10.795 Product: Integration Services
09/27/2006 11:01:10.811 Integration Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.827
09/27/2006 11:01:10.842 Product: Client Components
09/27/2006 11:01:10.842 Client Components (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.858
09/27/2006 11:01:10.873 Product: MSXML 6.0 Parser
09/27/2006 11:01:10.873 MSXML 6.0 Parser (RTM ) - Not Applied
09/27/2006 11:01:10.889
09/27/2006 11:01:10.905 Product: SQLXML4
09/27/2006 11:01:10.920 SQLXML4 (RTM ) - Not Applied
09/27/2006 11:01:10.920
09/27/2006 11:01:10.936 Product: Backward Compatibility
09/27/2006 11:01:10.952 Backward Compatibility (RTM ) - Not Applied
09/27/2006 11:01:10.952
09/27/2006 11:01:10.967 Product: Microsoft SQL Server VSS Writer
09/27/2006 11:01:10.983 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
09/27/2006 11:01:10.983

What doe all this mean? How do I fix the Business Intelligence Development Studio (BIDS) in its working with Analysis Services cubes?

|||

By the way the files noted earlier "msmgdsrv.dll" and "msmdlocal.dll" are still consistant in date betwee tne two folders.

Within BIDS I can make a connection to the database server. I know this because on the Browser tab of the cube I can drag different measures and dimensions onto the design surface and get results returned but I cannot view the cube's calculations. The design surface tells me;

"Unexpected error occurred: 'Error in the application.'"

At the bottom of the design window starts out with a message that says:

Unable to query the 'Adventure Works DW' cube: 'A connection cannot be made. Ensure that he server is running.'. The cube must be queried for you to browse data or meta data. Click here to retry the connection.

When I click the message at the bottom of the screen goes away, but the message on the design surface remains.

It appears that the needed connection for the calucations tabe is made because the Metadata tab, is populated with the proper measures and dimensions of the cube.

What is the cause of all this?

|||

hello,

the symptoms of the error definitely suggest files got mismatched... so, if the 2 files are consistent between PrivateAssemblies and the Ole Db folder, then perhaps the 2 files are inconsistent between themselves in both places. what are the file versions/modification dates on msmgdsrv.dll and msmdlocal.dll (in both places) ?

i'm not sure why setup fails for you...

thanks,

|||

> what are the file versions/modification dates on msmgdsrv.dll and msmdlocal.dll (in both places) ?

Here are the locations, filenames, versions, and date\time

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\

Filename: msmgdsrv.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM

Filename: msmdlocal.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\

Filename: msmgdsrv.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM

Filename: msmdlocal.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM

Before the complete Re-load of SQLS2k5 I had updated to the most recent hotfix (9.0.2153.0). At that time these files were also consistent in version and date and the same problem I now experience was there.

|||

hello,

actually, as i mentioned before, it's important to check the versions compared to: %ProgramFiles%\Common Files\System\Ole DB\ (and not %ProgramFiles%\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\). i.e. can you please check the files in that (Ole Db) directory?

thanks,

|||

Here it is:

C:\Program Files\Common Files\System\Ole DB\

Filename: msmgdsrv.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM

Filename: msmdlocal.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM

So what action do I take? Do I rename the existing (older) files (to something like msmgdsrv.dll.old and msmdlocal.dll.old) and copy the above files into both following locations?

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\

Then when install any new hotfixes (such as 2153) do make sure I review these three folders again with the newest of all files?

Thank you.

|||

hello,

here is what i would try:

- save out old files that you will replace (possibly rename just as you suggested), so that you can get back to original state if needed.

- copy both dlls from C:\Program Files\Common Files\System\Ole DB\ to the other folders (PrivateAssemblies, IDE)

start new BIDS and see if this helped solve the issue with the tab.

as of now, if you see an issue like this, it would usually mean files got mismatched and to fix this you'd need to make sure they are all consistent again. i guess, you could also proactivelly monitor the versions and update if needed. just be careful, and make sure you can get to the previous good state if something.

hope this helps,

|||

Hello,

Not resolved - Crashes Now.

1.) I have mad the recommended changes, reviewed and confirmed the file changes I made;

In all of these locations;

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\

C:\Program Files\Common Files\System\Ole DB\

I have these files;

Filename: msmgdsrv.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM

Filename: msmdlocal.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM

2.) I created a new project, and deployed it. Then to test it I went to the calculations page.

Now what I encounter are crashes! I receive an error that says;

========================

Microsoft Visual Studio

========================

Microsoft Visual Studio has encountered a problem and needs to close.

--

If you had files open....

[x] Restart Microsoft Visual Studio

Send an error report to Microsoft

A report has been created that includes more information about the cause of this error. Submitting this report helps Microsoft improve Visual Studio.

What information is contained in this report?

========================

[Debug] [Send Error Report]

========================

3.) I have tried many times and encoutered the crashes repeatedly. This includes restarting Windows.

What is my next step?

|||Hi,

I have the same problem on 1 machine. A fresh install of SQL 2005 SP1 (no hotfixes). and Office 2007 Beta 2 TR. I don't know, mayby this has something to do with Office?

Frederik|||

I have the same exact problem, and SQL 2005 SP1 & Office 2007 Beta TR. I didnt have this problem with office 2007 Beta.

Also I tried updating the dll's as advised in the two locations and visual studio crashes when I go to calculations tab, so I have rolled back to the old versions, but this comes with the error message on calculations tab and wont let me create any new calcs on a exisiting or any new cubes. It loads the existing calcs when I refresh the cube data, but just wont let me see it or edit it in design.

Any advise on how to fix this might help ?

|||Yes, my system too has has Office 2007 Beta 2 TR installed. Is there a pattern here? |||Seems like it because it worked perfectly fine before I refreshed it with Office 2007 TR, that must have upgraded the dll's on the oledb folder to the 3009 release making it out of sync with the dll's on the tools / SQL Server.|||I wonder if it will help, if Office 2007 Beta TR is uninstalled and Office 2007 beta is installed again.....(No TR) since it was working before?

BIDS - Error on design surface of Calculation tab in Cube

Has anyone seen this?

Within 'Business Intelligence Development Studio' (BIDS) with a cube opened and the calculations tab selected, the design surface displays a message that reads:

Unexpected error occurred: 'Error in the application.'

This occurs in any project I open and it still occurs when I restart BIDS or the computer itself.

Any ideas? Can anyone suggest a remedy?

hello,

this might be caused by version mismatch between some binaries. i'd suggest checking the versions of msmdlocal.dll and msmgdsrv.dll and making sure that the ones installed into %ProgramFiles%\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\ are the same as those in %ProgramFiles%\Common Files\System\Ole DB\ (if they are not then try updating the ones in the PrivateAssemblies with the ones from ole db; you might want to save the original ones as to be able to get back to original state just in case...)

hope this helps,

|||

I had already seen a similar post noting this as the possible cause so I checked the file versions in the appropriate folders an found no missmatch.

From there I went on to install the latest hotfix (2153) to see if that would clear up the problem. It did not.

After consulting with a friend I decided do a complete reinstall of SQL Server 2005 and related tools and such.

After the complete reinstall (and before a SP1 update) the problem still existed. I still recieve the error on the design surface of the Calculation tab for any cube I open.

I am currently trying to install SP1 and encounterring problems.

With my first attempt the 'Installation Progress' window for Service Pack 1 Setup showed product 'Analysis Services' status as "Failed". Here are the contents of the log file after it completed.

09/27/2006 09:26:44.282 ================================================================================
09/27/2006 09:26:44.314 Hotfix package launched
09/27/2006 09:31:58.503 Attempting to install instance: SQL Server Native Client
09/27/2006 09:31:58.534 Attempting to install target: L-0960
09/27/2006 09:31:58.581 Attempting to install file: sqlncli.msi
09/27/2006 09:31:58.675 Attempting to install file: \\L-0960\c$\06f6082a049155a5f4e3ece3b75f69\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 09:31:58.722 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
09/27/2006 09:31:58.737 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 09:31:58.753 Failed to read registry key: Debug
09/27/2006 09:32:01.329 MSP returned 0: The action completed successfully.
09/27/2006 09:32:01.501 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 09:32:01.689 Failed to read registry key: Debug
09/27/2006 09:32:01.704 Successfully installed file: \\L-0960\c$\06f6082a049155a5f4e3ece3b75f69\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 09:32:01.720 Successfully installed target: L-0960
09/27/2006 09:32:01.735 Successfully installed instance: SQL Server Native Client
09/27/2006 09:32:01.751
09/27/2006 09:32:01.751 Product Status Summary:
09/27/2006 09:32:01.767 Product: SQL Server Native Client
09/27/2006 09:32:01.782 SQL Server Native Client (RTM ) - Success
09/27/2006 09:32:01.782
09/27/2006 09:32:01.798 Product: Setup Support Files
09/27/2006 09:32:01.814 Setup Support Files (RTM ) - Not Applied
09/27/2006 09:32:01.829
09/27/2006 09:32:01.829 Product: Database Services
09/27/2006 09:32:01.845 Database Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:01.892 Analysis Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:01.923 Reporting Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:01.970
09/27/2006 09:32:01.985 Product: Notification Services
09/27/2006 09:32:02.017 Notification Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:02.048
09/27/2006 09:32:02.110 Product: Integration Services
09/27/2006 09:32:02.141 Integration Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:02.173
09/27/2006 09:32:02.204 Product: Client Components
09/27/2006 09:32:02.251 Client Components (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:02.282
09/27/2006 09:32:02.313 Product: MSXML 6.0 Parser
09/27/2006 09:32:02.360 MSXML 6.0 Parser (RTM ) - Not Applied
09/27/2006 09:32:02.391
09/27/2006 09:32:02.547 Product: SQLXML4
09/27/2006 09:32:02.641 SQLXML4 (RTM ) - Not Applied
09/27/2006 09:32:02.704
09/27/2006 09:32:02.735 Product: Backward Compatibility
09/27/2006 09:32:02.782 Backward Compatibility (RTM ) - Not Applied
09/27/2006 09:32:02.813
09/27/2006 09:32:02.844 Product: Microsoft SQL Server VSS Writer
09/27/2006 09:32:02.875 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
09/27/2006 09:32:02.907

After a restart I tried the Service Pack 1 installation again.

On this second attempt the 'Installation Progress' window for Service Pack 1 Setup showed product 'Analysis Services' status as "Warning".

Here are the contents of the log file after it completed.

09/27/2006 10:55:37.182 ================================================================================
09/27/2006 10:55:37.260 Hotfix package launched
09/27/2006 11:01:04.649 Attempting to install instance: SQL Server Native Client
09/27/2006 11:01:04.696 Attempting to install target: L-0960
09/27/2006 11:01:04.727 Attempting to install file: sqlncli.msi
09/27/2006 11:01:04.805 Attempting to install file: \\L-0960\c$\c13f3012d4415b5c63bc\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 11:01:04.868 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
09/27/2006 11:01:04.868 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 11:01:04.884 Failed to read registry key: Debug
09/27/2006 11:01:10.185 MSP returned 0: The action completed successfully.
09/27/2006 11:01:10.498 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 11:01:10.545 Failed to read registry key: Debug
09/27/2006 11:01:10.576 Successfully installed file: \\L-0960\c$\c13f3012d4415b5c63bc\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 11:01:10.608 Successfully installed target: L-0960
09/27/2006 11:01:10.608 Successfully installed instance: SQL Server Native Client
09/27/2006 11:01:10.623
09/27/2006 11:01:10.639 Product Status Summary:
09/27/2006 11:01:10.639 Product: SQL Server Native Client
09/27/2006 11:01:10.655 SQL Server Native Client (RTM ) - Success
09/27/2006 11:01:10.670
09/27/2006 11:01:10.686 Product: Setup Support Files
09/27/2006 11:01:10.686 Setup Support Files (RTM ) - Not Applied
09/27/2006 11:01:10.701
09/27/2006 11:01:10.717 Product: Database Services
09/27/2006 11:01:10.717 Database Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.733 Analysis Services (RTM 1399 ENU) - Not Applied
09/27/2006 11:01:10.748 Reporting Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.764
09/27/2006 11:01:10.764 Product: Notification Services
09/27/2006 11:01:10.780 Notification Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.795
09/27/2006 11:01:10.795 Product: Integration Services
09/27/2006 11:01:10.811 Integration Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.827
09/27/2006 11:01:10.842 Product: Client Components
09/27/2006 11:01:10.842 Client Components (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.858
09/27/2006 11:01:10.873 Product: MSXML 6.0 Parser
09/27/2006 11:01:10.873 MSXML 6.0 Parser (RTM ) - Not Applied
09/27/2006 11:01:10.889
09/27/2006 11:01:10.905 Product: SQLXML4
09/27/2006 11:01:10.920 SQLXML4 (RTM ) - Not Applied
09/27/2006 11:01:10.920
09/27/2006 11:01:10.936 Product: Backward Compatibility
09/27/2006 11:01:10.952 Backward Compatibility (RTM ) - Not Applied
09/27/2006 11:01:10.952
09/27/2006 11:01:10.967 Product: Microsoft SQL Server VSS Writer
09/27/2006 11:01:10.983 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
09/27/2006 11:01:10.983

What doe all this mean? How do I fix the Business Intelligence Development Studio (BIDS) in its working with Analysis Services cubes?

|||

By the way the files noted earlier "msmgdsrv.dll" and "msmdlocal.dll" are still consistant in date betwee tne two folders.

Within BIDS I can make a connection to the database server. I know this because on the Browser tab of the cube I can drag different measures and dimensions onto the design surface and get results returned but I cannot view the cube's calculations. The design surface tells me;

"Unexpected error occurred: 'Error in the application.'"

At the bottom of the design window starts out with a message that says:

Unable to query the 'Adventure Works DW' cube: 'A connection cannot be made. Ensure that he server is running.'. The cube must be queried for you to browse data or meta data. Click here to retry the connection.

When I click the message at the bottom of the screen goes away, but the message on the design surface remains.

It appears that the needed connection for the calucations tabe is made because the Metadata tab, is populated with the proper measures and dimensions of the cube.

What is the cause of all this?

|||

hello,

the symptoms of the error definitely suggest files got mismatched... so, if the 2 files are consistent between PrivateAssemblies and the Ole Db folder, then perhaps the 2 files are inconsistent between themselves in both places. what are the file versions/modification dates on msmgdsrv.dll and msmdlocal.dll (in both places) ?

i'm not sure why setup fails for you...

thanks,

|||

> what are the file versions/modification dates on msmgdsrv.dll and msmdlocal.dll (in both places) ?

Here are the locations, filenames, versions, and date\time

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\

Filename: msmgdsrv.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM

Filename: msmdlocal.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\

Filename: msmgdsrv.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM

Filename: msmdlocal.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM

Before the complete Re-load of SQLS2k5 I had updated to the most recent hotfix (9.0.2153.0). At that time these files were also consistent in version and date and the same problem I now experience was there.

|||

hello,

actually, as i mentioned before, it's important to check the versions compared to: %ProgramFiles%\Common Files\System\Ole DB\ (and not %ProgramFiles%\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\). i.e. can you please check the files in that (Ole Db) directory?

thanks,

|||

Here it is:

C:\Program Files\Common Files\System\Ole DB\

Filename: msmgdsrv.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM

Filename: msmdlocal.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM

So what action do I take? Do I rename the existing (older) files (to something like msmgdsrv.dll.old and msmdlocal.dll.old) and copy the above files into both following locations?

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\

Then when install any new hotfixes (such as 2153) do make sure I review these three folders again with the newest of all files?

Thank you.

|||

hello,

here is what i would try:

- save out old files that you will replace (possibly rename just as you suggested), so that you can get back to original state if needed.

- copy both dlls from C:\Program Files\Common Files\System\Ole DB\ to the other folders (PrivateAssemblies, IDE)

start new BIDS and see if this helped solve the issue with the tab.

as of now, if you see an issue like this, it would usually mean files got mismatched and to fix this you'd need to make sure they are all consistent again. i guess, you could also proactivelly monitor the versions and update if needed. just be careful, and make sure you can get to the previous good state if something.

hope this helps,

|||

Hello,

Not resolved - Crashes Now.

1.) I have mad the recommended changes, reviewed and confirmed the file changes I made;

In all of these locations;

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\

C:\Program Files\Common Files\System\Ole DB\

I have these files;

Filename: msmgdsrv.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM

Filename: msmdlocal.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM

2.) I created a new project, and deployed it. Then to test it I went to the calculations page.

Now what I encounter are crashes! I receive an error that says;

========================

Microsoft Visual Studio

========================

Microsoft Visual Studio has encountered a problem and needs to close.

--

If you had files open....

[x] Restart Microsoft Visual Studio

Send an error report to Microsoft

A report has been created that includes more information about the cause of this error. Submitting this report helps Microsoft improve Visual Studio.

What information is contained in this report?

========================

[Debug] [Send Error Report]

========================

3.) I have tried many times and encoutered the crashes repeatedly. This includes restarting Windows.

What is my next step?

|||Hi,

I have the same problem on 1 machine. A fresh install of SQL 2005 SP1 (no hotfixes). and Office 2007 Beta 2 TR. I don't know, mayby this has something to do with Office?

Frederik|||

I have the same exact problem, and SQL 2005 SP1 & Office 2007 Beta TR. I didnt have this problem with office 2007 Beta.

Also I tried updating the dll's as advised in the two locations and visual studio crashes when I go to calculations tab, so I have rolled back to the old versions, but this comes with the error message on calculations tab and wont let me create any new calcs on a exisiting or any new cubes. It loads the existing calcs when I refresh the cube data, but just wont let me see it or edit it in design.

Any advise on how to fix this might help ?

|||Yes, my system too has has Office 2007 Beta 2 TR installed. Is there a pattern here? |||Seems like it because it worked perfectly fine before I refreshed it with Office 2007 TR, that must have upgraded the dll's on the oledb folder to the 3009 release making it out of sync with the dll's on the tools / SQL Server.|||I wonder if it will help, if Office 2007 Beta TR is uninstalled and Office 2007 beta is installed again.....(No TR) since it was working before?