Showing posts with label machine. Show all posts
Showing posts with label machine. Show all posts

Tuesday, March 20, 2012

"The underlying connection was closed: An unexpected error occurred on a receive." End

what can cause the above error when connecting to an endpoint via a c# app? the app, and sql are both on my machine ( im just doing this for test purposes and to learn something new.)

i added this code on advice from a web site to the Reference.cs file:

{
HttpWebRequest webRequest = (HttpWebRequest) base.GetWebRequest(uri);

webRequest.KeepAlive = false;
webRequest.ProtocolVersion=HttpVersion.Version10;
return webRequest;
}

Now i get this error.

"The request failed with HTTP status 401: Unauthorized."

this is strange as i have granted the user who the application is running under control access to the endpoint, and even to the function behind the endpoint.

Here is the code behind the button for calling the web service:

private void button1_Click(object sender, EventArgs e)

{

try

{

v_fintag.my_Endpoint wsObject = new v_fintag.my_Endpoint();

wsObject.Credentials = System.Net.CredentialCache.DefaultCredentials;

System.Data.SqlTypes.SqlInt32 sqlint;

sqlint = 25;

System.Data.SqlTypes.SqlString sqlStr;

sqlStr = wsObject.GetFunctionData(sqlint);

}

catch (Exception ET)

{

label2.Text = ET.Message + " : " + ET.Data;

}

}

Also, here is the endpoint, in case its useful or provides information:

create endpoint my_Endpoint

state = started

as http(path='/sql',

authentication=(INTEGRATED),

PORTS=(CLEAR),

SITE='*')

For SOAP

(

webmethod 'GetSprocData'(name='adventureworksdw.dbo.testEndPointSproc'),

webmethod 'GetFunctionData'(name='adventureworksdw.dbo.endpointFunctionTest'),

wsdl=default,

schema=standard,

database ='adventureworksdw',

namespace = 'myNamespace'

)

grant execute on dbo.endpointfunctiontest to [user1]

use master

GRANT CONNECT ON ENDPOINT:: my_Endpoint TO [user1]

Friday, March 16, 2012

"Report is being generated" but never does...

I have created a report and deployed it successfully to a seperate machine with SSRS on. Both my dev machine and the SSRS machine are in the same workgroup. I can then Browse to the Report Manager though IE and click & run the report (The connection is using integrated security). The report requires a single parameter to be entered which once done works successfully. The report has a single table, an inbedded image and a few static fields in the report header.

If I however add a report viewer control to an aspx test form all is not well. As soon as the page opens I am prompted to enter the parameter which is good news as it shows there has been some communication with the SSRS metabase. I then click the view report button. Using Profiler I have proved that the report Stored Proc. is running with the correct parameter value. The report viewer however seems to hang and only displays "Report is being generated" without displaying the results. It does this even with a timeout set of 1000ms.

I don't think this is a security issue as both the Report Manager works and the test form prompts me for the parameter and effectively runs the report SP. I can only assume it is a problem with returning the report to the browser.

Does anyone have any insight?

Regards

Anthony Kay

Hmmh, 1000ms ist just a second, thats not much. Try to have a look in the log information, it should present jyou more details about opening the report, querying the data, rendering the report. There you might see where the execution stops.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

Seem to have the same problem.

Anthony, did you find a solution for this already?

thanks in advance

Wouter van Dis

|||I found later that it was specific to my development machine as my colleagues still worked. I have found no explaination for this as yet.

"Report is being generated" but never does...

I have created a report and deployed it successfully to a seperate machine with SSRS on. Both my dev machine and the SSRS machine are in the same workgroup. I can then Browse to the Report Manager though IE and click & run the report (The connection is using integrated security). The report requires a single parameter to be entered which once done works successfully. The report has a single table, an inbedded image and a few static fields in the report header.

