Showing posts with label ive. Show all posts
Showing posts with label ive. Show all posts

Thursday, March 22, 2012

error: 26 - Error Locating Server/Instance Specified

Hi

I seem to have a quite common problem. I’ve search forums and blogs both on Microsoft and outside but even though I find many people that have similar problems. After migrating from XP to Vista I can’t seem to solve the problem. I can’t seem to get by Windows Form application based on framework 2.0 to connect to my locally stored SQL Server 2005 Express database. The application has not changed and the environment (apart from the operating system) hasn’t changed either. No matter what I try the problem persists.

The thing that confuses me the most is that I within Visual Studio 2005 can preview data in the data sources tab. In my understanding, both uses the same connection string but I find it possible that the user might differ but I don’t understand why is should.

From my point of view (and might of course be wrong) these things should not be the source of the problem:

· The firewall, since that has been turned off

· The connection string, since that actually work when performing a preview data

· The remote settings, since the server and the client is on the same machine

· The SQL Browser, since I tried connecting using a TCP/IP connection with the same results

Possible problems:

· SQL User access, if the user when performing preview is for some reason not the same as when the application runs

· A Vista problem of some sort

I’ve read basically everything I’ve been able to find on the issue but even though the symptoms fit the solutions don’t solve the problem. This problem has been haunting me for weeks now and I’m really out of ideas?

Here is a listing of things I’ve tried without success:

· The remote settings in the SQL Server Surface Area Configuration has been turned on even though I don’t understand to what end since the server and client in this case reside on the same physical machine. However this did allow me to try connections using TCP/IP. I did restart both the services and the computer to be sure.

· Connections using TCP/IP where the connection string supply contain tcp:<ip>,<port>

· Different exceptions in the firewall, both on port level (for UDP and TCP) and on application level (sqlserver.exe and sqlbrowser.exe). The dynamic port setting has was changed during this test to a static port setting.

· A number of variants of the connection strings (e.g. using ./sqlexpress instead of <machine_name>/sqlexpress)

· All the error logs (Event logs, SQL ERRORLOGS and firewall log while it was turned on) have been checked and the only reoccurring message is a warning message from the SQL Browser: The configuration of the AdminConnection\TCP protocol in the SQL instance SQLEXPRESS is not valid.

The server and the client reside on the same machine.

[1] These are the specific CLIENT side settings:
1. Connection string: Data Source=.\SQLEXPRESS;Initial Catalog=Products;Integrated Security=True
2. Full error message: An error has occurred while establishing a connection to the server.When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
I can ping the server
3. Client and server reside on the same machine
4. Yes I can ping the machine
5. Haven’t tried
6. SQL Server Management Studio Express works, using Visual Studio 2005 works but the applications built by VS2005 doesn’t work.
7. N/A (Client and server reside on the same machine)
8.
9. No alias used
10. No encryption used.

[2] These are the specific SERVER side settings:
1. SQL Server 2005 Express SP2
2. Se above
3. Protocols enabled Shared Memory, TCPIP and Named Pipes
4. Yes, there are not errors in the ERRORLOG
5. Yes the SQL Browser is enabled and active and must work at least in some aspects since the preview data works
6. Currently running as default: Network Service
7. The firewall is turned off entirely
8. The firewall is turned off entirely

[2a] Visual Studio 2005 Team Edition for Developers

[3]
1. Vista Business
2. No antivirus installed at this point.

Hope for some help.

Regards Malin

Hi again

I've started using connecting via TCP to my old SQL Server Express server residing on a XP machine and suprise, it works perfectly without any problems what so ever! Apart the operating system I really can't find any differences in the settnigs. So my guess is that the problem must be somewhere in between Vista and my SQL server.

So has anybody else had any experience with Vista and SQL Server Express? Any suggestions are welcome!

Regards Malin

Error: 208, Severity: 16, State: 1

