When installing SQL 2005 on a 2 node cluster, the install fails saying setup
on the remote machine failed, check the task scheduler log. The log on the
remote machine says "Unable to start task...Access is denied". Any idea how
to get around this?
Environment is DL585, Windows 2003 x64 sp1, SQL 2005 x64 Dev Edition
I also need to mention that I have Act as part of the operating system and
log on as a service rights on both nodes.
"Brad" wrote:
> When installing SQL 2005 on a 2 node cluster, the install fails saying setup
> on the remote machine failed, check the task scheduler log. The log on the
> remote machine says "Unable to start task...Access is denied". Any idea how
> to get around this?
> Environment is DL585, Windows 2003 x64 sp1, SQL 2005 x64 Dev Edition
|||You have to install using a domain account that is a member of the local
administrators group on each server.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Brad" <Brad@.discussions.microsoft.com> wrote in message
news:AA1196F9-0113-4844-B2C4-1BEABCAE97F3@.microsoft.com...[vbcol=seagreen]
>I also need to mention that I have Act as part of the operating system and
> log on as a service rights on both nodes.
> "Brad" wrote:
|||Permissions. The account that you are using to install the failover cluster
instance must be a member of the local admin group on each machine. (The
service accounts related to SQL Server do NOT need to be.)
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Brad" <Brad@.discussions.microsoft.com> wrote in message
news:F9ED4AEF-08EF-40CD-845E-E86794714C8A@.microsoft.com...
> When installing SQL 2005 on a 2 node cluster, the install fails saying
> setup
> on the remote machine failed, check the task scheduler log. The log on
> the
> remote machine says "Unable to start task...Access is denied". Any idea
> how
> to get around this?
> Environment is DL585, Windows 2003 x64 sp1, SQL 2005 x64 Dev Edition
|||Yes, thank you. The domain account I am using is already a member of the
admin group on both nodes. The error still persists.
"Geoff N. Hiten" wrote:
> You have to install using a domain account that is a member of the local
> administrators group on each server.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Brad" <Brad@.discussions.microsoft.com> wrote in message
> news:AA1196F9-0113-4844-B2C4-1BEABCAE97F3@.microsoft.com...
>
>
|||I didn't provide that information up front but the account is a member of the
admin group on both boxes.
"Michael Hotek" wrote:
> Permissions. The account that you are using to install the failover cluster
> instance must be a member of the local admin group on each machine. (The
> service accounts related to SQL Server do NOT need to be.)
> --
> Mike
> http://www.solidqualitylearning.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
> "Brad" <Brad@.discussions.microsoft.com> wrote in message
> news:F9ED4AEF-08EF-40CD-845E-E86794714C8A@.microsoft.com...
>
>
|||Hi,
But is it the LOCAL ADMIN ACCOUNT not domain admin account?
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"Brad" <Brad@.discussions.microsoft.com> wrote in message
news:56372080-3701-40DA-8CF1-9B002BDC2E11@.microsoft.com...[vbcol=seagreen]
> Yes, thank you. The domain account I am using is already a member of the
> admin group on both nodes. The error still persists.
> "Geoff N. Hiten" wrote:
|||Yes, it is in the local admin group on both machines.
"Nik Marshall-Blank" wrote:
> Hi,
> But is it the LOCAL ADMIN ACCOUNT not domain admin account?
> --
> Nik Marshall-Blank MCSD/MCDBA
> Linz, Austria
> "Brad" <Brad@.discussions.microsoft.com> wrote in message
> news:56372080-3701-40DA-8CF1-9B002BDC2E11@.microsoft.com...
>
>
|||Make sure the task scheduler service is enabled and running on all nodes.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Brad" <Brad@.discussions.microsoft.com> wrote in message
news:DC6D365B-B9E9-4A59-947C-0A947C91826B@.microsoft.com...[vbcol=seagreen]
> Yes, it is in the local admin group on both machines.
> "Nik Marshall-Blank" wrote:
|||Did you ever get a resolution on this ? I am having the exact same
problem.
I have checked all the obvious problems, like permissions, task
scheduler service running, etc.
I am going to call Microsoft Support tomorrow if I can't figure this
out.
Brad wrote:[vbcol=seagreen]
> I didn't provide that information up front but the account is a member of the
> admin group on both boxes.
> "Michael Hotek" wrote:
sqlsql
Showing posts with label remote. Show all posts
Showing posts with label remote. Show all posts
Thursday, March 22, 2012
Friday, February 24, 2012
Clients in different domains
I have situation like this:
Company with one head office and one remote office. In the two offices I have two domains with two PDCs. The two networks are connected with eachother through leased line and the routers are configured properly. The SQL Server is on the PDC in head office and "local" clients connect fine. I cannot connect from the remote office. I think that I have folowing solutions:
1. make trust relationships between two domains - it will be hard a little bit because second PDC is samba on linux
2. make all clients in remote office to be members of the head office domain - potential problems if the leased line drops
3. make all clients to log in with same account as SQL Server logs locally - stupid
4. something else - what?
Thanks in advance!
DanielSql authentication is designed for such cases as this.
http://msdn.microsoft.com/library/en-us/architec/8_ar_cs_79kj.asp|||I am with SQL Server authentication and despite of this I cannot connect from some computers...|||Take a look at the following kb and make sure the firewall is setup correctly.
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
Company with one head office and one remote office. In the two offices I have two domains with two PDCs. The two networks are connected with eachother through leased line and the routers are configured properly. The SQL Server is on the PDC in head office and "local" clients connect fine. I cannot connect from the remote office. I think that I have folowing solutions:
1. make trust relationships between two domains - it will be hard a little bit because second PDC is samba on linux
2. make all clients in remote office to be members of the head office domain - potential problems if the leased line drops
3. make all clients to log in with same account as SQL Server logs locally - stupid
4. something else - what?
Thanks in advance!
DanielSql authentication is designed for such cases as this.
http://msdn.microsoft.com/library/en-us/architec/8_ar_cs_79kj.asp|||I am with SQL Server authentication and despite of this I cannot connect from some computers...|||Take a look at the following kb and make sure the firewall is setup correctly.
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
Clients being disconnected periodically over WAN
Some background information. I have a Windows 2003 Server that is also
running SQL 2000 on network "172.16.30.0". I have a remote facility,
"172.16.20.0", that is connected by WAN with a full T1 line. When the remote
users login to our SQL application the server creates a routing statement for
each user's machine. If I do a "route print" statement I see the static
routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
Active and Persistent routes. I also see the IP addresses of the remote
computers under Active Routes. For some reason the remote users are being
disconnected from the SQL application but their IP addresses still remain
under Active Routes. They cannot log back into the SQL application until I
manually delete their routes from the SQL Server. Once this is done they can
successful log back into the SQL application. Is the server suppose to keep
track of remote machine routing connections? We migrated from Frame Relay to
VPN connectivity and I do not recall seing each remote user's IP address
within the "Route Print" statement previously.
Not my usual turf, but since no one else responded, I'll put my foot in my
mouth.
I think you have a network issue, not a database issue. It sounds like
youhave a timeout in TCP/IP (or whatever) that is doing the disconnect. I
have not seen SS drop a user or prevent one from logging in (assuming valid
userid, etc), even multiple connections from the same place.
I know there are several places that timeout could be, so someone with more
of a networks background will have to help you point your shotgun.
Joseph R.P. Maloney, CSP,CCP,CDP
"Bill Freeze" wrote:
> Some background information. I have a Windows 2003 Server that is also
> running SQL 2000 on network "172.16.30.0". I have a remote facility,
> "172.16.20.0", that is connected by WAN with a full T1 line. When the remote
> users login to our SQL application the server creates a routing statement for
> each user's machine. If I do a "route print" statement I see the static
> routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
> Active and Persistent routes. I also see the IP addresses of the remote
> computers under Active Routes. For some reason the remote users are being
> disconnected from the SQL application but their IP addresses still remain
> under Active Routes. They cannot log back into the SQL application until I
> manually delete their routes from the SQL Server. Once this is done they can
> successful log back into the SQL application. Is the server suppose to keep
> track of remote machine routing connections? We migrated from Frame Relay to
> VPN connectivity and I do not recall seing each remote user's IP address
> within the "Route Print" statement previously.
>
running SQL 2000 on network "172.16.30.0". I have a remote facility,
"172.16.20.0", that is connected by WAN with a full T1 line. When the remote
users login to our SQL application the server creates a routing statement for
each user's machine. If I do a "route print" statement I see the static
routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
Active and Persistent routes. I also see the IP addresses of the remote
computers under Active Routes. For some reason the remote users are being
disconnected from the SQL application but their IP addresses still remain
under Active Routes. They cannot log back into the SQL application until I
manually delete their routes from the SQL Server. Once this is done they can
successful log back into the SQL application. Is the server suppose to keep
track of remote machine routing connections? We migrated from Frame Relay to
VPN connectivity and I do not recall seing each remote user's IP address
within the "Route Print" statement previously.
Not my usual turf, but since no one else responded, I'll put my foot in my
mouth.
I think you have a network issue, not a database issue. It sounds like
youhave a timeout in TCP/IP (or whatever) that is doing the disconnect. I
have not seen SS drop a user or prevent one from logging in (assuming valid
userid, etc), even multiple connections from the same place.
I know there are several places that timeout could be, so someone with more
of a networks background will have to help you point your shotgun.
Joseph R.P. Maloney, CSP,CCP,CDP
"Bill Freeze" wrote:
> Some background information. I have a Windows 2003 Server that is also
> running SQL 2000 on network "172.16.30.0". I have a remote facility,
> "172.16.20.0", that is connected by WAN with a full T1 line. When the remote
> users login to our SQL application the server creates a routing statement for
> each user's machine. If I do a "route print" statement I see the static
> routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
> Active and Persistent routes. I also see the IP addresses of the remote
> computers under Active Routes. For some reason the remote users are being
> disconnected from the SQL application but their IP addresses still remain
> under Active Routes. They cannot log back into the SQL application until I
> manually delete their routes from the SQL Server. Once this is done they can
> successful log back into the SQL application. Is the server suppose to keep
> track of remote machine routing connections? We migrated from Frame Relay to
> VPN connectivity and I do not recall seing each remote user's IP address
> within the "Route Print" statement previously.
>
Clients being disconnected periodically over WAN
Some background information. I have a Windows 2003 Server that is also
running SQL 2000 on network "172.16.30.0". I have a remote facility,
"172.16.20.0", that is connected by WAN with a full T1 line. When the remote
users login to our SQL application the server creates a routing statement for
each user's machine. If I do a "route print" statement I see the static
routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
Active and Persistent routes. I also see the IP addresses of the remote
computers under Active Routes. For some reason the remote users are being
disconnected from the SQL application but their IP addresses still remain
under Active Routes. They cannot log back into the SQL application until I
manually delete their routes from the SQL Server. Once this is done they can
successful log back into the SQL application. Is the server suppose to keep
track of remote machine routing connections? We migrated from Frame Relay to
VPN connectivity and I do not recall seing each remote user's IP address
within the "Route Print" statement previously.Not my usual turf, but since no one else responded, I'll put my foot in my
mouth.
I think you have a network issue, not a database issue. It sounds like
youhave a timeout in TCP/IP (or whatever) that is doing the disconnect. I
have not seen SS drop a user or prevent one from logging in (assuming valid
userid, etc), even multiple connections from the same place.
I know there are several places that timeout could be, so someone with more
of a networks background will have to help you point your shotgun.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Bill Freeze" wrote:
> Some background information. I have a Windows 2003 Server that is also
> running SQL 2000 on network "172.16.30.0". I have a remote facility,
> "172.16.20.0", that is connected by WAN with a full T1 line. When the remote
> users login to our SQL application the server creates a routing statement for
> each user's machine. If I do a "route print" statement I see the static
> routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
> Active and Persistent routes. I also see the IP addresses of the remote
> computers under Active Routes. For some reason the remote users are being
> disconnected from the SQL application but their IP addresses still remain
> under Active Routes. They cannot log back into the SQL application until I
> manually delete their routes from the SQL Server. Once this is done they can
> successful log back into the SQL application. Is the server suppose to keep
> track of remote machine routing connections? We migrated from Frame Relay to
> VPN connectivity and I do not recall seing each remote user's IP address
> within the "Route Print" statement previously.
>
running SQL 2000 on network "172.16.30.0". I have a remote facility,
"172.16.20.0", that is connected by WAN with a full T1 line. When the remote
users login to our SQL application the server creates a routing statement for
each user's machine. If I do a "route print" statement I see the static
routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
Active and Persistent routes. I also see the IP addresses of the remote
computers under Active Routes. For some reason the remote users are being
disconnected from the SQL application but their IP addresses still remain
under Active Routes. They cannot log back into the SQL application until I
manually delete their routes from the SQL Server. Once this is done they can
successful log back into the SQL application. Is the server suppose to keep
track of remote machine routing connections? We migrated from Frame Relay to
VPN connectivity and I do not recall seing each remote user's IP address
within the "Route Print" statement previously.Not my usual turf, but since no one else responded, I'll put my foot in my
mouth.
I think you have a network issue, not a database issue. It sounds like
youhave a timeout in TCP/IP (or whatever) that is doing the disconnect. I
have not seen SS drop a user or prevent one from logging in (assuming valid
userid, etc), even multiple connections from the same place.
I know there are several places that timeout could be, so someone with more
of a networks background will have to help you point your shotgun.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Bill Freeze" wrote:
> Some background information. I have a Windows 2003 Server that is also
> running SQL 2000 on network "172.16.30.0". I have a remote facility,
> "172.16.20.0", that is connected by WAN with a full T1 line. When the remote
> users login to our SQL application the server creates a routing statement for
> each user's machine. If I do a "route print" statement I see the static
> routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
> Active and Persistent routes. I also see the IP addresses of the remote
> computers under Active Routes. For some reason the remote users are being
> disconnected from the SQL application but their IP addresses still remain
> under Active Routes. They cannot log back into the SQL application until I
> manually delete their routes from the SQL Server. Once this is done they can
> successful log back into the SQL application. Is the server suppose to keep
> track of remote machine routing connections? We migrated from Frame Relay to
> VPN connectivity and I do not recall seing each remote user's IP address
> within the "Route Print" statement previously.
>
Clients being disconnected periodically over WAN
Some background information. I have a Windows 2003 Server that is also
running SQL 2000 on network "172.16.30.0". I have a remote facility,
"172.16.20.0", that is connected by WAN with a full T1 line. When the remot
e
users login to our SQL application the server creates a routing statement fo
r
each user's machine. If I do a "route print" statement I see the static
routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
Active and Persistent routes. I also see the IP addresses of the remote
computers under Active Routes. For some reason the remote users are being
disconnected from the SQL application but their IP addresses still remain
under Active Routes. They cannot log back into the SQL application until I
manually delete their routes from the SQL Server. Once this is done they ca
n
successful log back into the SQL application. Is the server suppose to keep
track of remote machine routing connections? We migrated from Frame Relay t
o
VPN connectivity and I do not recall seing each remote user's IP address
within the "Route Print" statement previously.Not my usual turf, but since no one else responded, I'll put my foot in my
mouth.
I think you have a network issue, not a database issue. It sounds like
youhave a timeout in TCP/IP (or whatever) that is doing the disconnect. I
have not seen SS drop a user or prevent one from logging in (assuming valid
userid, etc), even multiple connections from the same place.
I know there are several places that timeout could be, so someone with more
of a networks background will have to help you point your shotgun.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Bill Freeze" wrote:
> Some background information. I have a Windows 2003 Server that is also
> running SQL 2000 on network "172.16.30.0". I have a remote facility,
> "172.16.20.0", that is connected by WAN with a full T1 line. When the rem
ote
> users login to our SQL application the server creates a routing statement
for
> each user's machine. If I do a "route print" statement I see the static
> routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under bo
th
> Active and Persistent routes. I also see the IP addresses of the remote
> computers under Active Routes. For some reason the remote users are being
> disconnected from the SQL application but their IP addresses still remain
> under Active Routes. They cannot log back into the SQL application until
I
> manually delete their routes from the SQL Server. Once this is done they
can
> successful log back into the SQL application. Is the server suppose to ke
ep
> track of remote machine routing connections? We migrated from Frame Relay
to
> VPN connectivity and I do not recall seing each remote user's IP address
> within the "Route Print" statement previously.
>
running SQL 2000 on network "172.16.30.0". I have a remote facility,
"172.16.20.0", that is connected by WAN with a full T1 line. When the remot
e
users login to our SQL application the server creates a routing statement fo
r
each user's machine. If I do a "route print" statement I see the static
routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under both
Active and Persistent routes. I also see the IP addresses of the remote
computers under Active Routes. For some reason the remote users are being
disconnected from the SQL application but their IP addresses still remain
under Active Routes. They cannot log back into the SQL application until I
manually delete their routes from the SQL Server. Once this is done they ca
n
successful log back into the SQL application. Is the server suppose to keep
track of remote machine routing connections? We migrated from Frame Relay t
o
VPN connectivity and I do not recall seing each remote user's IP address
within the "Route Print" statement previously.Not my usual turf, but since no one else responded, I'll put my foot in my
mouth.
I think you have a network issue, not a database issue. It sounds like
youhave a timeout in TCP/IP (or whatever) that is doing the disconnect. I
have not seen SS drop a user or prevent one from logging in (assuming valid
userid, etc), even multiple connections from the same place.
I know there are several places that timeout could be, so someone with more
of a networks background will have to help you point your shotgun.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"Bill Freeze" wrote:
> Some background information. I have a Windows 2003 Server that is also
> running SQL 2000 on network "172.16.30.0". I have a remote facility,
> "172.16.20.0", that is connected by WAN with a full T1 line. When the rem
ote
> users login to our SQL application the server creates a routing statement
for
> each user's machine. If I do a "route print" statement I see the static
> routes for the facility, "172.16.20.0 255.255.255.0 172.16.30.11" under bo
th
> Active and Persistent routes. I also see the IP addresses of the remote
> computers under Active Routes. For some reason the remote users are being
> disconnected from the SQL application but their IP addresses still remain
> under Active Routes. They cannot log back into the SQL application until
I
> manually delete their routes from the SQL Server. Once this is done they
can
> successful log back into the SQL application. Is the server suppose to ke
ep
> track of remote machine routing connections? We migrated from Frame Relay
to
> VPN connectivity and I do not recall seing each remote user's IP address
> within the "Route Print" statement previously.
>
Client Web Browser & Remote SQL Script Error?
Hello all,
I know that this is a long shot, but I have a problem which someone
reading this group *may* just be able to shed some light on.
We have a new internal personnel planner/attendance system in place. It
uses a web interface to allow members of staff to select their site
location for any week, request leave and record absences.
The server-side scripting is composed of VB/ASP and Javascript which
ultimately queries & writes to an MS SQL Server 2000 database via an
ODBC connection between webserver (IIS6.0).
Here is the problem and I *know* that it sounds unlikely/impossible but
we carried out exhaustive tests.
-> I open a web browser on my local PC (XP Pro SP2)
-> Login to the web-based planning system
-> Update information
-> Submit Changes
At this point I get a script error:
--error message--
Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
[Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax
near ')'.
/staff/wfp/Whereabouts/writeAbsence_v2_5.asp, line 108
------
Which is fair enough as it probably points to a problem with the SQL
statement being passed by the .asp page.
***BUT*** I _only_ get this message when I access the page via a browser
from certain PCs!
I have tried 3 browsers: MSIE6, Firefox1.5, Opera8.5.
I have obviously ensured that it isn't any kind of browser caching issue.
I have no issues using scripted-based web pages in general from the PC
in question.
I have checked the regional settings to ensure that I am using a
standard character set.
I *can* submit database changes via web browsers from most other PCs on
our network, without incurring the error message.
Even when I get the error message, the values are written to the db and
the information is updated.
The other PCs from which I am experiencing the same difficulty are
servers running Win2000 & Win2003 respectively.
Is there any kind of OS/User Profile setting which would mean that
scripts running on a remote webserver would fall over when trying to
perform an SQL write?
Could it be some kind of character encoding issue, which means that the
parameters that are received by the .asp script and then written via the
SQL statement are mangled in any way?
I can't see that there is any kind of local setting that would influence
whether remote scripts would or would not cause an error such as this.
If anyone has any ideas, has encountered anything similar or can shed
light on a system-specific setting or feature that may cause this,
please post your thoughts.
Yours Gratefully
GuyIf the server-side code path is identical, I suggest you focus on the client
browser settings. My guess is that you have client-side script that doesn't
execute under certain configurations so data isn't posted back as expected.
This causes your server-side script to generate an invalid SQL statement
like 'INSERT INTO MyTable VALUES()' and results in the error you describe.
There are other clues in your post that you aren't following Best Practices
so you might want to revisit the items below.
Rather than ODBC, consider using the OLE DB provider directly. For Windows
Authentication:
Provider=SQLOLEDB;Data Source=MyServer;Initial Catalog=MyDatabase;Integrated
Security=SSPI"
For SQL Authentication:
Provider=SQLOLEDB;Data Source=MyServer;Initial Catalog=MyDatabase;User
Id=MyLogin;Password=myPassword1"
Consider using parameterized SQL Statements rather than build SQL statement
strings. This is more secure, provides better performance and eliminates
the need to double-up embedded quotes and format dates. For example:
myCommand.CommandText = "INSERT INTO MyTable VALUES(?)"
Set myIntegerParameter = myCommand.CreateParameter( _
"@.MyIntegerParameter", 3, 1)
myCommand.Parameters.Append myIntegerParameter
myIntegerParameter.Value = Request("UserValue")
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Guy Debord" <laugh@.life.org> wrote in message
news:tyDIf.45673$Rw6.23215@.newsfe7-gui.ntli.net...
> Hello all,
> I know that this is a long shot, but I have a problem which someone
> reading this group *may* just be able to shed some light on.
> We have a new internal personnel planner/attendance system in place. It
> uses a web interface to allow members of staff to select their site
> location for any week, request leave and record absences.
> The server-side scripting is composed of VB/ASP and Javascript which
> ultimately queries & writes to an MS SQL Server 2000 database via an
> ODBC connection between webserver (IIS6.0).
> Here is the problem and I *know* that it sounds unlikely/impossible but
> we carried out exhaustive tests.
> -> I open a web browser on my local PC (XP Pro SP2)
> -> Login to the web-based planning system
> -> Update information
> -> Submit Changes
> At this point I get a script error:
> --error message--
> Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
> [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax
> near ')'.
> /staff/wfp/Whereabouts/writeAbsence_v2_5.asp, line 108
> ------
> Which is fair enough as it probably points to a problem with the SQL
> statement being passed by the .asp page.
> ***BUT*** I _only_ get this message when I access the page via a browser
> from certain PCs!
> I have tried 3 browsers: MSIE6, Firefox1.5, Opera8.5.
> I have obviously ensured that it isn't any kind of browser caching issue.
> I have no issues using scripted-based web pages in general from the PC
> in question.
> I have checked the regional settings to ensure that I am using a
> standard character set.
> I *can* submit database changes via web browsers from most other PCs on
> our network, without incurring the error message.
> Even when I get the error message, the values are written to the db and
> the information is updated.
> The other PCs from which I am experiencing the same difficulty are
> servers running Win2000 & Win2003 respectively.
> Is there any kind of OS/User Profile setting which would mean that
> scripts running on a remote webserver would fall over when trying to
> perform an SQL write?
> Could it be some kind of character encoding issue, which means that the
> parameters that are received by the .asp script and then written via the
> SQL statement are mangled in any way?
> I can't see that there is any kind of local setting that would influence
> whether remote scripts would or would not cause an error such as this.
> If anyone has any ideas, has encountered anything similar or can shed
> light on a system-specific setting or feature that may cause this,
> please post your thoughts.
> Yours Gratefully
> Guy|||Dan,
Thanks for taking the time to offer up your suggestions.
Using parameterized SQL statements looks like it may well help to
eliminate some of the errors which are easy to make using lengthy
statement strings.
Thanks for the tip.
The OLE DB versus ODBC issue is one that I have one that I will address.
As for the the client-side script suggestion, I'll dig deep and let you
know if I can find any likely suspects.
Thanks again,
Guy|||Guy Debord (laugh@.life.org) writes:
> At this point I get a script error:
> --error message--
> Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
> [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax
> near ')'.
> /staff/wfp/Whereabouts/writeAbsence_v2_5.asp, line 108
I've seen plenty of those pages on the web!
> ***BUT*** I _only_ get this message when I access the page via a browser
> from certain PCs!
Well, rather than looking at the PCs, look at the SQL instead. Set up a
trace with Profiler, and see what is being sent to SQL Server. Include
the error events and StmtStarting.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx
Sunday, February 19, 2012
Client software
I have several developers that want access to my SQL server and I was
wondering instead of giving them Remote desktop access to access Enterprise
manager. I am going to install the SQL client tools locally on their PC.
My SQL server is behind a firewall, does anyone know what port needs to be
opened so I can see my SQL server in my list of available SQL servers.
Because I see all my SQL server on the local network, but not ones on other
networks.
Hope this makes some sense. Thanks for the help.
The following article answers questions related to firewall
ports:
INF: TCP Ports Needed for Communication to SQL Server
Through a Firewall
http://support.microsoft.com/?id=287932
However, what servers are listed in whatever tool drop downs
doesn't necessarily mean you have an issue with the firewall
ports. What servers are listed may not be a complete list
due to broadcast issues, network routers/subnet issues,
instances may not respond within the timeout period, etc.
The network architecture, configuration to wherever this SQL
Server box lives would be another factor.
You can always type in an IP address or a server name if a
server doesn't show up in the list.
-Sue
On Mon, 27 Feb 2006 12:38:02 -0500, "andespoint"
<andespoint@.nospam_yahoo.com> wrote:
>I have several developers that want access to my SQL server and I was
>wondering instead of giving them Remote desktop access to access Enterprise
>manager. I am going to install the SQL client tools locally on their PC.
>My SQL server is behind a firewall, does anyone know what port needs to be
>opened so I can see my SQL server in my list of available SQL servers.
>Because I see all my SQL server on the local network, but not ones on other
>networks.
>Hope this makes some sense. Thanks for the help.
>
wondering instead of giving them Remote desktop access to access Enterprise
manager. I am going to install the SQL client tools locally on their PC.
My SQL server is behind a firewall, does anyone know what port needs to be
opened so I can see my SQL server in my list of available SQL servers.
Because I see all my SQL server on the local network, but not ones on other
networks.
Hope this makes some sense. Thanks for the help.
The following article answers questions related to firewall
ports:
INF: TCP Ports Needed for Communication to SQL Server
Through a Firewall
http://support.microsoft.com/?id=287932
However, what servers are listed in whatever tool drop downs
doesn't necessarily mean you have an issue with the firewall
ports. What servers are listed may not be a complete list
due to broadcast issues, network routers/subnet issues,
instances may not respond within the timeout period, etc.
The network architecture, configuration to wherever this SQL
Server box lives would be another factor.
You can always type in an IP address or a server name if a
server doesn't show up in the list.
-Sue
On Mon, 27 Feb 2006 12:38:02 -0500, "andespoint"
<andespoint@.nospam_yahoo.com> wrote:
>I have several developers that want access to my SQL server and I was
>wondering instead of giving them Remote desktop access to access Enterprise
>manager. I am going to install the SQL client tools locally on their PC.
>My SQL server is behind a firewall, does anyone know what port needs to be
>opened so I can see my SQL server in my list of available SQL servers.
>Because I see all my SQL server on the local network, but not ones on other
>networks.
>Hope this makes some sense. Thanks for the help.
>
Client software
I have several developers that want access to my SQL server and I was
wondering instead of giving them Remote desktop access to access Enterprise
manager. I am going to install the SQL client tools locally on their PC.
My SQL server is behind a firewall, does anyone know what port needs to be
opened so I can see my SQL server in my list of available SQL servers.
Because I see all my SQL server on the local network, but not ones on other
networks.
Hope this makes some sense. Thanks for the help.The following article answers questions related to firewall
ports:
INF: TCP Ports Needed for Communication to SQL Server
Through a Firewall
http://support.microsoft.com/?id=287932
However, what servers are listed in whatever tool drop downs
doesn't necessarily mean you have an issue with the firewall
ports. What servers are listed may not be a complete list
due to broadcast issues, network routers/subnet issues,
instances may not respond within the timeout period, etc.
The network architecture, configuration to wherever this SQL
Server box lives would be another factor.
You can always type in an IP address or a server name if a
server doesn't show up in the list.
-Sue
On Mon, 27 Feb 2006 12:38:02 -0500, "andespoint"
<andespoint@.nospam_yahoo.com> wrote:
>I have several developers that want access to my SQL server and I was
>wondering instead of giving them Remote desktop access to access Enterprise
>manager. I am going to install the SQL client tools locally on their PC.
>My SQL server is behind a firewall, does anyone know what port needs to be
>opened so I can see my SQL server in my list of available SQL servers.
>Because I see all my SQL server on the local network, but not ones on other
>networks.
>Hope this makes some sense. Thanks for the help.
>
wondering instead of giving them Remote desktop access to access Enterprise
manager. I am going to install the SQL client tools locally on their PC.
My SQL server is behind a firewall, does anyone know what port needs to be
opened so I can see my SQL server in my list of available SQL servers.
Because I see all my SQL server on the local network, but not ones on other
networks.
Hope this makes some sense. Thanks for the help.The following article answers questions related to firewall
ports:
INF: TCP Ports Needed for Communication to SQL Server
Through a Firewall
http://support.microsoft.com/?id=287932
However, what servers are listed in whatever tool drop downs
doesn't necessarily mean you have an issue with the firewall
ports. What servers are listed may not be a complete list
due to broadcast issues, network routers/subnet issues,
instances may not respond within the timeout period, etc.
The network architecture, configuration to wherever this SQL
Server box lives would be another factor.
You can always type in an IP address or a server name if a
server doesn't show up in the list.
-Sue
On Mon, 27 Feb 2006 12:38:02 -0500, "andespoint"
<andespoint@.nospam_yahoo.com> wrote:
>I have several developers that want access to my SQL server and I was
>wondering instead of giving them Remote desktop access to access Enterprise
>manager. I am going to install the SQL client tools locally on their PC.
>My SQL server is behind a firewall, does anyone know what port needs to be
>opened so I can see my SQL server in my list of available SQL servers.
>Because I see all my SQL server on the local network, but not ones on other
>networks.
>Hope this makes some sense. Thanks for the help.
>
Sunday, February 12, 2012
Client cannot access SQL 2005 Express Server
I've installed SQL 2005 Express, enabled local and Remote connections but my client app cannot connect to the SQL server. I'm getting access denied or SQL does not exists. Any idea's on how to resolve this issue?
Perhaps these articles will help:
Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
Configuration -Connect to SQL Express from "downlevel clients"
http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx
Configuration -Connect to SQL Express and ‘Stay Connected’
http://betav.com/blog/billva/2006/06/getting_and_staying_connected.html
Subscribe to:
Posts (Atom)