Thursday, March 22, 2012
Couldn't connect to my server from client
server 2000 SP4 on a Windows 2003 server. Is there any method that I can get
to see if I don't miss something when I have made the installation on the
server part ?
Every help will be welcome
Regards,
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...curity/200609/1I dont believe that SQL server keeps track of that type of information
unless you have C2 auditing enabled. You could also pick that up in a trace
file had you been tracing.
http://www.microsoft.com/technet/pr...tain/sqlc2.mspx
I could be wrong though. Does anyone else have any information?
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Silver via droptable.com" <u26873@.uwe> wrote in message
news:669141b5c2b48@.uwe...
>I have a communication error from my client when I try to connect to my SQL
> server 2000 SP4 on a Windows 2003 server. Is there any method that I can
> get
> to see if I don't miss something when I have made the installation on the
> server part ?
> Every help will be welcome
> Regards,
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...curity/200609/1
>sql
Couldn't connect server
When I try to connect SQL 2000 Enterprise client with SQL
Server 2000 Enterprise Server , the following error
message displayed.
Unable to connect to server
Server:Msg 17,Level 16,State 1
Microsoft ODBC SQL Server Driver TCP/IP Sockets SQL
Server does not exist or access denied
How can i solve this problem?
Database Server configuration:
Windows Server 2003 with SQL Server 2000 Enterprise
Edition
Advance thankx
Sankar.First, verify you can make a network connection like a mapped drive to the
server.
Second, open Client Network Utility on your workstation, Server Network
Utility on the server (both programs are in the SQL Program group) and
verify you are both listening on the same protocols in the same order.
Lastly, you should verify MSSQLServer service is running on the server and
that there are no firewalls in between your computers which might be
blocking ports.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Sankar" <anonymous@.discussions.microsoft.com> wrote in message
news:04c801c3d8ea$36ab78e0$a301280a@.phx.gbl...
quote:|||Also, since you are attempting a TCP?IP connection verify that you can ping
> Hi to all,
> When I try to connect SQL 2000 Enterprise client with SQL
> Server 2000 Enterprise Server , the following error
> message displayed.
>
> Unable to connect to server
> Server:Msg 17,Level 16,State 1
> Microsoft ODBC SQL Server Driver TCP/IP Sockets SQL
> Server does not exist or access denied
> How can i solve this problem?
> Database Server configuration:
> Windows Server 2003 with SQL Server 2000 Enterprise
> Edition
>
> Advance thankx
> Sankar.
the SQL Server machine by name. If not, try specifying the SQL Server
machine name ip address as the server name when attempting to connect. If
the first fails but the second succeeds then there is a name resplution
problem. If the second fails as well then there could be a network related
problem that is preventing the client from accessing the SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||> the SQL Server machine by name. If not, try specifying the SQL Server
quote:
> machine name ip address as the server name when attempting to connect. If
> the first fails but the second succeeds then there is a name resplution
> problem. If the second fails as well then there could be a network related
> problem that is preventing the client from accessing the SQL Server.
I have the same problem but I can ping the machine.
Mike Collier BSc( Hons) Comp Sci
Get a copy of AdoAnywhere Browser FREE if you register for the forum
quickly...
http://www.adoanywhere.com/forum
"Rand Boyd [MS]" <rboyd@.onlinemicrosoft.com> wrote in message
news:h0mDbBU2DHA.2184@.cpmsftngxa07.phx.gbl...
quote:
> Also, since you are attempting a TCP?IP connection verify that you can
ping
quote:|||Work through this article:
> the SQL Server machine by name. If not, try specifying the SQL Server
> machine name ip address as the server name when attempting to connect. If
> the first fails but the second succeeds then there is a name resplution
> problem. If the second fails as well then there could be a network related
> problem that is preventing the client from accessing the SQL Server.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
328306 INF: Potential Causes of the ("SQL Server Does Not Exist or Access
http://support.microsoft.com/?id=328306
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Monday, March 19, 2012
'Could not open FCB for invalid file ID % in database %'
I am having some problems with my server. Installed is sql
server 7 and i have recently been getting the above error
message. I was advised to run the patch sql70sp4.exe and i
would be doing that tonight. Would this solve the problem.
Has anyone gone through this before ?
Any help appreciated.
Thanks
Chris Kentebe
ckentebe@.yahoo.ca
Hello Christopher
This message could be caused due to lot of reasons. I would advise you to
open a case with PSS to work on this in more detail.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
'Could not open FCB for invalid file ID % in database %'
I am having some problems with my server. Installed is sql
server 7 and i have recently been getting the above error
message. I was advised to run the patch sql70sp4.exe and i
would be doing that tonight. Would this solve the problem.
Has anyone gone through this before ?
Any help appreciated.
Thanks
Chris Kentebe
ckentebe@.yahoo.caHello Christopher
This message could be caused due to lot of reasons. I would advise you to
open a case with PSS to work on this in more detail.
Thank you for using Microsoft newsgroups.
Sincerely
Pankaj Agarwal
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Sunday, March 11, 2012
Could not load file or assembly 'Microsoft.SqlServer.Express.Reports, ....
freshly installed SSMSE and upon opening get the following error...
Could not load file or assembly 'Microsoft.SqlServer.Express.Reports, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)
Any ideas how to get past it?
This is really odd. Could you try the following...
1) Uninstall everything you have right now
2) Download the latest version directly from Microsoft
3) Install the latest version
Paul A. Mestemaker II
Program Manager
Microsoft SQL Server
http://blogs.msdn.com/sqlrem/
Sunday, February 19, 2012
Could install two Instance in a SQL Server
Could we install another Instance in the some Sqlserver.
For instance, I add Instance2 to the SqlServer?Sure. See:
http://msdn2.microsoft.com/en-us/library/ms143531.aspx
HTH
Jerry
"ad" <flying@.wfes.tcc.edu.tw> wrote in message
news:eTsboMseGHA.4948@.TK2MSFTNGP04.phx.gbl...
>I have install Sql2005 in my Server, and it use the default instance.
> Could we install another Instance in the some Sqlserver.
> For instance, I add Instance2 to the SqlServer?
>
Could install two Instance in a SQL Server
Could we install another Instance in the some Sqlserver.
For instance, I add Instance2 to the SqlServer?Sure. See:
http://msdn2.microsoft.com/en-us/library/ms143531.aspx
HTH
Jerry
"ad" <flying@.wfes.tcc.edu.tw> wrote in message
news:eTsboMseGHA.4948@.TK2MSFTNGP04.phx.gbl...
>I have install Sql2005 in my Server, and it use the default instance.
> Could we install another Instance in the some Sqlserver.
> For instance, I add Instance2 to the SqlServer?
>
Friday, February 17, 2012
Could a datatype of a column be like integer array?
I need a column in my table that its DataType should be as integer arrays how can I implemant it in my sqlserver table.
Any help appreciated.is it possible at all?I dont want to make another table.
Thanks|||Unfortunately, there are no array data types in SQL Server. If you provide more information we might be able to make suggestions.
Terri|||Thank you Terri for the reply
>>there are no array data types in SQL Server , I got my answer,I will make another table|||you could always create a user defined function that splits a comma delimited string into a @.table or something.|||If the OP provided more info I was going to suggest one of the approaches listed here:How to pass a list of values or array to SQL Server stored procedure?. That blog entry pretty nicely sums up all of the discussions we've had ad nauseum on this topic :-)
Terri
Tuesday, February 14, 2012
Corrupted view
price and some other infos of invoice items. everything worked fine.
Now, the view didn't return the same as when I created it. The price
column of the returned record set showed the invoice date instead of the
price and some other columns also contained wrong information.
After recreating the view everything was fine again.
How can this happen?
Cheers
FerdinandFerdinand,
Did someone change the underlying table definitions? If so, run
sp_refreshview 'viewname' to get the view resynchronized with the underlying
tables.
RLF
"Ferdinand Zaubzer" <ferdinand.zaubzer@.schendl.at> wrote in message
news:OkORyxYuHHA.4540@.TK2MSFTNGP05.phx.gbl...
> Some days ago I created a view on a sqlserver database, that returns the
> price and some other infos of invoice items. everything worked fine.
> Now, the view didn't return the same as when I created it. The price
> column of the returned record set showed the invoice date instead of the
> price and some other columns also contained wrong information.
> After recreating the view everything was fine again.
> How can this happen?
> Cheers
> Ferdinand|||The explanation was given by Russell.
I strongly suggest you remove any * from the selection list in the
view's definition. Apart from the side effects in the view when adding
columns to the specific table, it is considered a bad practice to use
SELECT * in views in production code.
Gert-Jan
Ferdinand Zaubzer wrote:
> Some days ago I created a view on a sqlserver database, that returns the
> price and some other infos of invoice items. everything worked fine.
> Now, the view didn't return the same as when I created it. The price
> column of the returned record set showed the invoice date instead of the
> price and some other columns also contained wrong information.
> After recreating the view everything was fine again.
> How can this happen?
> Cheers
> Ferdinand
Corrupted view
price and some other infos of invoice items. everything worked fine.
Now, the view didn't return the same as when I created it. The price
column of the returned record set showed the invoice date instead of the
price and some other columns also contained wrong information.
After recreating the view everything was fine again.
How can this happen?
Cheers
Ferdinand
Ferdinand,
Did someone change the underlying table definitions? If so, run
sp_refreshview 'viewname' to get the view resynchronized with the underlying
tables.
RLF
"Ferdinand Zaubzer" <ferdinand.zaubzer@.schendl.at> wrote in message
news:OkORyxYuHHA.4540@.TK2MSFTNGP05.phx.gbl...
> Some days ago I created a view on a sqlserver database, that returns the
> price and some other infos of invoice items. everything worked fine.
> Now, the view didn't return the same as when I created it. The price
> column of the returned record set showed the invoice date instead of the
> price and some other columns also contained wrong information.
> After recreating the view everything was fine again.
> How can this happen?
> Cheers
> Ferdinand
|||The explanation was given by Russell.
I strongly suggest you remove any * from the selection list in the
view's definition. Apart from the side effects in the view when adding
columns to the specific table, it is considered a bad practice to use
SELECT * in views in production code.
Gert-Jan
Ferdinand Zaubzer wrote:
> Some days ago I created a view on a sqlserver database, that returns the
> price and some other infos of invoice items. everything worked fine.
> Now, the view didn't return the same as when I created it. The price
> column of the returned record set showed the invoice date instead of the
> price and some other columns also contained wrong information.
> After recreating the view everything was fine again.
> How can this happen?
> Cheers
> Ferdinand
Corrupted view
price and some other infos of invoice items. everything worked fine.
Now, the view didn't return the same as when I created it. The price
column of the returned record set showed the invoice date instead of the
price and some other columns also contained wrong information.
After recreating the view everything was fine again.
How can this happen?
Cheers
FerdinandFerdinand,
Did someone change the underlying table definitions? If so, run
sp_refreshview 'viewname' to get the view resynchronized with the underlying
tables.
RLF
"Ferdinand Zaubzer" <ferdinand.zaubzer@.schendl.at> wrote in message
news:OkORyxYuHHA.4540@.TK2MSFTNGP05.phx.gbl...
> Some days ago I created a view on a sqlserver database, that returns the
> price and some other infos of invoice items. everything worked fine.
> Now, the view didn't return the same as when I created it. The price
> column of the returned record set showed the invoice date instead of the
> price and some other columns also contained wrong information.
> After recreating the view everything was fine again.
> How can this happen?
> Cheers
> Ferdinand|||The explanation was given by Russell.
I strongly suggest you remove any * from the selection list in the
view's definition. Apart from the side effects in the view when adding
columns to the specific table, it is considered a bad practice to use
SELECT * in views in production code.
Gert-Jan
Ferdinand Zaubzer wrote:
> Some days ago I created a view on a sqlserver database, that returns the
> price and some other infos of invoice items. everything worked fine.
> Now, the view didn't return the same as when I created it. The price
> column of the returned record set showed the invoice date instead of the
> price and some other columns also contained wrong information.
> After recreating the view everything was fine again.
> How can this happen?
> Cheers
> Ferdinand