Ive also got lots of these errors. Dont know if this helps.
"ChrisR" <noemail@.bla.com> wrote in message
news:eV%23sQagmFHA.3648@.TK2MSFTNGP10.phx.gbl...
>I think Im over the long running queries thing... probably not going to
>kill my connections. I do appreciate your help, I probably just shouldnt
>have bothered to post that part and stuck to the bigger issue which is loss
>of connections. (Guess I freaked out and shoudnt have thrown that in
>there.) Any thoughts on the connections?
>
> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
> news:uF0$ZNgmFHA.3300@.TK2MSFTNGP15.phx.gbl...
>ChrisR wrote:
> Ive also got lots of these errors. Dont know if this helps.
>
You don't have to worry about many 208 errors. Many are reported for
temp table access in procedures even though the temp table is there
(it's just not there at compile time is what I think triggers it).
However, the 208 error could mean that an object that should be there is
missing. You'll need to check the statement executed just prior to the
error to see what object is being referenced.
Not sure about your lost connections. Are they just breaking randomly?
Or are statements not completing but the connection remains active?
David Gugick
Quest Software
www.imceda.com
www.quest.com|||One web server will suddenly start losing connections randomly. Once
restarted, its good for maybe 20 minutes.
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:OFoGpttmFHA.3020@.TK2MSFTNGP10.phx.gbl...
> ChrisR wrote:
>
> You don't have to worry about many 208 errors. Many are reported for temp
> table access in procedures even though the temp table is there (it's just
> not there at compile time is what I think triggers it). However, the 208
> error could mean that an object that should be there is missing. You'll
> need to check the statement executed just prior to the error to see what
> object is being referenced.
> Not sure about your lost connections. Are they just breaking randomly? Or
> are statements not completing but the connection remains active?
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com|||David I just reread... after talking to the web admin, its probably closer
to say that statements just arent completing but the connection is staying
open.
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:OFoGpttmFHA.3020@.TK2MSFTNGP10.phx.gbl...
> ChrisR wrote:
>
> You don't have to worry about many 208 errors. Many are reported for temp
> table access in procedures even though the temp table is there (it's just
> not there at compile time is what I think triggers it). However, the 208
> error could mean that an object that should be there is missing. You'll
> need to check the statement executed just prior to the error to see what
> object is being referenced.
> Not sure about your lost connections. Are they just breaking randomly? Or
> are statements not completing but the connection remains active?
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com

Error: 208, Severity: 16, State: 1

Ive also got lots of these errors. Dont know if this helps.
"ChrisR" <noemail@.bla.com> wrote in message
news:eV%23sQagmFHA.3648@.TK2MSFTNGP10.phx.gbl...
>I think Im over the long running queries thing... probably not going to
>kill my connections. I do appreciate your help, I probably just shouldnt
>have bothered to post that part and stuck to the bigger issue which is loss
>of connections. (Guess I freaked out and shoudnt have thrown that in
>there.) Any thoughts on the connections?
>
> "David Gugick" <david.gugick-nospam@.quest.com> wrote in message
> news:uF0$ZNgmFHA.3300@.TK2MSFTNGP15.phx.gbl...
>
ChrisR wrote:
> Ive also got lots of these errors. Dont know if this helps.
>
You don't have to worry about many 208 errors. Many are reported for
temp table access in procedures even though the temp table is there
(it's just not there at compile time is what I think triggers it).
However, the 208 error could mean that an object that should be there is
missing. You'll need to check the statement executed just prior to the
error to see what object is being referenced.
Not sure about your lost connections. Are they just breaking randomly?
Or are statements not completing but the connection remains active?
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||One web server will suddenly start losing connections randomly. Once
restarted, its good for maybe 20 minutes.
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:OFoGpttmFHA.3020@.TK2MSFTNGP10.phx.gbl...
> ChrisR wrote:
>
> You don't have to worry about many 208 errors. Many are reported for temp
> table access in procedures even though the temp table is there (it's just
> not there at compile time is what I think triggers it). However, the 208
> error could mean that an object that should be there is missing. You'll
> need to check the statement executed just prior to the error to see what
> object is being referenced.
> Not sure about your lost connections. Are they just breaking randomly? Or
> are statements not completing but the connection remains active?
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
|||David I just reread... after talking to the web admin, its probably closer
to say that statements just arent completing but the connection is staying
open.
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:OFoGpttmFHA.3020@.TK2MSFTNGP10.phx.gbl...
> ChrisR wrote:
>
> You don't have to worry about many 208 errors. Many are reported for temp
> table access in procedures even though the temp table is there (it's just
> not there at compile time is what I think triggers it). However, the 208
> error could mean that an object that should be there is missing. You'll
> need to check the statement executed just prior to the error to see what
> object is being referenced.
> Not sure about your lost connections. Are they just breaking randomly? Or
> are statements not completing but the connection remains active?
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com

Monday, March 19, 2012

Error: 17805, Severity: 20, State: 3 Invalid buffer received from client.

Howdy Folks,
Our site has been experiencing this issue for a couple of months now.. Hopefully someone else can assist, as Ive got to a point where I think issue lies within the application or a Microsoft bug. Web searches have reveled a number installations that have also had this error but its has not revealed an actual fix.

I understand this error code basically means data being returned to the client is getting either corrupted or the data is too large to fit into the buffer on the client side. Client in our case is the terminal server, here after called a application server

As the user base has increased form 5 to 20, I have noticed that the issue is occurring more frequently in comparison to when the company first started using the application /database. Its just about daily now...

The db server also has 8 other db's residing on it - but they are all less than 300 meg.

The attached PowerPoint doc has the trace info & the surrounding code for each process that has suffered a buffer error over a period of a week.

DB Server Environment: Win2000 SP4, SQL2000 SP3a, MDAC 2.7 SP1 refresh.
Application Environment: Written In house in VB.NET Framework 1.1 setup as a published app on a terminal server running windows 2000 SP4

Common features of the issue, that have been omitted from trace output for visibility reasons are:
- Involves 1 particular DB (thats accessed by VB app) & its developement db
- All connections are coming from 1 application server
- Issue does not relate to any particular site connecting to the application server using this application

I have reviewed & fixed several potential server side causes but this error still is occuring with in the environment:

MDAC versions must be common on application & server:
- Removed from equation by updating MDAC version on App server to be the same as DB Server: 2.7 SP1 Refresh

Network related
- Considered unlikely; we are also not experiencing network card errors on either server; also all db's would be experiencing connectivity errors.

Which leaves us with Application related options to review:
- Compilation error of application
- App parameter definitions to stored procedures are the correct data type
- Ensure values being passed do not exceed 4000 characters as that has also been known to create this error message
- I've asked the developer to review MS KB 827366 article, as it may be a valid test
- In regard to MSKB 832977 - I am not using pssdiag & have a later version of the MS Analyzer. But what I thought was interesting, is the statement that this problem occurs more frequently when an application submits a large remote procedure call (RPC) input buffer, especially when the RPC input buffer is greater than or equal to 8 KB. However, this problem may occur even if the input buffer is less than 4 KB
- A is using datatypes varchar & char - not nvarchar & nhar

Any assistance with this issue would be appreicated as server performance is being effected - these processes hang around for 1 - 5 mins before terminating (refer duration times in the powerpoint traces)

Thanks In advance

Suze.I think Reads column referrs to physical reads. If that's the case then the number is pretty high and may be the reason for the client timeout. Sporadic behavior of the same query may be caused by inconsistent execution plan generated. Do you use dynamic SQL a lot?|||Thank you for your question...

The number of reads appears only on the first slide, the other 7 don't have any reads - just the really long duration.
Because of this long duration & the audit logout entry for the same process id directly after the buffer error, I've assumed that the process is timing out. But in saying that users are not reporting that they have been kicked out of the application or receiving any error messages - so maybe way off in that assumption.

We are using SP's passing in parameter's. The developer reckons this means its not being built at runtime. As you might be able to tell, I'm a newbie - so I don't know if this means they are dynamic sql or not... are you able to advise.

Best Regards|||The 4000-limit was revealed in my previous environment when SP3 was applied. The FE code was...of course, JAVA, what else can cause this. And they were parsing the call to the stored procedure without TYPEing the parameters, which resulted in every character-based parameter to be interpreted as NVARCHAR. Now, the article (827366) is also referring to the possibility of data type size misalignment, where the value supplied may be outside of the boundaries allowed for a specific data type (just a hunch).|||I like the sound of your hunch. Unfortunately I can't provide the developer any proof - being a newbie in all. Anyway, I think I've done the next best thing by sending the developer the MSKB article 827366 again & Ant profiler to use so he can see what his code is doing - hopefully this will give him the visibility he needs.

Thanks again & Best Regards
Suze.

Wednesday, March 7, 2012

Error with Logins into SQL 2K

Hello,
I need some advice...
I am running SQL Server 2000... I've installed a new instance of this on a
new
server (to migrate from server1 to server2).
On server1, i have a group set up (domain/SQLGroup)...
On server2, i have the exact same group set up... unfortunately all the
users in this group doesn't get recognized by my new sql installation. I
get the error above (SQL Error 18456, State '28000') when they try and
login. (Access, VB progs, etc)...
I can change permissions for all the users in this group to have "Domain
Admins", but obviously i don't want to do that... by doing this though, all
access works as before...
SP4 is installed on server2, but not on server1...
Server1 is the Domain Controller...running sbs2000 (windows 2000 server).
Server2 is just windows 2003, and is dedicated to sql server 2000...
Does anyone have any suggestions on how to proceed with this?
Thanks.
Hi
In my opinion the real problem seems to be with an ODBC connection
Does itt succeeds with NT authentication if and only if the user is an
administrator ?
"RL Tech" <tech_support@.nospamuls.com> wrote in message
news:%23b1DfodUGHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hello,
> I need some advice...
> I am running SQL Server 2000... I've installed a new instance of this on a
> new
> server (to migrate from server1 to server2).
> On server1, i have a group set up (domain/SQLGroup)...
> On server2, i have the exact same group set up... unfortunately all the
> users in this group doesn't get recognized by my new sql installation. I
> get the error above (SQL Error 18456, State '28000') when they try and
> login. (Access, VB progs, etc)...
> I can change permissions for all the users in this group to have "Domain
> Admins", but obviously i don't want to do that... by doing this though,
> all
> access works as before...
> SP4 is installed on server2, but not on server1...
> Server1 is the Domain Controller...running sbs2000 (windows 2000 server).
> Server2 is just windows 2003, and is dedicated to sql server 2000...
> Does anyone have any suggestions on how to proceed with this?
> Thanks.
>
>
|||This would help.
http://support.microsoft.com/kb/298897
-oj
"RL Tech" <tech_support@.nospamuls.com> wrote in message
news:%23b1DfodUGHA.1688@.TK2MSFTNGP11.phx.gbl...
> Hello,
> I need some advice...
> I am running SQL Server 2000... I've installed a new instance of this on a
> new
> server (to migrate from server1 to server2).
> On server1, i have a group set up (domain/SQLGroup)...
> On server2, i have the exact same group set up... unfortunately all the
> users in this group doesn't get recognized by my new sql installation. I
> get the error above (SQL Error 18456, State '28000') when they try and
> login. (Access, VB progs, etc)...
> I can change permissions for all the users in this group to have "Domain
> Admins", but obviously i don't want to do that... by doing this though,
> all
> access works as before...
> SP4 is installed on server2, but not on server1...
> Server1 is the Domain Controller...running sbs2000 (windows 2000 server).
> Server2 is just windows 2003, and is dedicated to sql server 2000...
> Does anyone have any suggestions on how to proceed with this?
> Thanks.
>
>
|||On server1, NT (windows) authentication works with the group SQLGroup
(whether they are admin or not)... as long as they are part of SQLGroup,
they will be fine.
On server2, NT (windows) authentication only works with Admin users (thus by
adding all the users in SQLGroup to Domain Admins, they would work)... Which
i obviously don't want to do.
Both are mixed mode authentication...
ODBC has worked from the moment i set up that connection with that group...
In fact, it still works fine when i authenticate non-windows usernames...
Do i need to make server2 a Domain controller?
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eeAlh4jUGHA.5884@.TK2MSFTNGP14.phx.gbl...[vbcol=seagreen]
> Hi
> In my opinion the real problem seems to be with an ODBC connection
>
> Does itt succeeds with NT authentication if and only if the user is an
> administrator ?
>
> "RL Tech" <tech_support@.nospamuls.com> wrote in message
> news:%23b1DfodUGHA.1688@.TK2MSFTNGP11.phx.gbl...
a[vbcol=seagreen]
I[vbcol=seagreen]
server).
>
|||Hi,
I did look at it yesterday, but i wasn't sure if that was the problem...
I'll give it a try and see if it works out..
Thanks!
...Robin
"oj" <nospam_ojngo@.home.com> wrote in message
news:u1vHDDlUGHA.5004@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> This would help.
> http://support.microsoft.com/kb/298897
>
> --
> -oj
>
> "RL Tech" <tech_support@.nospamuls.com> wrote in message
> news:%23b1DfodUGHA.1688@.TK2MSFTNGP11.phx.gbl...
a[vbcol=seagreen]
I[vbcol=seagreen]
server).
>

