Showing posts with label setup. Show all posts
Showing posts with label setup. Show all posts

Thursday, March 29, 2012

Can't Switch to SQL Authentication (Mixed Mode)

We have a SQL installation that was setup with Windows Authentication.
The software we will run requires SQL Authentication (Mixed Mode).
When I right click on properties, go to the security tab, click the SQL
Authentication, click on OK and it exits. However, when I go back in
and look at the security tab, it is still set on Windows
Authentication. I tried restarting the SQL services and I get the same
thing.
Ideas?
I have resolved this issue by logging in as the domain admin. I had
previously tried using a local admin account.
jd
JohnDoe wrote:
> We have a SQL installation that was setup with Windows Authentication.
> The software we will run requires SQL Authentication (Mixed Mode).
> When I right click on properties, go to the security tab, click the SQL
> Authentication, click on OK and it exits. However, when I go back in
> and look at the security tab, it is still set on Windows
> Authentication. I tried restarting the SQL services and I get the same
> thing.
> Ideas?

Can't Switch to SQL Authentication (Mixed Mode)

We have a SQL installation that was setup with Windows Authentication.
The software we will run requires SQL Authentication (Mixed Mode).
When I right click on properties, go to the security tab, click the SQL
Authentication, click on OK and it exits. However, when I go back in
and look at the security tab, it is still set on Windows
Authentication. I tried restarting the SQL services and I get the same
thing.
Ideas?I have resolved this issue by logging in as the domain admin. I had
previously tried using a local admin account.
jd
JohnDoe wrote:
> We have a SQL installation that was setup with Windows Authentication.
> The software we will run requires SQL Authentication (Mixed Mode).
> When I right click on properties, go to the security tab, click the SQL
> Authentication, click on OK and it exits. However, when I go back in
> and look at the security tab, it is still set on Windows
> Authentication. I tried restarting the SQL services and I get the same
> thing.
> Ideas?

Can't Switch to SQL Authentication (Mixed Mode)

We have a SQL installation that was setup with Windows Authentication.
The software we will run requires SQL Authentication (Mixed Mode).
When I right click on properties, go to the security tab, click the SQL
Authentication, click on OK and it exits. However, when I go back in
and look at the security tab, it is still set on Windows
Authentication. I tried restarting the SQL services and I get the same
thing.
Ideas?I have resolved this issue by logging in as the domain admin. I had
previously tried using a local admin account.
jd
JohnDoe wrote:
> We have a SQL installation that was setup with Windows Authentication.
> The software we will run requires SQL Authentication (Mixed Mode).
> When I right click on properties, go to the security tab, click the SQL
> Authentication, click on OK and it exits. However, when I go back in
> and look at the security tab, it is still set on Windows
> Authentication. I tried restarting the SQL services and I get the same
> thing.
> Ideas?

Sunday, March 25, 2012

Can't setup SQL AgentMail

Dear all:
I've setup Outlook 2003 for my MAPI client, and setup service that not run
the local machine. And my SQL Mail can work. However, the profile in SQL
AgentMail still can't setup. How should I setup the SQL Agent Mail?Sorry that forgot post my environment:
Win2003 + AD
SQL 2000 + sp3a
Exchange 2003
Outlook 2003
Thank you very much for your reply!
"David" <david@.ms59.ideanote.org.NOSPAM> glsD
:uKhVx5A5DHA.2556@.TK2MSFTNGP09.phx.gbl...
quote:

> Dear all:
> I've setup Outlook 2003 for my MAPI client, and setup service that not run
> the local machine. And my SQL Mail can work. However, the profile in SQL
> AgentMail still can't setup. How should I setup the SQL Agent Mail?
>
|||1.And make sure that SQL service account have permission to access the
Outlook profile's user account.
Try to use the Outlook user login to your SQL server, then create the
Outlook profile.
Then check again that SQL agentmail profile can setup or not.
2.Verify the MAPI32.dll version, you can see this to check your version.
http://support.microsoft.com/defaul...kb;en-us;263556
Microsoft MVP
Alvin Chen for Windows Server
MCP,MCSE,MCSA,MCSA+Messenger,RHCE,CCNA,T
CSE.
"David" <david@.ms59.ideanote.org.NOSPAM> glsD
:ORmhc4B5DHA.1936@.TK2MSFTNGP12.phx.gbl...
quote:

> Sorry that forgot post my environment:
> Win2003 + AD
> SQL 2000 + sp3a
> Exchange 2003
> Outlook 2003
> Thank you very much for your reply!
> "David" <david@.ms59.ideanote.org.NOSPAM> glsD
> :uKhVx5A5DHA.2556@.TK2MSFTNGP09.phx.gbl...
run[QUOTE]
>

Can't setup SQL AgentMail

Dear all:
I've setup Outlook 2003 for my MAPI client, and setup service that not run
the local machine. And my SQL Mail can work. However, the profile in SQL
AgentMail still can't setup. How should I setup the SQL Agent Mail?Sorry that forgot post my environment:
Win2003 + AD
SQL 2000 + sp3a
Exchange 2003
Outlook 2003
Thank you very much for your reply!
"David" <david@.ms59.ideanote.org.NOSPAM> ¼¶¼g©ó¶l¥ó·s»D
:uKhVx5A5DHA.2556@.TK2MSFTNGP09.phx.gbl...
> Dear all:
> I've setup Outlook 2003 for my MAPI client, and setup service that not run
> the local machine. And my SQL Mail can work. However, the profile in SQL
> AgentMail still can't setup. How should I setup the SQL Agent Mail?
>|||1.And make sure that SQL service account have permission to access the
Outlook profile's user account.
Try to use the Outlook user login to your SQL server, then create the
Outlook profile.
Then check again that SQL agentmail profile can setup or not.
2.Verify the MAPI32.dll version, you can see this to check your version.
http://support.microsoft.com/default.aspx?scid=kb;en-us;263556
Microsoft MVP
Alvin Chen for Windows Server
MCP,MCSE,MCSA,MCSA+Messenger,RHCE,CCNA,TCSE.
"David" <david@.ms59.ideanote.org.NOSPAM> ¼¶¼g©ó¶l¥ó·s»D
:ORmhc4B5DHA.1936@.TK2MSFTNGP12.phx.gbl...
> Sorry that forgot post my environment:
> Win2003 + AD
> SQL 2000 + sp3a
> Exchange 2003
> Outlook 2003
> Thank you very much for your reply!
> "David" <david@.ms59.ideanote.org.NOSPAM> ¼¶¼g©ó¶l¥ó·s»D
> :uKhVx5A5DHA.2556@.TK2MSFTNGP09.phx.gbl...
> > Dear all:
> >
> > I've setup Outlook 2003 for my MAPI client, and setup service that not
run
> > the local machine. And my SQL Mail can work. However, the profile in SQL
> > AgentMail still can't setup. How should I setup the SQL Agent Mail?
> >
> >
>

Can't setup replication: Encryption error using CryptProtectData?

I am trying to setup replication but am having the following issues
Publisher:
SQL 2005 SP1 Enterprise Cluster (Active, Passive)
Subscriber:
SQL 2005 SP1 Enterprise


When trying to create a publication or subsubscription running under a Windows Domain account the following error message appears:

Replication-Replication Distribution Subsystem: agent ECHO\ECHO-InsDB-INS_CMS_PUB-HARPO-58 failed. Unable to start execution of step 2 (reason: Error authenticating proxy DETINI\srvRep_user, system error: Logon failure: unknown user name or bad password.). The step failed.


Further in the SQL logs we find that the above message is due to:

[298] SQLServer Error: 22046, Encryption error using CryptProtectData. [SQLSTATE 42000]

It appears that when Credentials for the agent proxy are being created that this message occurs. So when the SP that tries to run the agent (snapshot or distrobution) is called it always returns incorrect password details.

The Credentials do appear to be created, they are visible via SQL Studio, but you can't see the password. Changing the password via SQL Studio does not work as the Credentials are recreated every time.


I have checked the following:

MSDTC is running correctly
The Domain Account has the correct privileges to run these services
Regenerated the Service Master Key
Created Master Keys in each database effected by replication
Ensure SQL Service accounts have access to decrypt the Service Master Key
I can create a Publication and Subscription using the local system account on the cluster

Does anyone have any idea ?

Chris

Chirs,

My testing environment is the same as yours - the publisher/distributer is clustered SQL2005 enterprise with SP1 on windows 2003, and the subscriber is SQL2005 enterprise on 2003 server, and I have got the same error when I was trying to run the creating snapshot job. The only workaround I found was to put the distributor on the same server as the publisher, and use a local directory for shapshot folder, which was not ideal, but at least I could continue with my test. Then I had the same error again when I ran the push distribution job using a domain ammount. I had to change the security to use SQL agent account, which is a domain admin account.

I would like to know how to avoid the error too, since I want the distributor to be on a different machine than the publisher, and limit the rights of the credentials on the production environments.

Ying

sql

Can't setup replication: Encryption error using CryptProtectData?

I am trying to setup replication but am having the following issues
Publisher:
SQL 2005 SP1 Enterprise Cluster (Active, Passive)
Subscriber:
SQL 2005 SP1 Enterprise


When trying to create a publication or subsubscription running under a Windows Domain account the following error message appears:

Replication-Replication Distribution Subsystem: agent ECHO\ECHO-InsDB-INS_CMS_PUB-HARPO-58 failed. Unable to start execution of step 2 (reason: Error authenticating proxy DETINI\srvRep_user, system error: Logon failure: unknown user name or bad password.). The step failed.


Further in the SQL logs we find that the above message is due to:

[298] SQLServer Error: 22046, Encryption error using CryptProtectData. [SQLSTATE 42000]

It appears that when Credentials for the agent proxy are being created that this message occurs. So when the SP that tries to run the agent (snapshot or distrobution) is called it always returns incorrect password details.

The Credentials do appear to be created, they are visible via SQL Studio, but you can't see the password. Changing the password via SQL Studio does not work as the Credentials are recreated every time.


I have checked the following:

MSDTC is running correctly
The Domain Account has the correct privileges to run these services
Regenerated the Service Master Key
Created Master Keys in each database effected by replication
Ensure SQL Service accounts have access to decrypt the Service Master Key
I can create a Publication and Subscription using the local system account on the cluster

Does anyone have any idea ?

Chris

Chirs,

My testing environment is the same as yours - the publisher/distributer is clustered SQL2005 enterprise with SP1 on windows 2003, and the subscriber is SQL2005 enterprise on 2003 server, and I have got the same error when I was trying to run the creating snapshot job. The only workaround I found was to put the distributor on the same server as the publisher, and use a local directory for shapshot folder, which was not ideal, but at least I could continue with my test. Then I had the same error again when I ran the push distribution job using a domain ammount. I had to change the security to use SQL agent account, which is a domain admin account.

I would like to know how to avoid the error too, since I want the distributor to be on a different machine than the publisher, and limit the rights of the credentials on the production environments.

Ying

Thursday, March 22, 2012

Can't setup replication

Initially, when I started to setup replication I received the error message ~
"one or more articles are published ...", so I issued the following commands
to remove replication settings from the DB:
sp_configure 'allow',1
GO
reconfigure with override
GO
USE ImageCraft
GO
sp_removedbreplication 'IMAGECRAFT'
GO
UPDATE sysobjects set replinfo=0 WHERE replinfo<>0
GO
Drop table MSdynamicsnapshotjobs
Drop table MSdynamicsnapshotviews
Drop table MSmerge_altsyncpartners
Drop table MSmerge_contents
Drop table MSmerge_delete_conflicts
Drop table MSmerge_errorlineage
Drop table MSmerge_genhistory
Drop table MSmerge_replinfo
Drop table MSmerge_tombstone
Drop table MSrepl_identity_range
Drop table sysmergearticles
Drop table sysmergepublications
Drop table sysmergeschemaarticles
Drop table sysmergeschemachange
Drop table sysmergesubscriptions
Drop table sysmergesubsetfilters
GO
sp_configure 'allow',0
GO
reconfigure with override
GO
Appearently, I overkilled it because I get an error message I've never seen
before when adding a table to the replication setup:
SQL Server Enterprise Manager could not initialize an article based on table
'BusinessUnit'.
Error 208: Invalid object name 'sysmergearticles'.
Invalid object name 'sysmergeschemaarticles'.
Invalid object name 'sysmergearticles'.
Invalid object name 'sysmergeschmaarticles'.
Could not use view or function 'sysmergeextendedarticlesview' because of
binding errors.
Could not use view or function 'sysmergeextendedarticlesview' because of
binding errors.
I did a restore on the I am trying to create the replication for, but still
get the same errors.
Any suggestions?
can you disable this database for merge publishing and then try to re-enable
it. Also what version of SQL are you running?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Steven" <Steven@.discussions.microsoft.com> wrote in message
news:1838D345-A23E-4CB6-A122-3736554334BE@.microsoft.com...
> Initially, when I started to setup replication I received the error
> message ~
> "one or more articles are published ...", so I issued the following
> commands
> to remove replication settings from the DB:
> sp_configure 'allow',1
> GO
> reconfigure with override
> GO
> USE ImageCraft
> GO
> sp_removedbreplication 'IMAGECRAFT'
> GO
> UPDATE sysobjects set replinfo=0 WHERE replinfo<>0
> GO
> Drop table MSdynamicsnapshotjobs
> Drop table MSdynamicsnapshotviews
> Drop table MSmerge_altsyncpartners
> Drop table MSmerge_contents
> Drop table MSmerge_delete_conflicts
> Drop table MSmerge_errorlineage
> Drop table MSmerge_genhistory
> Drop table MSmerge_replinfo
> Drop table MSmerge_tombstone
> Drop table MSrepl_identity_range
> Drop table sysmergearticles
> Drop table sysmergepublications
> Drop table sysmergeschemaarticles
> Drop table sysmergeschemachange
> Drop table sysmergesubscriptions
> Drop table sysmergesubsetfilters
> GO
> sp_configure 'allow',0
> GO
> reconfigure with override
> GO
> Appearently, I overkilled it because I get an error message I've never
> seen
> before when adding a table to the replication setup:
> SQL Server Enterprise Manager could not initialize an article based on
> table
> 'BusinessUnit'.
> Error 208: Invalid object name 'sysmergearticles'.
> Invalid object name 'sysmergeschemaarticles'.
> Invalid object name 'sysmergearticles'.
> Invalid object name 'sysmergeschmaarticles'.
> Could not use view or function 'sysmergeextendedarticlesview' because of
> binding errors.
> Could not use view or function 'sysmergeextendedarticlesview' because of
> binding errors.
> I did a restore on the I am trying to create the replication for, but
> still
> get the same errors.
> Any suggestions?
>
|||I tried this, but no success. The system tables required for replication
have been deleted and I'm not sure how to bring them back. This seems to be
crux anyways. Any further thoughts?
"Narayana Vyas Kondreddi" wrote:

> Try this. Using sp_dboption set 'published' and 'merge publish' options to
> false.
> Then from the publisher properties dialog box in enterprise manager, enable
> this database again for replication.
> Then try to setup a publication and see if it works.
> --
> HTH,
> Vyas, MVP (SQL Server)
> SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
>
> "Steven" <Steven@.discussions.microsoft.com> wrote in message
> news:1838D345-A23E-4CB6-A122-3736554334BE@.microsoft.com...
>
>
|||I tried this too, but no success. I seem to have deleted the system tables
required for replication and need to bring them back.
"Hilary Cotter" wrote:

> can you disable this database for merge publishing and then try to re-enable
> it. Also what version of SQL are you running?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Steven" <Steven@.discussions.microsoft.com> wrote in message
> news:1838D345-A23E-4CB6-A122-3736554334BE@.microsoft.com...
>
>

Tuesday, March 20, 2012

can't see the sql 2005 box from sql 2000 box

Hey guys. my plans were to setup replicatin for test from sql 2005 to sql
2000. I could see the 2k box from 2005 but not the other way. Is there
something i'm missing or it's not doable? Please let me know. Also, i can't
replicate from 2000 to 2005, right? can i replicate from 2005 to 2000? thank
you very much for your help...
Tejas
Tejas,
this article will explain the compatibility between different versions:
http://msdn2.microsoft.com/en-us/library/ms143241.aspx
As for setting up the SQL 2005 subscription to a 2000 publisher, you can set
this up by registering your 2000 publisher in Management Studio.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I actually have problems even before doing all this. I can't even register my
2005 box in 2000 SQL EM. I can register the 2000 box in 2005 though. To do
this, I'm using SQL authentication. I have created usernames in both servers.
I dont know if it's doable. Please let me know. Thank you for the article
though.
I will be able to use Transactional(1 way) i assume since my pub/dist is
2000 and sub will be 2005. Please let me know if i understand this crrrectly.
thank you.
|||Tejas,
I probably didn't explain myself clearly - what I was meaning is that you
can register the 2000 SQL Server in SSMS and then create the publication on
the 2000 box using SSMS.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hey Paul. I might be missing something maybe. I'll explain to you what i did.
I registered the 2000 box in SSMS. I created a Trans. publication (1 way)
from there. The publisher and dist side is setup. Now I wanted to add a pull
subscription from 2005 box.
What I did was, I went to the publisher properties on the 2000 box, went to
subscribers and tried to add a subscriber there. I supplied the instance
name, SQL authentication etc. for the 2005 box, but it gives me an error
saying
"SQL Server replication requires the actual server name to make a connection
to the server. Connections through a server alias, IP address, or any other
alternate name are not supported. Specify the actual server name, ''.
(Replication.Utilities)
I can ping my 2005 box but can't see SQL on that box from any 2000 boxes.
They are on different windows domain if that makes any difference for SQL
authentication. Please let me know how i would add this subscriber and
subscribe a 2005 box to a 2000 publication.
thank you, paul
Regards,
Tejas Parikh
|||Tejas,
I'll just install SQL 2000 on my 2005 Virtual PC then try to repro this.
Rgds,
Paul
"Tejas Parikh" <TejasParikh@.discussions.microsoft.com> wrote in message
news:258DC9E3-EA16-4A7B-AF7A-2BB853B26529@.microsoft.com...
> Hey Paul. I might be missing something maybe. I'll explain to you what i
> did.
> I registered the 2000 box in SSMS. I created a Trans. publication (1 way)
> from there. The publisher and dist side is setup. Now I wanted to add a
> pull
> subscription from 2005 box.
> What I did was, I went to the publisher properties on the 2000 box, went
> to
> subscribers and tried to add a subscriber there. I supplied the instance
> name, SQL authentication etc. for the 2005 box, but it gives me an error
> saying
> "SQL Server replication requires the actual server name to make a
> connection
> to the server. Connections through a server alias, IP address, or any
> other
> alternate name are not supported. Specify the actual server name, ''.
> (Replication.Utilities)
> I can ping my 2005 box but can't see SQL on that box from any 2000 boxes.
> They are on different windows domain if that makes any difference for SQL
> authentication. Please let me know how i would add this subscriber and
> subscribe a 2005 box to a 2000 publication.
> thank you, paul
> Regards,
> Tejas Parikh
|||Tejas,
I have no problem registering SQL 2005 as a subscriber on my SQP 2000
Publisher box. In fact, I didn't have to register the server in Enterprise
Manager as a SQL Server - it was automatically picked up. As a variation, I
could also create the subscription directly (including having the subscriber
added as I verified from the generated script) from within SSMS. You might
want to try it that way instead.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Hey Paul. I thought it should be that easy. but my EM doesn't pick it up. I
try to register it and it gives me an error saying the server doesn't exist
or access denied. the username i'm trying to use is a sysadmin on the 2005
box. Do i have to check something in Windows or i'm just crazy to not get it
to work? thank you for your time and help, Paul.
|||Tejas,
have a look in the SQL Server Configuration Manager on the 2005 box and
check onn the protocol properties that the instance isn't hidden. Also, on
the 2000 box, you say that pinging the 2005 box works - is this using the IP
address or the netbios name? If the IP address, then I wonder if a full
trust relationship exists between your domains? What happens if you ping the
netbiosname instead? If this doesn't work, then I think you'll need an alias
set up on the publisher for the subscriber, and an entry in the hosts file.
Also I can't tell if you've tried setting up the subscription while using
SSMS - both push and pull would be interesting.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Cant see sql express in vwd2005

I've installed vwd2005 and sql express, I'm trying to setup a database connection but the sql server doesnt appear in the drop down list. I've checked that the service is running and that the browser service is running too.

Anyone any ideas?

just type name of you server in the list and it should work

|||

just type name of you server in the list and it should work

Janusz

Monday, March 19, 2012

Can't save view - linked server

Our customer has an external SQL server on which they want to make a
lookup into a table/view.
I have setup a Linked server and retrieve data from the linked server.
Example:
EXEC sp_addlinkedserver
@.server = 'NPRSQL',
@.srvproduct = 'SQLServer OLEDB Provider',
@.provider = 'SQLOLEDB',
@.datasrc = 'SQL01'
Go
SELECT *
FROM NPRSQL.DTS.dbo.ItemView
However I can "create" the view, get the data, but when I try to save
the view I get the following error:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The
operation could
not be performed because the OLE DB provider 'SQLOLEDB' was unable to
begin a
distributed transaction.[Microsoft][ODBC SQL Server Driver][SQL
Server]
[OLE/DB
provider returned message: New transaction cannot enlist in the
specified transaction
coordinator.]
How can it be that I can get the data but not save the view?
I have tried to make a similarly scenario on the Northwind database,
create a view on the linked server and the "call" this view via a view
on my local server with the same result.
/refdkHi
see this link
http://support.microsoft.com/kb/839279
try this first and let us know
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"refdk" <fuhlendorf@.gmail.com> wrote in message
news:1181027684.578393.61140@.o5g2000hsb.googlegroups.com...
> Our customer has an external SQL server on which they want to make a
> lookup into a table/view.
> I have setup a Linked server and retrieve data from the linked server.
> Example:
> EXEC sp_addlinkedserver
> @.server = 'NPRSQL',
> @.srvproduct = 'SQLServer OLEDB Provider',
> @.provider = 'SQLOLEDB',
> @.datasrc = 'SQL01'
> Go
> SELECT *
> FROM NPRSQL.DTS.dbo.ItemView
> However I can "create" the view, get the data, but when I try to save
> the view I get the following error:
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The
> operation could
> not be performed because the OLE DB provider 'SQLOLEDB' was unable to
> begin a
> distributed transaction.[Microsoft][ODBC SQL Server Driver][SQ
L
> Server]
> [OLE/DB
> provider returned message: New transaction cannot enlist in the
> specified transaction
> coordinator.]
> How can it be that I can get the data but not save the view?
> I have tried to make a similarly scenario on the Northwind database,
> create a view on the linked server and the "call" this view via a view
> on my local server with the same result.
>
> /refdk
>|||I had already done most of the stuff in the kb-issue. However, I have
now completed every step but the error persists.
/refdk|||Hi
Can you post the view statement
Regards
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"refdk" <fuhlendorf@.gmail.com> wrote in message
news:1181109437.668792.166410@.q75g2000hsh.googlegroups.com...
>I had already done most of the stuff in the kb-issue. However, I have
> now completed every step but the error persists.
> /refdk
>|||SELECT dbo.Hornsh=F8j$Item.No_ AS [No], dbo.Hornsh=F8j
$Item.Description, dbo.Hornsh=F8j$Item.[Unit Price], SUM(dbo.[Hornsh
=F8j
$Item Ledger Entry].Quantity)
AS Quantity
FROM dbo.Hornsh=F8j$Item INNER JOIN
dbo.[Hornsh=F8j$Item Ledger Entry] ON dbo.Hornsh=F8j
$Item.No_ =3D dbo.[Hornsh=F8j$Item Ledger Entry].[Item No_]
GROUP BY dbo.Hornsh=F8j$Item.No_, dbo.Hornsh=F8j$Item.Description,
dbo.Hornsh=F8j$Item.[Unit Price]|||> How can it be that I can get the data but not save the view?
Are you trying to create the view inside of a transaction? Why is it going
through ODBC/OLEDB? Shouldn't you be creating the view in a query window
connected to that server, instead of trying to create the view through your
app via the linked server? (Well, that's how I would do it, anyway.)

Can't save view - linked server

Our customer has an external SQL server on which they want to make a
lookup into a table/view.
I have setup a Linked server and retrieve data from the linked server.
Example:
EXEC sp_addlinkedserver
@.server = 'NPRSQL',
@.srvproduct = 'SQLServer OLEDB Provider',
@.provider = 'SQLOLEDB',
@.datasrc = 'SQL01'
Go
SELECT *
FROM NPRSQL.DTS.dbo.ItemView
However I can "create" the view, get the data, but when I try to save
the view I get the following error:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The
operation could
not be performed because the OLE DB provider 'SQLOLEDB' was unable to
begin a
distributed transaction.[Microsoft][ODBC SQL Server Driver][SQL
Server]
[OLE/DB
provider returned message: New transaction cannot enlist in the
specified transaction
coordinator.]
How can it be that I can get the data but not save the view?
I have tried to make a similarly scenario on the Northwind database,
create a view on the linked server and the "call" this view via a view
on my local server with the same result.
/refdkHi
see this link
http://support.microsoft.com/kb/839279
try this first and let us know
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"refdk" <fuhlendorf@.gmail.com> wrote in message
news:1181027684.578393.61140@.o5g2000hsb.googlegroups.com...
> Our customer has an external SQL server on which they want to make a
> lookup into a table/view.
> I have setup a Linked server and retrieve data from the linked server.
> Example:
> EXEC sp_addlinkedserver
> @.server = 'NPRSQL',
> @.srvproduct = 'SQLServer OLEDB Provider',
> @.provider = 'SQLOLEDB',
> @.datasrc = 'SQL01'
> Go
> SELECT *
> FROM NPRSQL.DTS.dbo.ItemView
> However I can "create" the view, get the data, but when I try to save
> the view I get the following error:
> ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The
> operation could
> not be performed because the OLE DB provider 'SQLOLEDB' was unable to
> begin a
> distributed transaction.[Microsoft][ODBC SQL Server Driver][SQL
> Server]
> [OLE/DB
> provider returned message: New transaction cannot enlist in the
> specified transaction
> coordinator.]
> How can it be that I can get the data but not save the view?
> I have tried to make a similarly scenario on the Northwind database,
> create a view on the linked server and the "call" this view via a view
> on my local server with the same result.
>
> /refdk
>|||I had already done most of the stuff in the kb-issue. However, I have
now completed every step but the error persists.
/refdk|||Hi
Can you post the view statement
Regards
VT
Knowledge is power, share it...
http://oneplace4sql.blogspot.com/
"refdk" <fuhlendorf@.gmail.com> wrote in message
news:1181109437.668792.166410@.q75g2000hsh.googlegroups.com...
>I had already done most of the stuff in the kb-issue. However, I have
> now completed every step but the error persists.
> /refdk
>|||SELECT dbo.Hornsh=F8j$Item.No_ AS [No], dbo.Hornsh=F8j
$Item.Description, dbo.Hornsh=F8j$Item.[Unit Price], SUM(dbo.[Hornsh=F8j
$Item Ledger Entry].Quantity)
AS Quantity
FROM dbo.Hornsh=F8j$Item INNER JOIN
dbo.[Hornsh=F8j$Item Ledger Entry] ON dbo.Hornsh=F8j
$Item.No_ =3D dbo.[Hornsh=F8j$Item Ledger Entry].[Item No_]
GROUP BY dbo.Hornsh=F8j$Item.No_, dbo.Hornsh=F8j$Item.Description,
dbo.Hornsh=F8j$Item.[Unit Price]|||> How can it be that I can get the data but not save the view?
Are you trying to create the view inside of a transaction? Why is it going
through ODBC/OLEDB? Shouldn't you be creating the view in a query window
connected to that server, instead of trying to create the view through your
app via the linked server? (Well, that's how I would do it, anyway.)

Can't save view - linked server

Our customer has an external SQL server on which they want to make a
lookup into a table/view.
I have setup a Linked server and retrieve data from the linked server.
Example:
EXEC sp_addlinkedserver
@.server = 'NPRSQL',
@.srvproduct = 'SQLServer OLEDB Provider',
@.provider = 'SQLOLEDB',
@.datasrc = 'SQL01'
Go
SELECT *
FROM NPRSQL.DTS.dbo.ItemView
However I can "create" the view, get the data, but when I try to save
the view I get the following error:
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server]The
operation could
not be performed because the OLE DB provider 'SQLOLEDB' was unable to
begin a
distributed transaction.[Microsoft][ODBC SQL Server Driver][SQL
Server]
[OLE/DB
provider returned message: New transaction cannot enlist in the
specified transaction
coordinator.]
How can it be that I can get the data but not save the view?
I have tried to make a similarly scenario on the Northwind database,
create a view on the linked server and the "call" this view via a view
on my local server with the same result.
/refdk
I had already done most of the stuff in the kb-issue. However, I have
now completed every step but the error persists.
/refdk
|||SELECT dbo.Hornshj$Item.No_ AS [No], dbo.Hornshj
$Item.Description, dbo.Hornshj$Item.[Unit Price], SUM(dbo.[Hornshj
$Item Ledger Entry].Quantity)
AS Quantity
FROM dbo.Hornshj$Item INNER JOIN
dbo.[Hornshj$Item Ledger Entry] ON dbo.Hornshj
$Item.No_ = dbo.[Hornshj$Item Ledger Entry].[Item No_]
GROUP BY dbo.Hornshj$Item.No_, dbo.Hornshj$Item.Description,
dbo.Hornshj$Item.[Unit Price]
|||> How can it be that I can get the data but not save the view?
Are you trying to create the view inside of a transaction? Why is it going
through ODBC/OLEDB? Shouldn't you be creating the view in a query window
connected to that server, instead of trying to create the view through your
app via the linked server? (Well, that's how I would do it, anyway.)

Sunday, March 11, 2012

Can't run dts package job

I setup a job which call a dts package (I try to call it from file system and from SSIS Package Store with the same result) and it doesn't run.

If you take a look from the SQL Server Agent you could see this >>
2012-06-17 09:01:02 - ! [LOG] Step 1 of job 'prueba' (0x85B4D5E843DB3145A6A1A6A0A43D04F3) cannot be run because the DTS subsystem failed to load. The job has been suspended
Any ideas?This was happening to people that installed to a drive other than C:. Did you install to a different drive? It's a bug in setup. If so, you can fix it by changing the dbo.syssubsystems table in MSDB for the dts subsystem.

Look to see where it's pointing. It should be something like this:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\SQLDTSSS90.DLL

If the drive is different then the one you installed on, correct it. It should work then.

Please let me know if this worked.
Thanks,|||I saw what you said. I installed SQL in D drive in a directory called SQL_Server. The path you told me was right but the path in the agent_exe field was wrong.

Thanks for your help.|||Excellent! Glad to help out.|||

This was a dts in SQL 2005, right? If so, how did you get to the dbo.syssubsystems table? I know its in the MSDB but I can't get access to that table, even as an admin of the box. Any ideas?

|||

Hi,

I have a similar situation. We have program files on C:\ and Data files on D:\. I ran the following sql to update the syssubsystems table, but I still get the " 2007-01-22 12:13:37 - ! [LOG] Step 1 of job 'MaintenancePlan 1' (0xC433119AFB756E4E844D94759A65B68A) cannot be run because the SSIS subsystem failed to load. The job has been suspended" message.

INSERT INTO [msdb].[dbo].[syssubsystems]

([subsystem_id]

,[subsystem]

,[description_id]

,[subsystem_dll]

,[agent_exe]

,[start_entry_point]

,[event_entry_point]

,[stop_entry_point]

,[max_worker_threads])

VALUES

(11

,'SSIS'

,14538

,'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\SQLDTSSS90.DLL'

,'C:\Program Files\Microsoft SQL Server\90\DTS\Connections\Binn\DTExec.exe'

,'DtsStart'

,'DtsEvent'

,'DtsStop'

,200);

Do I need to restart the Intergration services service?

Paul

|||

janislkovach wrote:

This was a dts in SQL 2005, right? If so, how did you get to the dbo.syssubsystems table? I know its in the MSDB but I can't get access to that table, even as an admin of the box. Any ideas?

Did you log in as a SQL Server admin?|||

Yes I can login to the box with Domain admin, then onto the Database engine with the SA id and password. I run the sqlagent job as a 'SQL Server Intergration Services package' and it fails with the 'failed to load susbsystem message'. If I run it as an 'Operating system(CmdExec)' i.e dtexec / SQL "[package name]" etc, then it works.

I can obviously get round the problem this way, but it's frustrating it doesn't work as it should. I think it started to happen after SP1 was installed.

Is it something to do with what account Integration Services runs under? As all the other SQL server service run as domain admin, my intergration Services service runs as NT authority\network service. Should I run this as domain admin also?

One further thing, when comparing other boxes with my problem box, is that I have DTEXEC.exe & DTAttach(and associated Dll's) in C:\Program Files\Microsoft SQL Server\90\DTS\Connections\Binn on the problem box whereas they are in C:\Program Files\Microsoft SQL Server\90\DTS\Binn in all other ones. Is this my problem? Can I simply move them to C:\Program Files\Microsoft SQL Server\90\DTS\Binn?

Can't run dts package job

I setup a job which call a dts package (I try to call it from file system and from SSIS Package Store with the same result) and it doesn't run.

If you take a look from the SQL Server Agent you could see this >>
2012-06-17 09:01:02 - ! [LOG] Step 1 of job 'prueba' (0x85B4D5E843DB3145A6A1A6A0A43D04F3) cannot be run because the DTS subsystem failed to load. The job has been suspended
Any ideas?This was happening to people that installed to a drive other than C:. Did you install to a different drive? It's a bug in setup. If so, you can fix it by changing the dbo.syssubsystems table in MSDB for the dts subsystem.

Look to see where it's pointing. It should be something like this:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\SQLDTSSS90.DLL

If the drive is different then the one you installed on, correct it. It should work then.

Please let me know if this worked.
Thanks,|||I saw what you said. I installed SQL in D drive in a directory called SQL_Server. The path you told me was right but the path in the agent_exe field was wrong.

Thanks for your help.|||Excellent! Glad to help out.|||

This was a dts in SQL 2005, right? If so, how did you get to the dbo.syssubsystems table? I know its in the MSDB but I can't get access to that table, even as an admin of the box. Any ideas?

|||

Hi,

I have a similar situation. We have program files on C:\ and Data files on D:\. I ran the following sql to update the syssubsystems table, but I still get the " 2007-01-22 12:13:37 - ! [LOG] Step 1 of job 'MaintenancePlan 1' (0xC433119AFB756E4E844D94759A65B68A) cannot be run because the SSIS subsystem failed to load. The job has been suspended" message.

INSERT INTO [msdb].[dbo].[syssubsystems]

([subsystem_id]

,[subsystem]

,[description_id]

,[subsystem_dll]

,[agent_exe]

,[start_entry_point]

,[event_entry_point]

,[stop_entry_point]

,[max_worker_threads])

VALUES

(11

,'SSIS'

,14538

,'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\SQLDTSSS90.DLL'

,'C:\Program Files\Microsoft SQL Server\90\DTS\Connections\Binn\DTExec.exe'

,'DtsStart'

,'DtsEvent'

,'DtsStop'

,200);

Do I need to restart the Intergration services service?

Paul

|||

janislkovach wrote:

This was a dts in SQL 2005, right? If so, how did you get to the dbo.syssubsystems table? I know its in the MSDB but I can't get access to that table, even as an admin of the box. Any ideas?

Did you log in as a SQL Server admin?|||

Yes I can login to the box with Domain admin, then onto the Database engine with the SA id and password. I run the sqlagent job as a 'SQL Server Intergration Services package' and it fails with the 'failed to load susbsystem message'. If I run it as an 'Operating system(CmdExec)' i.e dtexec / SQL "[package name]" etc, then it works.

I can obviously get round the problem this way, but it's frustrating it doesn't work as it should. I think it started to happen after SP1 was installed.

Is it something to do with what account Integration Services runs under? As all the other SQL server service run as domain admin, my intergration Services service runs as NT authority\network service. Should I run this as domain admin also?

One further thing, when comparing other boxes with my problem box, is that I have DTEXEC.exe & DTAttach(and associated Dll's) in C:\Program Files\Microsoft SQL Server\90\DTS\Connections\Binn on the problem box whereas they are in C:\Program Files\Microsoft SQL Server\90\DTS\Binn in all other ones. Is this my problem? Can I simply move them to C:\Program Files\Microsoft SQL Server\90\DTS\Binn?

Can't run dts package job

I setup a job which call a dts package (I try to call it from file system and from SSIS Package Store with the same result) and it doesn't run.

If you take a look from the SQL Server Agent you could see this >>
2012-06-17 09:01:02 - ! [LOG] Step 1 of job 'prueba' (0x85B4D5E843DB3145A6A1A6A0A43D04F3) cannot be run because the DTS subsystem failed to load. The job has been suspended
Any ideas?This was happening to people that installed to a drive other than C:. Did you install to a different drive? It's a bug in setup. If so, you can fix it by changing the dbo.syssubsystems table in MSDB for the dts subsystem.

Look to see where it's pointing. It should be something like this:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\SQLDTSSS90.DLL

If the drive is different then the one you installed on, correct it. It should work then.

Please let me know if this worked.
Thanks,|||I saw what you said. I installed SQL in D drive in a directory called SQL_Server. The path you told me was right but the path in the agent_exe field was wrong.

Thanks for your help.|||Excellent! Glad to help out.|||

This was a dts in SQL 2005, right? If so, how did you get to the dbo.syssubsystems table? I know its in the MSDB but I can't get access to that table, even as an admin of the box. Any ideas?

|||

Hi,

I have a similar situation. We have program files on C:\ and Data files on D:\. I ran the following sql to update the syssubsystems table, but I still get the " 2007-01-22 12:13:37 - ! [LOG] Step 1 of job 'MaintenancePlan 1' (0xC433119AFB756E4E844D94759A65B68A) cannot be run because the SSIS subsystem failed to load. The job has been suspended" message.

INSERT INTO [msdb].[dbo].[syssubsystems]

([subsystem_id]

,[subsystem]

,[description_id]

,[subsystem_dll]

,[agent_exe]

,[start_entry_point]

,[event_entry_point]

,[stop_entry_point]

,[max_worker_threads])

VALUES

(11

,'SSIS'

,14538

,'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\binn\SQLDTSSS90.DLL'

,'C:\Program Files\Microsoft SQL Server\90\DTS\Connections\Binn\DTExec.exe'

,'DtsStart'

,'DtsEvent'

,'DtsStop'

,200);

Do I need to restart the Intergration services service?

Paul

|||

janislkovach wrote:

This was a dts in SQL 2005, right? If so, how did you get to the dbo.syssubsystems table? I know its in the MSDB but I can't get access to that table, even as an admin of the box. Any ideas?

Did you log in as a SQL Server admin?|||

Yes I can login to the box with Domain admin, then onto the Database engine with the SA id and password. I run the sqlagent job as a 'SQL Server Intergration Services package' and it fails with the 'failed to load susbsystem message'. If I run it as an 'Operating system(CmdExec)' i.e dtexec / SQL "[package name]" etc, then it works.

I can obviously get round the problem this way, but it's frustrating it doesn't work as it should. I think it started to happen after SP1 was installed.

Is it something to do with what account Integration Services runs under? As all the other SQL server service run as domain admin, my intergration Services service runs as NT authority\network service. Should I run this as domain admin also?

One further thing, when comparing other boxes with my problem box, is that I have DTEXEC.exe & DTAttach(and associated Dll's) in C:\Program Files\Microsoft SQL Server\90\DTS\Connections\Binn on the problem box whereas they are in C:\Program Files\Microsoft SQL Server\90\DTS\Binn in all other ones. Is this my problem? Can I simply move them to C:\Program Files\Microsoft SQL Server\90\DTS\Binn?

Thursday, February 16, 2012

Can't install sqlserver 2000

I tried the following question in setup, but didn't get an answer. I think
not being able to install sqlserver 2000 is a serious problem. I'd
appreciate any help.
thanks.
dennist685
When I try to install sql server 2000 I get the following message.
Microsoft sql server 2000 enterprise edition server component is not
supported on this operating system. Only client components will be available
for installation.
I have xp pro.
I have never installed sql server 2000 before.
If client components are sufficient, how do I configure the security as
simple as possible. For now, just so I can sign in with all rights, with as
little typing as possible.
I went this far before cancelling. I clicked setup(I have the msdn DVD
version). After clicking next a few times it gave me the choice of client
tools only or connectivity only. The option button for server and client
tools was greyed out.
I have adsl and an ethernet card for the adsl, but I am not connected to any
sqlserver 2000.
Please help.
dennist685
Hi,
The server components of the Enterprise Edition could not be installed on xp.
You should use the Developer Edition if you want to install all components
on xp.
If you do not have any server component available, client components only
will not provide the ability to create databases/tables….
Lionel
my answer
Thanks Lionel. I chose the developer edition, server and client tools.
However when I get to services accounts I accepted the default - use a domain
user account. It had the username I use for logon to windows - dennist685.
the domain name was my first name in Caps. I tried several passwords, but got
the following error message:
The logon account cannot be validated for the sql server service. Verify
that the user name and password entered are correct. The logon attempt
failed.
Any ideas?
dennist685
"dennist685" <dennist685@.discussions.microsoft.com> wrote in message
news:9ABFFC87-5999-4FDE-83D8-84E1CC3BF0E7@.microsoft.com...
>I tried the following question in setup, but didn't get an answer. I think
> not being able to install sqlserver 2000 is a serious problem. I'd
> appreciate any help.
> thanks.
> dennist685
> When I try to install sql server 2000 I get the following message.
> Microsoft sql server 2000 enterprise edition server component is not
> supported on this operating system. Only client components will be
> available
> for installation.
> I have xp pro.
> I have never installed sql server 2000 before.
> If client components are sufficient, how do I configure the security as
> simple as possible. For now, just so I can sign in with all rights, with
> as
> little typing as possible.
> I went this far before cancelling. I clicked setup(I have the msdn DVD
> version). After clicking next a few times it gave me the choice of client
> tools only or connectivity only. The option button for server and client
> tools was greyed out.
> I have adsl and an ethernet card for the adsl, but I am not connected to
> any
> sqlserver 2000.
> Please help.
> dennist685
> Hi,
> The server components of the Enterprise Edition could not be installed on
> xp.
> You should use the Developer Edition if you want to install all components
> on xp.
> If you do not have any server component available, client components only
> will not provide the ability to create databases/tables..
> Lionel
> my answer
> Thanks Lionel. I chose the developer edition, server and client tools.
> However when I get to services accounts I accepted the default - use a
> domain
> user account. It had the username I use for logon to windows -
> dennist685.
> the domain name was my first name in Caps. I tried several passwords, but
> got
> the following error message:
> The logon account cannot be validated for the sql server service. Verify
> that the user name and password entered are correct. The logon attempt
> failed.
> Any ideas?
> dennist685
On xp you can install only the "desktop" or "developer" edition. Find it in
you msdn cd collection.
|||"Giuseppe Battaglia" <beppeb_datogliere@.tiscali.it> wrote in message
news:QSesd.26134$C94.25844@.tornado.fastwebnet.it.. .
> On xp you can install only the "desktop" or "developer" edition. Find it
> in you msdn cd collection.
sorry, I did'nt read all (use > to quote!), use your computer name as domain
name (user name= PCNAME\USERNAME), or use a system account (if you don't
remember your password), or create a new user in xp (in the administrator
group).
|||Thanks Giuseppe,
I was installing the developer edition.
dennist685
"Giuseppe Battaglia" wrote:

> "dennist685" <dennist685@.discussions.microsoft.com> wrote in message
> news:9ABFFC87-5999-4FDE-83D8-84E1CC3BF0E7@.microsoft.com...
> On xp you can install only the "desktop" or "developer" edition. Find it in
> you msdn cd collection.
>
>
|||You can use your own network login for the service accounts on your
workstation but you need to be connected to the domain and you must have
local admin privleges.
Otherwise, the other options Giuseppe provide would be good alternatives.
Remember, if you use your own credentials, you will need to reset the
service account passwords whenever you change your password.
Sincerely,
Anthony Thomas

"dennist685" <dennist685@.discussions.microsoft.com> wrote in message
news:6F2716E5-9592-4E87-9E0D-C461399ADC84@.microsoft.com...
Thanks Giuseppe,
I was installing the developer edition.
dennist685
"Giuseppe Battaglia" wrote:
[vbcol=seagreen]
> "dennist685" <dennist685@.discussions.microsoft.com> wrote in message
> news:9ABFFC87-5999-4FDE-83D8-84E1CC3BF0E7@.microsoft.com...
think[vbcol=seagreen]
with[vbcol=seagreen]
client[vbcol=seagreen]
client[vbcol=seagreen]
on[vbcol=seagreen]
components[vbcol=seagreen]
only[vbcol=seagreen]
but[vbcol=seagreen]
Verify
> On xp you can install only the "desktop" or "developer" edition. Find it
in
> you msdn cd collection.
>
>
|||Thanks Anthony and Giuseppe
But, I can't say I know what you're talking about.
I have no password for the dennist685 xp account. It's the only account,
the only account I want, and I was never asked for a password in the xp pro
installation. I fully installed iis with frontpage extensions.
What do you mean by network login? The login my ISP gave me to connect to
ADSL? I'm not part of any network. Mine is a lone computer connected to the
internet through an ADSL. I don't know what is meant by own credentials.
I also have no idea what this sentence means: You can use your own network
login for the service accounts on your
workstation but you need to be connected to the domain and you must have
local admin privleges.
or how to do it. What I need is just the simplest way to install sqlserver
2000, any edition, on xp pro. given my only account is dennist685, and there
is no password. My ISP account is also named dennist685. To that there is a
password and I tried it with the error above.
You're dealing with a real newbie here. Up to now I've been dealing with
Microsoft Access databases.
Thanks.
dennist685
|||What I really want to know is the following. When I reach the point
specified, what should I type so that the installation proceeds.
Alternatively, what choices should I be making earlier in the installation
so that the screen in question works.
thanks.
dennist685
|||On Sun, 5 Dec 2004 03:13:01 -0800, "dennist685"
<dennist685@.discussions.microsoft.com> wrote:

>Thanks Anthony and Giuseppe
>But, I can't say I know what you're talking about.
>I have no password for the dennist685 xp account. It's the only account,
>the only account I want, and I was never asked for a password in the xp pro
>installation. I fully installed iis with frontpage extensions.
>What do you mean by network login? The login my ISP gave me to connect to
>ADSL? I'm not part of any network. Mine is a lone computer connected to the
>internet through an ADSL. I don't know what is meant by own credentials.
>I also have no idea what this sentence means: You can use your own network
>login for the service accounts on your
>workstation but you need to be connected to the domain and you must have
>local admin privleges.
> or how to do it. What I need is just the simplest way to install sqlserver
>2000, any edition, on xp pro. given my only account is dennist685, and there
>is no password. My ISP account is also named dennist685. To that there is a
>password and I tried it with the error above.
>You're dealing with a real newbie here. Up to now I've been dealing with
>Microsoft Access databases.
>
Use the "local system" option. That will work. (Unless you limited the
permissions for SYSTEM, which is unlikely)
Joachim.
This post is free post; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.
Joachim Verhagen (jcdverha@.xs4all.nl)
WWW http://www.xs4all.nl/~jcdverha/ (Science Jokes)
|||Joachim,
I got it installed. We got that far. However, when I view server explorer,
after a bunch of databases (all access)I get servers. under servers dennis.
One more indent a bunch of things ending in SQL Servers. Under that, one
indent more, is DENNIS. If I click the box for that, the screen freezes up
for awhile, then I finally get a login box that says
Server Dennis(textbox disabled)
Database blank (textbox disabled)
checkbox, unchecked, use NT integrated security
Login dennist685 (textbox enabled)
Password (blank (textbox enabled)
buttons OK, Cancel, Help
Help is unhelpful
If I click OK, nothing happens
If I click use NT sercurity and then OK, the screen freezes for a minute.
Then I get the message
[DTNETLIB[]ConnectionOpen(Connect(),]SL Server does not exist or access
denied.
dennist685
"Joachim Verhagen" wrote:

> On Sun, 5 Dec 2004 03:13:01 -0800, "dennist685"
> <dennist685@.discussions.microsoft.com> wrote:
>
> Use the "local system" option. That will work. (Unless you limited the
> permissions for SYSTEM, which is unlikely)
> Joachim.
> --
> This post is free post; you can redistribute it and/or
> modify it under the terms of the GNU General Public License
> as published by the Free Software Foundation; either version 2
> of the License, or (at your option) any later version.
> Joachim Verhagen (jcdverha@.xs4all.nl)
> WWW http://www.xs4all.nl/~jcdverha/ (Science Jokes)
>
|||I don't remember exactly what I did, but it seems installed now with all the
sample databases installed as well. 'Seems' is the operative word.
dennist685
"Joachim Verhagen" wrote:

> On Sun, 5 Dec 2004 03:13:01 -0800, "dennist685"
> <dennist685@.discussions.microsoft.com> wrote:
>
> Use the "local system" option. That will work. (Unless you limited the
> permissions for SYSTEM, which is unlikely)
> Joachim.
> --
> This post is free post; you can redistribute it and/or
> modify it under the terms of the GNU General Public License
> as published by the Free Software Foundation; either version 2
> of the License, or (at your option) any later version.
> Joachim Verhagen (jcdverha@.xs4all.nl)
> WWW http://www.xs4all.nl/~jcdverha/ (Science Jokes)
>

Can't install sqlserver 2000

I tried the following question in setup, but didn't get an answer. I think
not being able to install sqlserver 2000 is a serious problem. I'd
appreciate any help.
thanks.
dennist685
When I try to install sql server 2000 I get the following message.
Microsoft sql server 2000 enterprise edition server component is not
supported on this operating system. Only client components will be available
for installation.
I have xp pro.
I have never installed sql server 2000 before.
If client components are sufficient, how do I configure the security as
simple as possible. For now, just so I can sign in with all rights, with as
little typing as possible.
I went this far before cancelling. I clicked setup(I have the msdn DVD
version). After clicking next a few times it gave me the choice of client
tools only or connectivity only. The option button for server and client
tools was greyed out.
I have adsl and an ethernet card for the adsl, but I am not connected to any
sqlserver 2000.
Please help.
dennist685
Hi,
The server components of the Enterprise Edition could not be installed on xp.
You should use the Developer Edition if you want to install all components
on xp.
If you do not have any server component available, client components only
will not provide the ability to create databases/tablesâ?¦.
Lionel
my answer
Thanks Lionel. I chose the developer edition, server and client tools.
However when I get to services accounts I accepted the default - use a domain
user account. It had the username I use for logon to windows - dennist685.
the domain name was my first name in Caps. I tried several passwords, but got
the following error message:
The logon account cannot be validated for the sql server service. Verify
that the user name and password entered are correct. The logon attempt
failed.
Any ideas?
dennist685"dennist685" <dennist685@.discussions.microsoft.com> wrote in message
news:9ABFFC87-5999-4FDE-83D8-84E1CC3BF0E7@.microsoft.com...
>I tried the following question in setup, but didn't get an answer. I think
> not being able to install sqlserver 2000 is a serious problem. I'd
> appreciate any help.
> thanks.
> dennist685
> When I try to install sql server 2000 I get the following message.
> Microsoft sql server 2000 enterprise edition server component is not
> supported on this operating system. Only client components will be
> available
> for installation.
> I have xp pro.
> I have never installed sql server 2000 before.
> If client components are sufficient, how do I configure the security as
> simple as possible. For now, just so I can sign in with all rights, with
> as
> little typing as possible.
> I went this far before cancelling. I clicked setup(I have the msdn DVD
> version). After clicking next a few times it gave me the choice of client
> tools only or connectivity only. The option button for server and client
> tools was greyed out.
> I have adsl and an ethernet card for the adsl, but I am not connected to
> any
> sqlserver 2000.
> Please help.
> dennist685
> Hi,
> The server components of the Enterprise Edition could not be installed on
> xp.
> You should use the Developer Edition if you want to install all components
> on xp.
> If you do not have any server component available, client components only
> will not provide the ability to create databases/tables..
> Lionel
> my answer
> Thanks Lionel. I chose the developer edition, server and client tools.
> However when I get to services accounts I accepted the default - use a
> domain
> user account. It had the username I use for logon to windows -
> dennist685.
> the domain name was my first name in Caps. I tried several passwords, but
> got
> the following error message:
> The logon account cannot be validated for the sql server service. Verify
> that the user name and password entered are correct. The logon attempt
> failed.
> Any ideas?
> dennist685
On xp you can install only the "desktop" or "developer" edition. Find it in
you msdn cd collection.|||"Giuseppe Battaglia" <beppeb_datogliere@.tiscali.it> wrote in message
news:QSesd.26134$C94.25844@.tornado.fastwebnet.it...
>> Thanks Lionel. I chose the developer edition, server and client tools.
>> However when I get to services accounts I accepted the default - use a
>> domain
>> user account. It had the username I use for logon to windows -
>> dennist685.
>> the domain name was my first name in Caps. I tried several passwords, but
>> got
>> the following error message:
>> The logon account cannot be validated for the sql server service. Verify
>> that the user name and password entered are correct. The logon attempt
>> failed.
>> Any ideas?
>> dennist685
> On xp you can install only the "desktop" or "developer" edition. Find it
> in you msdn cd collection.
sorry, I did'nt read all (use > to quote!), use your computer name as domain
name (user name= PCNAME\USERNAME), or use a system account (if you don't
remember your password), or create a new user in xp (in the administrator
group).|||Thanks Giuseppe,
I was installing the developer edition.
dennist685
"Giuseppe Battaglia" wrote:
> "dennist685" <dennist685@.discussions.microsoft.com> wrote in message
> news:9ABFFC87-5999-4FDE-83D8-84E1CC3BF0E7@.microsoft.com...
> >I tried the following question in setup, but didn't get an answer. I think
> > not being able to install sqlserver 2000 is a serious problem. I'd
> > appreciate any help.
> >
> > thanks.
> >
> > dennist685
> >
> > When I try to install sql server 2000 I get the following message.
> >
> > Microsoft sql server 2000 enterprise edition server component is not
> > supported on this operating system. Only client components will be
> > available
> > for installation.
> >
> > I have xp pro.
> >
> > I have never installed sql server 2000 before.
> >
> > If client components are sufficient, how do I configure the security as
> > simple as possible. For now, just so I can sign in with all rights, with
> > as
> > little typing as possible.
> >
> > I went this far before cancelling. I clicked setup(I have the msdn DVD
> > version). After clicking next a few times it gave me the choice of client
> > tools only or connectivity only. The option button for server and client
> > tools was greyed out.
> >
> > I have adsl and an ethernet card for the adsl, but I am not connected to
> > any
> > sqlserver 2000.
> >
> > Please help.
> >
> > dennist685
> >
> > Hi,
> >
> > The server components of the Enterprise Edition could not be installed on
> > xp.
> > You should use the Developer Edition if you want to install all components
> > on xp.
> > If you do not have any server component available, client components only
> > will not provide the ability to create databases/tables..
> >
> > Lionel
> >
> > my answer
> >
> > Thanks Lionel. I chose the developer edition, server and client tools.
> > However when I get to services accounts I accepted the default - use a
> > domain
> > user account. It had the username I use for logon to windows -
> > dennist685.
> > the domain name was my first name in Caps. I tried several passwords, but
> > got
> > the following error message:
> >
> > The logon account cannot be validated for the sql server service. Verify
> > that the user name and password entered are correct. The logon attempt
> > failed.
> >
> > Any ideas?
> >
> > dennist685
> On xp you can install only the "desktop" or "developer" edition. Find it in
> you msdn cd collection.
>
>|||You can use your own network login for the service accounts on your
workstation but you need to be connected to the domain and you must have
local admin privleges.
Otherwise, the other options Giuseppe provide would be good alternatives.
Remember, if you use your own credentials, you will need to reset the
service account passwords whenever you change your password.
Sincerely,
Anthony Thomas
"dennist685" <dennist685@.discussions.microsoft.com> wrote in message
news:6F2716E5-9592-4E87-9E0D-C461399ADC84@.microsoft.com...
Thanks Giuseppe,
I was installing the developer edition.
dennist685
"Giuseppe Battaglia" wrote:
> "dennist685" <dennist685@.discussions.microsoft.com> wrote in message
> news:9ABFFC87-5999-4FDE-83D8-84E1CC3BF0E7@.microsoft.com...
> >I tried the following question in setup, but didn't get an answer. I
think
> > not being able to install sqlserver 2000 is a serious problem. I'd
> > appreciate any help.
> >
> > thanks.
> >
> > dennist685
> >
> > When I try to install sql server 2000 I get the following message.
> >
> > Microsoft sql server 2000 enterprise edition server component is not
> > supported on this operating system. Only client components will be
> > available
> > for installation.
> >
> > I have xp pro.
> >
> > I have never installed sql server 2000 before.
> >
> > If client components are sufficient, how do I configure the security as
> > simple as possible. For now, just so I can sign in with all rights,
with
> > as
> > little typing as possible.
> >
> > I went this far before cancelling. I clicked setup(I have the msdn DVD
> > version). After clicking next a few times it gave me the choice of
client
> > tools only or connectivity only. The option button for server and
client
> > tools was greyed out.
> >
> > I have adsl and an ethernet card for the adsl, but I am not connected to
> > any
> > sqlserver 2000.
> >
> > Please help.
> >
> > dennist685
> >
> > Hi,
> >
> > The server components of the Enterprise Edition could not be installed
on
> > xp.
> > You should use the Developer Edition if you want to install all
components
> > on xp.
> > If you do not have any server component available, client components
only
> > will not provide the ability to create databases/tables..
> >
> > Lionel
> >
> > my answer
> >
> > Thanks Lionel. I chose the developer edition, server and client tools.
> > However when I get to services accounts I accepted the default - use a
> > domain
> > user account. It had the username I use for logon to windows -
> > dennist685.
> > the domain name was my first name in Caps. I tried several passwords,
but
> > got
> > the following error message:
> >
> > The logon account cannot be validated for the sql server service.
Verify
> > that the user name and password entered are correct. The logon attempt
> > failed.
> >
> > Any ideas?
> >
> > dennist685
> On xp you can install only the "desktop" or "developer" edition. Find it
in
> you msdn cd collection.
>
>|||Thanks Anthony and Giuseppe
But, I can't say I know what you're talking about.
I have no password for the dennist685 xp account. It's the only account,
the only account I want, and I was never asked for a password in the xp pro
installation. I fully installed iis with frontpage extensions.
What do you mean by network login? The login my ISP gave me to connect to
ADSL? I'm not part of any network. Mine is a lone computer connected to the
internet through an ADSL. I don't know what is meant by own credentials.
I also have no idea what this sentence means: You can use your own network
login for the service accounts on your
workstation but you need to be connected to the domain and you must have
local admin privleges.
or how to do it. What I need is just the simplest way to install sqlserver
2000, any edition, on xp pro. given my only account is dennist685, and there
is no password. My ISP account is also named dennist685. To that there is a
password and I tried it with the error above.
You're dealing with a real newbie here. Up to now I've been dealing with
Microsoft Access databases.
Thanks.
dennist685|||What I really want to know is the following. When I reach the point
specified, what should I type so that the installation proceeds.
Alternatively, what choices should I be making earlier in the installation
so that the screen in question works.
thanks.
dennist685|||On Sun, 5 Dec 2004 03:13:01 -0800, "dennist685"
<dennist685@.discussions.microsoft.com> wrote:
>Thanks Anthony and Giuseppe
>But, I can't say I know what you're talking about.
>I have no password for the dennist685 xp account. It's the only account,
>the only account I want, and I was never asked for a password in the xp pro
>installation. I fully installed iis with frontpage extensions.
>What do you mean by network login? The login my ISP gave me to connect to
>ADSL? I'm not part of any network. Mine is a lone computer connected to the
>internet through an ADSL. I don't know what is meant by own credentials.
>I also have no idea what this sentence means: You can use your own network
>login for the service accounts on your
>workstation but you need to be connected to the domain and you must have
>local admin privleges.
> or how to do it. What I need is just the simplest way to install sqlserver
>2000, any edition, on xp pro. given my only account is dennist685, and there
>is no password. My ISP account is also named dennist685. To that there is a
>password and I tried it with the error above.
>You're dealing with a real newbie here. Up to now I've been dealing with
>Microsoft Access databases.
>
Use the "local system" option. That will work. (Unless you limited the
permissions for SYSTEM, which is unlikely)
Joachim.
--
This post is free post; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.
Joachim Verhagen (jcdverha@.xs4all.nl)
WWW http://www.xs4all.nl/~jcdverha/ (Science Jokes)|||Joachim,
I got it installed. We got that far. However, when I view server explorer,
after a bunch of databases (all access)I get servers. under servers dennis.
One more indent a bunch of things ending in SQL Servers. Under that, one
indent more, is DENNIS. If I click the box for that, the screen freezes up
for awhile, then I finally get a login box that says
Server Dennis(textbox disabled)
Database blank (textbox disabled)
checkbox, unchecked, use NT integrated security
Login dennist685 (textbox enabled)
Password (blank (textbox enabled)
buttons OK, Cancel, Help
Help is unhelpful
If I click OK, nothing happens
If I click use NT sercurity and then OK, the screen freezes for a minute.
Then I get the message
[DTNETLIB[]ConnectionOpen(Connect(),]SL Server does not exist or access
denied.
dennist685
"Joachim Verhagen" wrote:
> On Sun, 5 Dec 2004 03:13:01 -0800, "dennist685"
> <dennist685@.discussions.microsoft.com> wrote:
> >Thanks Anthony and Giuseppe
> >
> >But, I can't say I know what you're talking about.
> >
> >I have no password for the dennist685 xp account. It's the only account,
> >the only account I want, and I was never asked for a password in the xp pro
> >installation. I fully installed iis with frontpage extensions.
> >What do you mean by network login? The login my ISP gave me to connect to
> >ADSL? I'm not part of any network. Mine is a lone computer connected to the
> >internet through an ADSL. I don't know what is meant by own credentials.
> >
> >I also have no idea what this sentence means: You can use your own network
> >login for the service accounts on your
> >workstation but you need to be connected to the domain and you must have
> >local admin privleges.
> > or how to do it. What I need is just the simplest way to install sqlserver
> >2000, any edition, on xp pro. given my only account is dennist685, and there
> >is no password. My ISP account is also named dennist685. To that there is a
> >password and I tried it with the error above.
> >
> >You're dealing with a real newbie here. Up to now I've been dealing with
> >Microsoft Access databases.
> >
> Use the "local system" option. That will work. (Unless you limited the
> permissions for SYSTEM, which is unlikely)
> Joachim.
> --
> This post is free post; you can redistribute it and/or
> modify it under the terms of the GNU General Public License
> as published by the Free Software Foundation; either version 2
> of the License, or (at your option) any later version.
> Joachim Verhagen (jcdverha@.xs4all.nl)
> WWW http://www.xs4all.nl/~jcdverha/ (Science Jokes)
>|||I don't remember exactly what I did, but it seems installed now with all the
sample databases installed as well. 'Seems' is the operative word.
dennist685
"Joachim Verhagen" wrote:
> On Sun, 5 Dec 2004 03:13:01 -0800, "dennist685"
> <dennist685@.discussions.microsoft.com> wrote:
> >Thanks Anthony and Giuseppe
> >
> >But, I can't say I know what you're talking about.
> >
> >I have no password for the dennist685 xp account. It's the only account,
> >the only account I want, and I was never asked for a password in the xp pro
> >installation. I fully installed iis with frontpage extensions.
> >What do you mean by network login? The login my ISP gave me to connect to
> >ADSL? I'm not part of any network. Mine is a lone computer connected to the
> >internet through an ADSL. I don't know what is meant by own credentials.
> >
> >I also have no idea what this sentence means: You can use your own network
> >login for the service accounts on your
> >workstation but you need to be connected to the domain and you must have
> >local admin privleges.
> > or how to do it. What I need is just the simplest way to install sqlserver
> >2000, any edition, on xp pro. given my only account is dennist685, and there
> >is no password. My ISP account is also named dennist685. To that there is a
> >password and I tried it with the error above.
> >
> >You're dealing with a real newbie here. Up to now I've been dealing with
> >Microsoft Access databases.
> >
> Use the "local system" option. That will work. (Unless you limited the
> permissions for SYSTEM, which is unlikely)
> Joachim.
> --
> This post is free post; you can redistribute it and/or
> modify it under the terms of the GNU General Public License
> as published by the Free Software Foundation; either version 2
> of the License, or (at your option) any later version.
> Joachim Verhagen (jcdverha@.xs4all.nl)
> WWW http://www.xs4all.nl/~jcdverha/ (Science Jokes)
>|||SQLServer always installs with the sample databases, so you must have them.
The most likely cause is that SQLServer is not running. (SQLServer is a
service, not just a file like MSaccess). At the right of the taskbar you
should have an icon looking like a tower model computer with a circle on it.
If the circle shows a green arrow, SQLServer is running, if it shows a red
square it is not. If you see a red square you should double click the icon
and start SQLServer.
SQLServer comes with a tool called the enterprise manager. Start it up from
the start menu->programs->Microsoft SQLServer. You can easily manage
SQLServer with it. Navigate around and use right-clicks to see what actions
you can do.
Joachim.
On Mon, 6 Dec 2004 03:35:05 -0800, "dennist685"
<dennist685@.discussions.microsoft.com> wrote:
>I don't remember exactly what I did, but it seems installed now with all the
>sample databases installed as well. 'Seems' is the operative word.
>dennist685
>"Joachim Verhagen" wrote:
>> On Sun, 5 Dec 2004 03:13:01 -0800, "dennist685"
>> <dennist685@.discussions.microsoft.com> wrote:
>> >Thanks Anthony and Giuseppe
>> >
>> >But, I can't say I know what you're talking about.
>> >
>> >I have no password for the dennist685 xp account. It's the only account,
>> >the only account I want, and I was never asked for a password in the xp pro
>> >installation. I fully installed iis with frontpage extensions.
>> >What do you mean by network login? The login my ISP gave me to connect to
>> >ADSL? I'm not part of any network. Mine is a lone computer connected to the
>> >internet through an ADSL. I don't know what is meant by own credentials.
>> >
>> >I also have no idea what this sentence means: You can use your own network
>> >login for the service accounts on your
>> >workstation but you need to be connected to the domain and you must have
>> >local admin privleges.
>> > or how to do it. What I need is just the simplest way to install sqlserver
>> >2000, any edition, on xp pro. given my only account is dennist685, and there
>> >is no password. My ISP account is also named dennist685. To that there is a
>> >password and I tried it with the error above.
>> >
>> >You're dealing with a real newbie here. Up to now I've been dealing with
>> >Microsoft Access databases.
>> >
>> Use the "local system" option. That will work. (Unless you limited the
>> permissions for SYSTEM, which is unlikely)
>> Joachim.
>> --
>> This post is free post; you can redistribute it and/or
>> modify it under the terms of the GNU General Public License
>> as published by the Free Software Foundation; either version 2
>> of the License, or (at your option) any later version.
>> Joachim Verhagen (jcdverha@.xs4all.nl)
>> WWW http://www.xs4all.nl/~jcdverha/ (Science Jokes)
--
This post is free post; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.
Joachim Verhagen (jcdverha@.xs4all.nl)
WWW http://www.xs4all.nl/~jcdverha/ (Science Jokes)|||I hate to tell you, Joachim, but the tower doesn't appear in my taskbar.
What does that mean?
dennist685
"Joachim Verhagen" wrote:
> SQLServer always installs with the sample databases, so you must have them.
> The most likely cause is that SQLServer is not running. (SQLServer is a
> service, not just a file like MSaccess). At the right of the taskbar you
> should have an icon looking like a tower model computer with a circle on it.
> If the circle shows a green arrow, SQLServer is running, if it shows a red
> square it is not. If you see a red square you should double click the icon
> and start SQLServer.
> SQLServer comes with a tool called the enterprise manager. Start it up from
> the start menu->programs->Microsoft SQLServer. You can easily manage
> SQLServer with it. Navigate around and use right-clicks to see what actions
> you can do.
> Joachim.
>
> On Mon, 6 Dec 2004 03:35:05 -0800, "dennist685"
> <dennist685@.discussions.microsoft.com> wrote:
> >I don't remember exactly what I did, but it seems installed now with all the
> >sample databases installed as well. 'Seems' is the operative word.
> >
> >dennist685
> >
> >"Joachim Verhagen" wrote:
> >
> >> On Sun, 5 Dec 2004 03:13:01 -0800, "dennist685"
> >> <dennist685@.discussions.microsoft.com> wrote:
> >>
> >> >Thanks Anthony and Giuseppe
> >> >
> >> >But, I can't say I know what you're talking about.
> >> >
> >> >I have no password for the dennist685 xp account. It's the only account,
> >> >the only account I want, and I was never asked for a password in the xp pro
> >> >installation. I fully installed iis with frontpage extensions.
> >> >What do you mean by network login? The login my ISP gave me to connect to
> >> >ADSL? I'm not part of any network. Mine is a lone computer connected to the
> >> >internet through an ADSL. I don't know what is meant by own credentials.
> >> >
> >> >I also have no idea what this sentence means: You can use your own network
> >> >login for the service accounts on your
> >> >workstation but you need to be connected to the domain and you must have
> >> >local admin privleges.
> >> > or how to do it. What I need is just the simplest way to install sqlserver
> >> >2000, any edition, on xp pro. given my only account is dennist685, and there
> >> >is no password. My ISP account is also named dennist685. To that there is a
> >> >password and I tried it with the error above.
> >> >
> >> >You're dealing with a real newbie here. Up to now I've been dealing with
> >> >Microsoft Access databases.
> >> >
> >>
> >> Use the "local system" option. That will work. (Unless you limited the
> >> permissions for SYSTEM, which is unlikely)
> >>
> >> Joachim.
> >>
> >> --
> >> This post is free post; you can redistribute it and/or
> >> modify it under the terms of the GNU General Public License
> >> as published by the Free Software Foundation; either version 2
> >> of the License, or (at your option) any later version.
> >>
> >> Joachim Verhagen (jcdverha@.xs4all.nl)
> >> WWW http://www.xs4all.nl/~jcdverha/ (Science Jokes)
> >>
> --
> This post is free post; you can redistribute it and/or
> modify it under the terms of the GNU General Public License
> as published by the Free Software Foundation; either version 2
> of the License, or (at your option) any later version.
> Joachim Verhagen (jcdverha@.xs4all.nl)
> WWW http://www.xs4all.nl/~jcdverha/ (Science Jokes)
>|||I rebooted my system and the tower was right there in the taskbar.
thanks muchly,
dennist685
"Joachim Verhagen" wrote:
> SQLServer always installs with the sample databases, so you must have them.
> The most likely cause is that SQLServer is not running. (SQLServer is a
> service, not just a file like MSaccess). At the right of the taskbar you
> should have an icon looking like a tower model computer with a circle on it.
> If the circle shows a green arrow, SQLServer is running, if it shows a red
> square it is not. If you see a red square you should double click the icon
> and start SQLServer.
> SQLServer comes with a tool called the enterprise manager. Start it up from
> the start menu->programs->Microsoft SQLServer. You can easily manage
> SQLServer with it. Navigate around and use right-clicks to see what actions
> you can do.
> Joachim.
>
> On Mon, 6 Dec 2004 03:35:05 -0800, "dennist685"
> <dennist685@.discussions.microsoft.com> wrote:
> >I don't remember exactly what I did, but it seems installed now with all the
> >sample databases installed as well. 'Seems' is the operative word.
> >
> >dennist685
> >
> >"Joachim Verhagen" wrote:
> >
> >> On Sun, 5 Dec 2004 03:13:01 -0800, "dennist685"
> >> <dennist685@.discussions.microsoft.com> wrote:
> >>
> >> >Thanks Anthony and Giuseppe
> >> >
> >> >But, I can't say I know what you're talking about.
> >> >
> >> >I have no password for the dennist685 xp account. It's the only account,
> >> >the only account I want, and I was never asked for a password in the xp pro
> >> >installation. I fully installed iis with frontpage extensions.
> >> >What do you mean by network login? The login my ISP gave me to connect to
> >> >ADSL? I'm not part of any network. Mine is a lone computer connected to the
> >> >internet through an ADSL. I don't know what is meant by own credentials.
> >> >
> >> >I also have no idea what this sentence means: You can use your own network
> >> >login for the service accounts on your
> >> >workstation but you need to be connected to the domain and you must have
> >> >local admin privleges.
> >> > or how to do it. What I need is just the simplest way to install sqlserver
> >> >2000, any edition, on xp pro. given my only account is dennist685, and there
> >> >is no password. My ISP account is also named dennist685. To that there is a
> >> >password and I tried it with the error above.
> >> >
> >> >You're dealing with a real newbie here. Up to now I've been dealing with
> >> >Microsoft Access databases.
> >> >
> >>
> >> Use the "local system" option. That will work. (Unless you limited the
> >> permissions for SYSTEM, which is unlikely)
> >>
> >> Joachim.
> >>
> >> --
> >> This post is free post; you can redistribute it and/or
> >> modify it under the terms of the GNU General Public License
> >> as published by the Free Software Foundation; either version 2
> >> of the License, or (at your option) any later version.
> >>
> >> Joachim Verhagen (jcdverha@.xs4all.nl)
> >> WWW http://www.xs4all.nl/~jcdverha/ (Science Jokes)
> >>
> --
> This post is free post; you can redistribute it and/or
> modify it under the terms of the GNU General Public License
> as published by the Free Software Foundation; either version 2
> of the License, or (at your option) any later version.
> Joachim Verhagen (jcdverha@.xs4all.nl)
> WWW http://www.xs4all.nl/~jcdverha/ (Science Jokes)
>

cant install SQL Web Data Administrator

Hi

I am using Web Developer 2005 Express. I am trying to install the SQL Web Data Administrator (setup.msi), but it gives an error message saying that I need to install Framework 1.1, BUT I already have version 2, so no-go for me there.

Also I have been trying to install the Cassini version with zero luck. When I run the build.bat file I get the csc and gacutil errors. However, when I set up the Environmental variable PATH within My Computer\Properties\Advanced\Environmental Variables\user Variables as per the instructions on the Cassini discussion forum, no change, I do not get 200 bucks or pass GO .

Please tell me I am being stupid

Dose your system fit all the requirements?

System Requirements

Supported Operating Systems:Windows 2000

Can't install SQL Server 2005 Standard on Windows Server 2003

--
SQL Server 2005 Setup has detected incompatible components from beta
versions of Visual Studio, .NET Framework, or SQL Server 2005.
(Full text of dialog below.)
--
Well, thanks guys, for narrowing it down for me with such precision. :-\
Yes, I did have Beta components installed at one point, but I've removed
them all. I've looked through Add/Remove Programs and I don't see any Beta
products left to uninstall. How can I find out what exactly is blocking my
install?
Thanks for your help!
- Joe Geretz -
TITLE: Microsoft SQL Server 2005 Setup
--
SQL Server 2005 Setup has detected incompatible components from beta
versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or
Remove Programs to remove these components, and then run SQL Server 2005
Setup again. For detailed instructions on uninstalling SQL Server 2005, see
the SQL Server 2005 Readme.
For help, click:
http://go.microsoft.com/fwlink?Link...rform%400x11190
BUTTONS:
OK
--OK, I found it.
It was the SQL Server Setup Support Files, must have been left over form a
previous Beta install. Tricky, because it wasn't titled as Beta in the Add /
Remove Programs listing.
- Joe Geretz -
"Joseph Geretz" <jgeretz@.nospam.com> wrote in message
news:%23P$1CbOaGHA.3896@.TK2MSFTNGP05.phx.gbl...
> --
> SQL Server 2005 Setup has detected incompatible components from beta
> versions of Visual Studio, .NET Framework, or SQL Server 2005.
> (Full text of dialog below.)
> --
> Well, thanks guys, for narrowing it down for me with such precision. :-\
> Yes, I did have Beta components installed at one point, but I've removed
> them all. I've looked through Add/Remove Programs and I don't see any Beta
> products left to uninstall. How can I find out what exactly is blocking my
> install?
> Thanks for your help!
> - Joe Geretz -
> TITLE: Microsoft SQL Server 2005 Setup
> --
> SQL Server 2005 Setup has detected incompatible components from beta
> versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or
> Remove Programs to remove these components, and then run SQL Server 2005
> Setup again. For detailed instructions on uninstalling SQL Server 2005,
> see the SQL Server 2005 Readme.
>
> For help, click:
> http://go.microsoft.com/fwlink?Link...rform%400x11190
> --
> BUTTONS:
> OK
> --
>