If I however add a report viewer control to an aspx test form all is not well. As soon as the page opens I am prompted to enter the parameter which is good news as it shows there has been some communication with the SSRS metabase. I then click the view report button. Using Profiler I have proved that the report Stored Proc. is running with the correct parameter value. The report viewer however seems to hang and only displays "Report is being generated" without displaying the results. It does this even with a timeout set of 1000ms.

I don't think this is a security issue as both the Report Manager works and the test form prompts me for the parameter and effectively runs the report SP. I can only assume it is a problem with returning the report to the browser.

Does anyone have any insight?

Regards

Anthony Kay

Hmmh, 1000ms ist just a second, thats not much. Try to have a look in the log information, it should present jyou more details about opening the report, querying the data, rendering the report. There you might see where the execution stops.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

Seem to have the same problem.

Anthony, did you find a solution for this already?

thanks in advance

Wouter van Dis

|||I found later that it was specific to my development machine as my colleagues still worked. I have found no explaination for this as yet.

Thursday, March 8, 2012

"Named Pipes Provider: Could not open a connection to SQL Server [53]", but only on th

My connection string (to a remote instance of SQL Server Exress 2005) is exactly the same when the web files are located on my local machine or my remote machine, and while it works fine when I use the local web files, I get the following error when I use the remote files:

"Named Pipes Provider: Could not open a connection to SQL Server [53]"

As you can see, since it works from the local version, I've setup SQL to accept remote connections via TCP/IP and Named Pipes. I'm using IIS7 on the local, and IIS6 on the remote, in case that makes a difference. I have other sites setup the same way, which work fine.

Any thoughts?

Open the configuration manager and set SQL Server to allow remote connections.
This is off by default on SQL Server Express Edition.

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

|||Thank you for responding, although as you can see in my question, I point out that this is clearly set up, as I am connecting successfully from my local machine.

However, I should note that I have resolved the problem by replicating the database.
|||

Oops, I didn't read that little sentence, sorry :-)

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

Sunday, February 19, 2012

<NEWBIE>Move database from case sensitive to case insensitive servers

I know there are several ways to copy information from one machine to anothe
r, and from my research in the archives every approach has its adherents. I'
d just like a better idea of which is the best method for my particular case
.
There is a database residing on a remote server that has been set up as case
sensitive. I need to move the database to my own departmental server, which
is case insensitive (and the app vendor prefers this). Which is the best me
thod to move the system, wh
ere best means first, no errors and second, little effort on my part.
Right now I'm leaning toward detaching the database on the other machine and
copying its mdf and ldf files to the local machine and reattaching it. Will
the case sensitivity cause problems?
Thanks,
J"John" <anonymous@.discussions.microsoft.com> wrote in message
news:1C256B86-16BD-4933-B081-264AC510F814@.microsoft.com...
> I know there are several ways to copy information from one machine to
another, and from my research in the archives every approach has its
adherents. I'd just like a better idea of which is the best method for my
particular case.
> There is a database residing on a remote server that has been set up as
case sensitive. I need to move the database to my own departmental server,
which is case insensitive (and the app vendor prefers this). Which is the
best method to move the system, where best means first, no errors and
second, little effort on my part.
> Right now I'm leaning toward detaching the database on the other machine
and copying its mdf and ldf files to the local machine and reattaching it.
Will the case sensitivity cause problems?
>
Are you running SQL Server 2000? Then that should work for you. Another
option, create the database on the target with the collation you need, then
run a RESTORE. For more information, see BOL "SQL Server Collation
Fundamentals".
Steve|||Do you want the database to be case sensitive or case insensitive on the new
server?
Watch out having different collations for you system databases vs. your
application database(s). If the app wasn't tested for this, you might get
error messages from the queries it submits (collation conflict messages).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:1C256B86-16BD-4933-B081-264AC510F814@.microsoft.com...
> I know there are several ways to copy information from one machine to
another, and from my research in the archives every approach has its
adherents. I'd just like a better idea of which is the best method for my
particular case.
> There is a database residing on a remote server that has been set up as
case sensitive. I need to move the database to my own departmental server,
which is case insensitive (and the app vendor prefers this). Which is the
best method to move the system, where best means first, no errors and
second, little effort on my part.
> Right now I'm leaning toward detaching the database on the other machine
and copying its mdf and ldf files to the local machine and reattaching it.
Will the case sensitivity cause problems?
> Thanks,
> J