Wednesday, February 15, 2012

Error while executing the Best Practice Group

Hi,
I've tried to install the BPA on two different SQL servers, but in every
case I get the following error executing it (bellow). I've reinstalled
several times and used different computers and SQL's. The .NET framework is
1.1. Any ideas?
"Error while executing the Best Practice Group. See the log file
Cmpl_javierx_0001_1.1.1.1_sqlbpa.log. Error message: Execution log not found
in the repository"
Thanks
Any ideas? Anyone?
"Javier" wrote:

> Hi,
> I've tried to install the BPA on two different SQL servers, but in every
> case I get the following error executing it (bellow). I've reinstalled
> several times and used different computers and SQL's. The .NET framework is
> 1.1. Any ideas?
> "Error while executing the Best Practice Group. See the log file
> Cmpl_javierx_0001_1.1.1.1_sqlbpa.log. Error message: Execution log not found
> in the repository"
> Thanks
>
>
|||Hi Javier,
If you didn't find your solution yet, I've got the same problem as you
but fix it by unchecking the no Count option on in the SQL Server Properties.
In the connection Tab, you will need to uncheck "no Count"... Try that, it
should fix the problem...
"Javier Limones" wrote:
[vbcol=seagreen]
> Any ideas? Anyone?
> "Javier" wrote:
|||Dennis,
Sorry for the late reply... The servers we use need the "No Count" option
checked for an application to work... Is there another way to fix this?
Javier
"Denis Daigle" wrote:
[vbcol=seagreen]
> Hi Javier,
> If you didn't find your solution yet, I've got the same problem as you
> but fix it by unchecking the no Count option on in the SQL Server Properties.
> In the connection Tab, you will need to uncheck "no Count"... Try that, it
> should fix the problem...
> "Javier Limones" wrote: