Cannot register 6.5 server

Hi,
I'm using my computer (Windows XP Professional) to
administrate remote sql servers 6.5, 7.0, and 2000. I can
successfully register all servers except one, sql server
6.5. Difference between this one and the other 6.5
servers is that it uses Named Pipes server library, and
the other ones use TCP/IP. I created an alias for this
specific server (with named pipes), but still, I get an
error message: "A connection could not be established to
<server name>. [DB Library] Unable to connect: SQL Server
is unavailable or does not exist."
At the same time I can ping the server... I can also
register this server from the other, Windows 2000 PC...
Any ideas?
Thanks,
BakiCan you map a drive to the \\<SQL Server Machine>\IPC$ share from the
WIndows XP machine. Named pipes requires a trusted connection and you may
not be able to establish that from the XP machine. If you cannot map a
drive then you will not be able to use named pipes. You may have to switch
to TCP/IP
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Hi,
Are you saying that I cannot connect to this server using
Named Pipes if I'm not logged on to the same domain as
sql server is?
Thanks,
Baki

quote:

---

>--Original Message--
>Can you map a drive to the \\<SQL Server Machine>\IPC$

---

share from the

quote:

---

>WIndows XP machine. Named pipes requires a trusted

---

connection and you may

quote:

---

>not be able to establish that from the XP machine. If

---

you cannot map a

quote:

---

>drive then you will not be able to use named pipes. You

---

may have to switch

quote:

---

>to TCP/IP
>Rand
>This posting is provided "as is" with no warranties and

---

confers no rights.

quote:

---

>.
>

---

|||You have to access to the machine at the OS level. Named pipes requries
that you have access to the machine. You do not have to be in the same
domain, but there does need to be some type of trust to use named pipes. If
your NT account has an account on the SQL Server machine you should be able
to use named pipes.
Either way named pipes requires a trust. This is documented in Books on
Line.
Rand
Thsi posting is proved "AS IS" with no warranties, and confers no rights.

Cannot Open / Create SQL Express Databases (.mdf files) in Visual Studio 2005 Professional

Hi, I am trying to open or create a sqlexpress database within Visual Studio 2005 Professional in the App_Data folder. If I attempt either method, I get the following dialog box:

Required Components Missing

Connections to SQL Server files (*.mdf) require SQL Server Express 2005 to function properly. Please verify the installation of the component or download from the URL: http://go.microsoft.com/fwlink/?LinkID=49251

The link above just takes you to the download page for Sql Server Express 2005.

I have both SQL Server 2005 Developer and SQL Server 2005 Expression instances running. The existing database will work properly in my web application, however I cannot access it through Visual Studio.

As background, I did have a problem connecting to the database via the web application, receiving a "Failed to generate a User Instance of SQL Server" error. But I was able to fix that by renaming my SQLEXPRESS folder in C:\Documents and Settings\user\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data. When the web page ran, it created another SQLEXPRESS folder.

However, I cannot figure out why I am having the other issue.

Thanks in advance

Patrick

Hi,

This error means that you are not pointing to the correct instance.

Right click the mdf database > Modify Connection > Advanced > Data Source string.

Check this string and see if it points to the correct instance

HTH,
Suprotim Agarwal

--
http://www.dotnetcurry.com
--

Cannot Install SQL2005 developer on Windows XP with Office 2007 pr

Have a new computer with Windows XP SP2 and all updates and Office 2007
professional.
When I try and install SQL2005 developer get an error 1706: Setup cannot
find the required file c:/program files/Microsoft Office11/1033/setup.chm
Any assistance is appreciated.
GavinHi Gavin,
This is actually a known bug and Microsoft is aware of it. Until a fix
is released you need to workaround it by uninstalling Microsoft Office
2003 Web Components from the Add/Remove Software control panel and then
re-run the SQL Server setup.
Hope this helps!
Jonathan
gavin wrote:
> Have a new computer with Windows XP SP2 and all updates and Office 2007
> professional.
> When I try and install SQL2005 developer get an error 1706: Setup cannot
> find the required file c:/program files/Microsoft Office11/1033/setup.chm
> Any assistance is appreciated.
> Gavin|||On Aug 2, 10:17 am, Jonathan Psaila-Depasquale
<nos...@.nospamplease.com> wrote:
> Hi Gavin,
> This is actually a known bug and Microsoft is aware of it. Until a fix
> is released you need to workaround it by uninstalling Microsoft Office
> 2003 Web Components from the Add/Remove Software control panel and then
> re-run the SQL Server setup.
> Hope this helps!
> Jonathan
>
> gavin wrote:
> > Have a new computer with Windows XP SP2 and all updates and Office 2007
> > professional.
> > When I try and install SQL2005 developer get an error 1706: Setup cannot
> > find the required file c:/program files/Microsoft Office11/1033/setup.chm
> > Any assistance is appreciated.
> > Gavin- Hide quoted text -
> - Show quoted text -
Interesting. I was curious to what it was looking in the Office11
folder, as I believe Office 2007 falls withing the Office12 arena. I
have the same setup (no Office Web Components) and had no issues
installing the SQL 2005 developer edition.

Cannot install SP1 x86 - Windows XP Professional

Hi, I am trying to install SP1 on a Windows XP Professional - Version 2002 SP2.

but i got an Error, this is the error log :

(File : Redist9_Hotfix_KB913090.log )

-

05/18/2006 16:59:31.835 ================================================================================
05/18/2006 16:59:31.866 Hotfix package launched
05/18/2006 17:01:07.616 Attempting to install instance: SQL Server Native Client
05/18/2006 17:01:07.631 Attempting to install target: GDSA3367
05/18/2006 17:01:07.678 Attempting to install file: sqlncli.msi
05/18/2006 17:01:07.881 Attempting to install file: \\GDSA3367\c$\33b3e8d8202a1514eb8d3dbc\HotFixSqlncli\Files\sqlncli.msi
05/18/2006 17:01:07.928 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
05/18/2006 17:01:07.959 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/18/2006 17:01:07.991 Failed to read registry key: Debug
05/18/2006 17:01:11.381 MSP returned 0: The action completed successfully.
05/18/2006 17:01:11.444 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/18/2006 17:01:11.475 Failed to read registry key: Debug
05/18/2006 17:01:11.491 Successfully installed file: \\GDSA3367\c$\33b3e8d8202a1514eb8d3dbc\HotFixSqlncli\Files\sqlncli.msi
05/18/2006 17:01:11.522 Successfully installed target: GDSA3367
05/18/2006 17:01:11.553 Successfully installed instance: SQL Server Native Client
05/18/2006 17:01:11.584
05/18/2006 17:01:11.600 Product Status Summary:
05/18/2006 17:01:11.631 Product: SQL Server Native Client
05/18/2006 17:01:11.662 SQL Server Native Client (RTM ) - Success
05/18/2006 17:01:11.694
05/18/2006 17:01:11.709 Product: Setup Support Files
05/18/2006 17:01:11.741 Setup Support Files (RTM ) - Not Applied
05/18/2006 17:01:11.756
05/18/2006 17:01:11.834 Product: Database Services
05/18/2006 17:01:11.928 Database Services (RTM 1399 ENU) - Not Applied
05/18/2006 17:01:11.975
05/18/2006 17:01:11.991 Product: Client Components
05/18/2006 17:01:12.022 Client Components (SP1 2047 ENU) - Not Applied
05/18/2006 17:01:12.053
05/18/2006 17:01:12.069 Product: MSXML 6.0 Parser
05/18/2006 17:01:12.116 MSXML 6.0 Parser (RTM ) - Not Applied
05/18/2006 17:01:12.147
05/18/2006 17:01:12.162 Product: SQLXML4
05/18/2006 17:01:12.194 SQLXML4 (RTM ) - Not Applied
05/18/2006 17:01:12.225
05/18/2006 17:01:12.272 Product: Backward Compatibility
05/18/2006 17:01:12.303 Backward Compatibility (RTM ) - Not Applied
05/18/2006 17:01:12.381
05/18/2006 17:01:12.412 Product: Microsoft SQL Server VSS Writer
05/18/2006 17:01:12.428 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/18/2006 17:01:12.459
-<EOF>

...and this is the Error Report sends this info:

EventType : sqlsesetup P1 : sql9 P2 : 9 P3 : x86 P4 : null
P5 : null P6 : kb913090
P7 : _depot_sqlvault_setupmain_setup_sqlse_sqlsedll_copyengine.cpp - 856
P8 : null

Files:
C:\WINDOWS\Hotfix\HotFix.log
C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090.log
C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090.log
C:\WINDOWS\Hotfix\OLAP9\Logs\OLAP9_Hotfix_KB913090.log
C:\WINDOWS\Hotfix\NS9\Logs\NS9_Hotfix_KB913090.log
C:\WINDOWS\Hotfix\RS9\Logs\RS9_Hotfix_KB913090.log
C:\WINDOWS\Hotfix\DTS9\Logs\DTS9_Hotfix_KB913090.log
C:\WINDOWS\Hotfix\SQLTools9\Logs\SQLTools9_Hotfix_KB913090.log
C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_SqlSupport.msp.log
C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090_sqlrun_sql.msp.log
C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090_sqlrun_sql.msp.out

-

My Version of SQL is - Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2) .

Thanks.

Cristian Bianchi

I don't see anything interesting there. Can you look in the log files here:

%Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files

|||

Paul:

In the folder " %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files" there in not files dated when i made the instalation of the SP1. But i found in the log C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090_sqlrun_sql.msp.log , the next line :

MSI (s) (FC:F0) [17:21:26:030]: Product: Microsoft SQL Server 2005 - Update 'Service Pack 1 for SQL Server Database Services 2005 ENU (KB913090)' could not be installed. Error code 1603. Additional information is available in the log file C:\WINDOWS\Hotfix\SQL9\Logs\SQL9_Hotfix_KB913090_sqlrun_sql.msp.log.

Thanks in advance.

Crsitan F. Bianchi

|||1603 is just "Fatal error during installation." The lines above that in the log should reveal something about the cause of the error.

'cannot generate sspi context'

Hello,
a client of me has upgraded its win2000 professional to Windows Xp. When
he first tries to connect to sql2000 all is well, but after +/- 20 minutes
he get the error 'cannot generate sspi context' when trying to connect to
the sql server again.
Any suggestions
MarcTry this - http://support.microsoft.com/default.aspx?scid=kb;en-us;811889
--
Ray Higdon MCSE, MCDBA, CCNA
--
"news.microsoft.com" <marc.mertens@.azlan.com> wrote in message
news:Ozkvisz3DHA.1404@.TK2MSFTNGP11.phx.gbl...
> Hello,
> a client of me has upgraded its win2000 professional to Windows Xp.
When
> he first tries to connect to sql2000 all is well, but after +/- 20 minutes
> he get the error 'cannot generate sspi context' when trying to connect to
> the sql server again.
> Any suggestions
> Marc
>

'cannot generate sspi context'

Hello,
a client of me has upgraded its win2000 professional to Windows Xp. When
he first tries to connect to sql2000 all is well, but after +/- 20 minutes
he get the error 'cannot generate sspi context' when trying to connect to
the sql server again.
Any suggestions
MarcTry this - http://support.microsoft.com/defaul...kb;en-us;811889
Ray Higdon MCSE, MCDBA, CCNA
--
"news.microsoft.com" <marc.mertens@.azlan.com> wrote in message
news:Ozkvisz3DHA.1404@.TK2MSFTNGP11.phx.gbl...

quote:

---

> Hello,
> a client of me has upgraded its win2000 professional to Windows Xp.

---

When

quote:

---

> he first tries to connect to sql2000 all is well, but after +/- 20 minutes
> he get the error 'cannot generate sspi context' when trying to connect to
> the sql server again.
> Any suggestions
> Marc
>

---