<NEWBIE>Move database from case sensitive to case insensitive servers

I know there are several ways to copy information from one machine to another, and from my research in the archives every approach has its adherents. I'd just like a better idea of which is the best method for my particular case.
There is a database residing on a remote server that has been set up as case sensitive. I need to move the database to my own departmental server, which is case insensitive (and the app vendor prefers this). Which is the best method to move the system, where best means first, no errors and second, little effort on my part.
Right now I'm leaning toward detaching the database on the other machine and copying its mdf and ldf files to the local machine and reattaching it. Will the case sensitivity cause problems
Thanks
J"John" <anonymous@.discussions.microsoft.com> wrote in message
news:1C256B86-16BD-4933-B081-264AC510F814@.microsoft.com...
> I know there are several ways to copy information from one machine to
another, and from my research in the archives every approach has its
adherents. I'd just like a better idea of which is the best method for my
particular case.
> There is a database residing on a remote server that has been set up as
case sensitive. I need to move the database to my own departmental server,
which is case insensitive (and the app vendor prefers this). Which is the
best method to move the system, where best means first, no errors and
second, little effort on my part.
> Right now I'm leaning toward detaching the database on the other machine
and copying its mdf and ldf files to the local machine and reattaching it.
Will the case sensitivity cause problems?
>
Are you running SQL Server 2000? Then that should work for you. Another
option, create the database on the target with the collation you need, then
run a RESTORE. For more information, see BOL "SQL Server Collation
Fundamentals".
Steve|||Do you want the database to be case sensitive or case insensitive on the new
server?
Watch out having different collations for you system databases vs. your
application database(s). If the app wasn't tested for this, you might get
error messages from the queries it submits (collation conflict messages).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"John" <anonymous@.discussions.microsoft.com> wrote in message
news:1C256B86-16BD-4933-B081-264AC510F814@.microsoft.com...
> I know there are several ways to copy information from one machine to
another, and from my research in the archives every approach has its
adherents. I'd just like a better idea of which is the best method for my
particular case.
> There is a database residing on a remote server that has been set up as
case sensitive. I need to move the database to my own departmental server,
which is case insensitive (and the app vendor prefers this). Which is the
best method to move the system, where best means first, no errors and
second, little effort on my part.
> Right now I'm leaning toward detaching the database on the other machine
and copying its mdf and ldf files to the local machine and reattaching it.
Will the case sensitivity cause problems?
> Thanks,
> J

Thursday, February 16, 2012

>2G ram & Standard Edition supported?

We have SQLServer standard edition running on a machine
with 2.2G of RAM. The sales faq appears to indicate that
SQLServer is not supported on a machine with more than 2G
of RAM. Is this the case?
Thanks,
Simon
--
http://www.microsoft.com/sql/howtobuy/faq.asp
Q. What is the maximum amount of RAM supported by SQL
Server 2000?
A. SQL Server 2000 Standard Edition supports up to 2
gigabytes (GB) of RAM. SQL Server 2000 Enterprise Edition
supports up to 64 GB of RAM.Simon
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750
"Simon Massey" <anonymous@.discussions.microsoft.com> wrote in message
news:3e9101c3e40f$4aa2c710$a301280a@.phx.gbl...
> We have SQLServer standard edition running on a machine
> with 2.2G of RAM. The sales faq appears to indicate that
> SQLServer is not supported on a machine with more than 2G
> of RAM. Is this the case?
> Thanks,
> Simon
> --
> http://www.microsoft.com/sql/howtobuy/faq.asp
> Q. What is the maximum amount of RAM supported by SQL
> Server 2000?
> A. SQL Server 2000 Standard Edition supports up to 2
> gigabytes (GB) of RAM. SQL Server 2000 Enterprise Edition
> supports up to 64 GB of RAM.
>|||SQL Server Standard Edition is "supported" on machines with > 2GB, meaning
that MS will still give you technical support if you run it this way.
However Standard Edition only "supports" 2GB of RAM, meaning it will not use
more even if the machine has more installed.
To get SQL Server to use more than 2GB RAM you need the Enterprise Edition.
Note that the OS and other programs on that server could utilize the RAM,
like Analysis Services, Reporting Services or Notification Services.
Mike Kruchten
"Simon Massey" <anonymous@.discussions.microsoft.com> wrote in message
news:3e9101c3e40f$4aa2c710$a301280a@.phx.gbl...
> We have SQLServer standard edition running on a machine
> with 2.2G of RAM. The sales faq appears to indicate that
> SQLServer is not supported on a machine with more than 2G
> of RAM. Is this the case?
> Thanks,
> Simon
> --
> http://www.microsoft.com/sql/howtobuy/faq.asp
> Q. What is the maximum amount of RAM supported by SQL
> Server 2000?
> A. SQL Server 2000 Standard Edition supports up to 2
> gigabytes (GB) of RAM. SQL Server 2000 Enterprise Edition
> supports up to 64 GB of RAM.
>

Monday, February 13, 2012

'OraOLEDB.Oracle.1' is not registered on local machine

Hi all of you,

Primary platform is Framework 2.0 running over XP.

I've got an issue with a SSIS package which uses Oracle Provider for OleDB:

Test connection failed because of an error in initializing provider 'OraOLEDB.Oracle.1' is not registered on local machine

Nevertheless, MS Ole DB Provider for Oracle works fine. Let me know where am I failing.

Thanks in advance,

Try reinstalling the Oracle client.|||

Thanks for your answer Phil.

I've got a question.. If I do such thing, my tnsnames.ora will be destroyed? 'suppose so

Anyway, I think that my problem is other one..

|||Copy your tnsnames.ora file to another name and then restore it when done. Which is something you should be doing anyway -- backing it up.

You can try just reinstalling the OLE provider: http://www.oracle.com/technology/software/tech/windows/ole_db/index.html|||

Hi Phil,

Thanks indeed. It works fine. I'm sorry for my scepticism.

|||

Hi Phil.

I am also having this problem, made sure that the ACL are read and execute for ASPNET, IUSR, IWAM users on the server. The app is .NET 2.0 by a vendor that is using the following connection string. names change to protect the innocent.

Provider=OraOLEDB.Oracle;Password=pass;User ID=user; Data Source=ds'/>

Unfortunately the vendor has no answers...

My question is that I have been told by my DBA that reinstalling doesn't always reinstall correctly as the registry entries still exists. Am I being told correctly? Also, If I reinstall, am I creating a new Oracle_Home that I would have set up in the OBDC administrator.

|||

n2magick wrote:

Hi Phil.

I am also having this problem, made sure that the ACL are read and execute for ASPNET, IUSR, IWAM users on the server. The app is .NET 2.0 by a vendor that is using the following connection string. names change to protect the innocent.

Provider=OraOLEDB.Oracle;Password=pass;User ID=user; Data Source=ds'/>

Unfortunately the vendor has no answers...

My question is that I have been told by my DBA that reinstalling doesn't always reinstall correctly as the registry entries still exists. Am I being told correctly? Also, If I reinstall, am I creating a new Oracle_Home that I would have set up in the OBDC administrator.

Right, but are you using SSIS? If not, I'm afraid I cannot help you... It seems that you have several layers that could be causing you issues.|||

Thanks Phil for answering my question. No I am not using SSIS. Just happen on the post doing a search trying to find the answer to my problem. Smile

Thanks again for your prompt answer.

LuAnn