Wednesday, March 7, 2012
errors
server 2000, i have many webs over a single server and i do not want to show
errors in explorer when a bad user writes false urls intentionally trying to
inject code via sql. Or maybe that security i have to control via the code in
asp.
Thanks in advance
Trapping the error in the application is the best way.
Jason Massie
Web: http://statisticsio.com
RSS: http://feeds.feedburner.com/statisticsio
"Arturo J" <Arturo J@.discussions.microsoft.com> wrote in message
news:5B649D1E-2B9C-4293-A383-90F28FD1D8A8@.microsoft.com...
> Hello everyone, i like to know if someone knows how to denied errors y SQL
> server 2000, i have many webs over a single server and i do not want to
> show
> errors in explorer when a bad user writes false urls intentionally trying
> to
> inject code via sql. Or maybe that security i have to control via the code
> in
> asp.
> Thanks in advance
>
|||Thanks for your qick repond, just one doubt, you mean to manage the error
reports through the asp?
"Jason Massie" wrote:
> Trapping the error in the application is the best way.
> --
> Jason Massie
> Web: http://statisticsio.com
> RSS: http://feeds.feedburner.com/statisticsio
> "Arturo J" <Arturo J@.discussions.microsoft.com> wrote in message
> news:5B649D1E-2B9C-4293-A383-90F28FD1D8A8@.microsoft.com...
>
>
errors
server 2000, i have many webs over a single server and i do not want to show
errors in explorer when a bad user writes false urls intentionally trying to
inject code via sql. Or maybe that security i have to control via the code in
asp.
Thanks in advanceTrapping the error in the application is the best way.
--
Jason Massie
Web: http://statisticsio.com
RSS: http://feeds.feedburner.com/statisticsio
"Arturo J" <Arturo J@.discussions.microsoft.com> wrote in message
news:5B649D1E-2B9C-4293-A383-90F28FD1D8A8@.microsoft.com...
> Hello everyone, i like to know if someone knows how to denied errors y SQL
> server 2000, i have many webs over a single server and i do not want to
> show
> errors in explorer when a bad user writes false urls intentionally trying
> to
> inject code via sql. Or maybe that security i have to control via the code
> in
> asp.
> Thanks in advance
>|||Thanks for your qick repond, just one doubt, you mean to manage the error
reports through the asp?
"Jason Massie" wrote:
> Trapping the error in the application is the best way.
> --
> Jason Massie
> Web: http://statisticsio.com
> RSS: http://feeds.feedburner.com/statisticsio
> "Arturo J" <Arturo J@.discussions.microsoft.com> wrote in message
> news:5B649D1E-2B9C-4293-A383-90F28FD1D8A8@.microsoft.com...
> > Hello everyone, i like to know if someone knows how to denied errors y SQL
> > server 2000, i have many webs over a single server and i do not want to
> > show
> > errors in explorer when a bad user writes false urls intentionally trying
> > to
> > inject code via sql. Or maybe that security i have to control via the code
> > in
> > asp.
> >
> > Thanks in advance
> >
> >
>
>
errors
server 2000, i have many webs over a single server and i do not want to show
errors in explorer when a bad user writes false urls intentionally trying to
inject code via sql. Or maybe that security i have to control via the code i
n
asp.
Thanks in advanceTrapping the error in the application is the best way.
Jason Massie
Web: http://statisticsio.com
RSS: http://feeds.feedburner.com/statisticsio
"Arturo J" <Arturo J@.discussions.microsoft.com> wrote in message
news:5B649D1E-2B9C-4293-A383-90F28FD1D8A8@.microsoft.com...
> Hello everyone, i like to know if someone knows how to denied errors y SQL
> server 2000, i have many webs over a single server and i do not want to
> show
> errors in explorer when a bad user writes false urls intentionally trying
> to
> inject code via sql. Or maybe that security i have to control via the code
> in
> asp.
> Thanks in advance
>|||Thanks for your qick repond, just one doubt, you mean to manage the error
reports through the asp?
"Jason Massie" wrote:
> Trapping the error in the application is the best way.
> --
> Jason Massie
> Web: http://statisticsio.com
> RSS: http://feeds.feedburner.com/statisticsio
> "Arturo J" <Arturo J@.discussions.microsoft.com> wrote in message
> news:5B649D1E-2B9C-4293-A383-90F28FD1D8A8@.microsoft.com...
>
>
Wednesday, February 15, 2012
Error: SQL Server does not exist or access denied. (Error code 17).
Hello everyone.
I am trying to install Project Server, and i'm having issues with sharepoint, and connecting to SQL:
dataserver is running sbs2003 sql2003 and analsys services.
server2 is running server2003 is to be the application server for project.
ProjectDb is the database that i have setup in sql.
username is the account that can control everything as administrer.
in Sharepoint is asks for the database server: <<dataserver>>
SQL Server database name: <<ProjectDb>>
I'm using windoes authentication and then i click ok, and get the error message.
I've also see the error message can not find the SQL Server, and access denied. Under ODBC i have installed the sql server information under System DSN.
Any help would be great.
Thanks
Everett Buel
Start by confirming that SQL Server is running and that you can access it directly. I take it this is SQL Server 2000, so you should have Query Analyzer installed and you can use it to try to connect to your database. Also (more basic) check to confirm that the SQL Server service is started.|||SQL is running I have the Query Analyzer installed. All services are started. I can access the Sql Server from my desktop so i know that part is working.
But when I try to start up the data connection of the sharepoint services on the server running server 2003 i still get the error message.
Data services are all running on both servers.
Thanks for your reply
Everett Buel
|||It would be nice if you two finished this thread. I can't tell you how many times I've gone searching the MS web site for resolution of error messages only to find this type of non-solution. If this is all you can do then why don't you delete the useless thread.
Bryce
Error: SQL Server does not exist or access denied. (Error code 17).
Hello everyone.
I am trying to install Project Server, and i'm having issues with sharepoint, and connecting to SQL:
dataserver is running sbs2003 sql2003 and analsys services.
server2 is running server2003 is to be the application server for project.
ProjectDb is the database that i have setup in sql.
username is the account that can control everything as administrer.
in Sharepoint is asks for the database server: <<dataserver>>
SQL Server database name: <<ProjectDb>>
I'm using windoes authentication and then i click ok, and get the error message.
I've also see the error message can not find the SQL Server, and access denied. Under ODBC i have installed the sql server information under System DSN.
Any help would be great.
Thanks
Everett Buel
Start by confirming that SQL Server is running and that you can access it directly. I take it this is SQL Server 2000, so you should have Query Analyzer installed and you can use it to try to connect to your database. Also (more basic) check to confirm that the SQL Server service is started.|||SQL is running I have the Query Analyzer installed. All services are started. I can access the Sql Server from my desktop so i know that part is working.
But when I try to start up the data connection of the sharepoint services on the server running server 2003 i still get the error message.
Data services are all running on both servers.
Thanks for your reply
Everett Buel
|||
It would be nice if you two finished this thread. I can't tell you how many times I've gone searching the MS web site for resolution of error messages only to find this type of non-solution. If this is all you can do then why don't you delete the useless thread.
Bryce
Error: Server doesnot exist or Access denied
trying to connect to their individual databases using SQL webadmin or
Enterprise manager tool and they get the following message:
"SQL server doesnot exist or access denied.
ConnectionOpen(Connect())"
This is the message from SQL enterprise manager. The workstation is XP SP1.
Any suggestions>> Any suggestions
Oh the usual:
1. Check to make sure that they are using the right username/password
combination.
2. Make sure the client is not behind a firewall that prevents comm
over the SQL Server port.
3. Make sure the same applies for the server.
4. Make sure that they are using the right authentication type (sql or
win).
5. Make sure that the server is configured to use the right auth mode.
6. Make sure that the server's host name appears in the list of
available server to connect to (see 2 & 3).
HTH
AM|||Actually we found out that the SQL is not listening on any TCP/IP port but
only listening to named pipes. Any idea of how to make SQL Server listen to
any tcp/ip ports?
"AM" wrote:
> Oh the usual:
> 1. Check to make sure that they are using the right username/password
> combination.
> 2. Make sure the client is not behind a firewall that prevents comm
> over the SQL Server port.
> 3. Make sure the same applies for the server.
> 4. Make sure that they are using the right authentication type (sql or
> win).
> 5. Make sure that the server is configured to use the right auth mode.
> 6. Make sure that the server's host name appears in the list of
> available server to connect to (see 2 & 3).
> HTH
> AM
>|||In Enterprise Manager, right click on the DB, select properties. In
ther dialog box, int he General tab, on the bottom click on Network
configuration. In the dialog box that pops up, in the general tab,
check to see if TCP/IP is listed on the box on the right. If not select
it from the box on the left and click on enable. YOu can edit the
properties to set up the port to listen on.
HTH
AM|||You can use Server Network Utility to set the tcp port for the sql instance.
-oj
"Snehal Rana" <SnehalRana@.discussions.microsoft.com> wrote in message
news:E263310C-BB72-483D-BE16-DA854F38CB40@.microsoft.com...[vbcol=seagreen]
> Actually we found out that the SQL is not listening on any TCP/IP port but
> only listening to named pipes. Any idea of how to make SQL Server listen
> to
> any tcp/ip ports?
>
> "AM" wrote:
>
Error: Server doesnot exist or Access denied
trying to connect to their individual databases using SQL webadmin or
Enterprise manager tool and they get the following message:
"SQL server doesnot exist or access denied.
ConnectionOpen(Connect())"
This is the message from SQL enterprise manager. The workstation is XP SP1.
Any suggestions>> Any suggestions
Oh the usual:
1. Check to make sure that they are using the right username/password
combination.
2. Make sure the client is not behind a firewall that prevents comm
over the SQL Server port.
3. Make sure the same applies for the server.
4. Make sure that they are using the right authentication type (sql or
win).
5. Make sure that the server is configured to use the right auth mode.
6. Make sure that the server's host name appears in the list of
available server to connect to (see 2 & 3).
HTH
AM|||Actually we found out that the SQL is not listening on any TCP/IP port but
only listening to named pipes. Any idea of how to make SQL Server listen to
any tcp/ip ports?
"AM" wrote:
> >> Any suggestions
> Oh the usual:
> 1. Check to make sure that they are using the right username/password
> combination.
> 2. Make sure the client is not behind a firewall that prevents comm
> over the SQL Server port.
> 3. Make sure the same applies for the server.
> 4. Make sure that they are using the right authentication type (sql or
> win).
> 5. Make sure that the server is configured to use the right auth mode.
> 6. Make sure that the server's host name appears in the list of
> available server to connect to (see 2 & 3).
> HTH
> AM
>|||In Enterprise Manager, right click on the DB, select properties. In
ther dialog box, int he General tab, on the bottom click on Network
configuration. In the dialog box that pops up, in the general tab,
check to see if TCP/IP is listed on the box on the right. If not select
it from the box on the left and click on enable. YOu can edit the
properties to set up the port to listen on.
HTH
AM|||You can use Server Network Utility to set the tcp port for the sql instance.
--
-oj
"Snehal Rana" <SnehalRana@.discussions.microsoft.com> wrote in message
news:E263310C-BB72-483D-BE16-DA854F38CB40@.microsoft.com...
> Actually we found out that the SQL is not listening on any TCP/IP port but
> only listening to named pipes. Any idea of how to make SQL Server listen
> to
> any tcp/ip ports?
>
> "AM" wrote:
>> >> Any suggestions
>> Oh the usual:
>> 1. Check to make sure that they are using the right username/password
>> combination.
>> 2. Make sure the client is not behind a firewall that prevents comm
>> over the SQL Server port.
>> 3. Make sure the same applies for the server.
>> 4. Make sure that they are using the right authentication type (sql or
>> win).
>> 5. Make sure that the server is configured to use the right auth mode.
>> 6. Make sure that the server's host name appears in the list of
>> available server to connect to (see 2 & 3).
>> HTH
>> AM
>>
Error: Server doesnot exist or Access denied
trying to connect to their individual databases using SQL webadmin or
Enterprise manager tool and they get the following message:
"SQL server doesnot exist or access denied.
ConnectionOpen(Connect())"
This is the message from SQL enterprise manager. The workstation is XP SP1.
Any suggestions
>> Any suggestions
Oh the usual:
1. Check to make sure that they are using the right username/password
combination.
2. Make sure the client is not behind a firewall that prevents comm
over the SQL Server port.
3. Make sure the same applies for the server.
4. Make sure that they are using the right authentication type (sql or
win).
5. Make sure that the server is configured to use the right auth mode.
6. Make sure that the server's host name appears in the list of
available server to connect to (see 2 & 3).
HTH
AM
|||Actually we found out that the SQL is not listening on any TCP/IP port but
only listening to named pipes. Any idea of how to make SQL Server listen to
any tcp/ip ports?
"AM" wrote:
> Oh the usual:
> 1. Check to make sure that they are using the right username/password
> combination.
> 2. Make sure the client is not behind a firewall that prevents comm
> over the SQL Server port.
> 3. Make sure the same applies for the server.
> 4. Make sure that they are using the right authentication type (sql or
> win).
> 5. Make sure that the server is configured to use the right auth mode.
> 6. Make sure that the server's host name appears in the list of
> available server to connect to (see 2 & 3).
> HTH
> AM
>
|||In Enterprise Manager, right click on the DB, select properties. In
ther dialog box, int he General tab, on the bottom click on Network
configuration. In the dialog box that pops up, in the general tab,
check to see if TCP/IP is listed on the box on the right. If not select
it from the box on the left and click on enable. YOu can edit the
properties to set up the port to listen on.
HTH
AM
|||You can use Server Network Utility to set the tcp port for the sql instance.
-oj
"Snehal Rana" <SnehalRana@.discussions.microsoft.com> wrote in message
news:E263310C-BB72-483D-BE16-DA854F38CB40@.microsoft.com...[vbcol=seagreen]
> Actually we found out that the SQL is not listening on any TCP/IP port but
> only listening to named pipes. Any idea of how to make SQL Server listen
> to
> any tcp/ip ports?
>
> "AM" wrote: