Can't get in to SQLServer 2005 express with a Privileged account

Bummer. I can't remember the SA password. I had setup a user account, but I can't change anything or add any new accounts using this login. I can't get in using the windows authentication method no matter how I am logged into this machine.

Any suggestions? I have never been able to use Windows Authentication. There must be something I'm missing here. I have spent hours and hours trying to get into this machine. I just want to replicate a database. This is very frustrating.

Thanks guys.

How are you connecting to SQL Server? On Express edition, Windows authentication should always work even if you are non-admin.

You can also try using Windows Authentication with a user account that is a machine admin.

Alternatively, members of this Windows Group: SQLServer2005MSSQLUSER$<machine_name>$<instance_name> should also have access. Please replace the <machine_name> and <instance_name> variables with the appropriate values for your installation. So if you add your Windows user to this group, you should also have access.

What error message are you seeing?

Sung

|||

It was telling me that I couldn't access the default database. I found where someone said to do:

sqlcmd -E -d master

That allowed me to get the SQLCMD prompt. I didn't know what to do after that. I found in the SQL Server 2005 Administrator's Pocket Consultant that you can make any user an administrator by issuing the command:

sp_addsrvrolemember 'login', 'sysadmin'

That did the trick. I was able to elevate the one login that I knew to sysadmin status. From there I had full access and privileges.

Thanks for your response.

Can't find rsactivate.exe

I've spent a few hours bashing my head into the wall - no matter what I install and uninstall, I can't seem to get setup to put the rsactivate.exe file into my sql server 2005 installation. Without this tool, I can't get sql reporting working. Can anyone tell me step by step what I need to do to get this tool installed?

Thanks!

rsactivate.exe does no longer exist and is no longer needed in RS 2005.

There is a new graphical configuration tool (Reporting Services Configuration Tool) and you can use rsconfig.exe / rskeymgmt.exe to configure the report server.

-- Robert

|||

Thanks - now that I know that I managed to get my server set up, but the ReportServer virtual directory still returns this error:

Reporting Services Error

---

The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError)|||

Most likely the account that is configured to run the RS Web service (typcially Network Service) does not have any file system permissions to access the installation directory and consequently cannot access the configuration file.

In general, setup would set the ACLs correctly on those folders. However, you mentioned that you ran through multiple install/uninstall cycles, so something with the ACLs may be messed up.

One approach you should try is to start the RS configuration tool, go the web service account and (re-)apply the account settings.

-- Robert

|||

Looks like it was a conflict with sharepoint services. I found a KB article on this, and now everything seems to be resolved. I also found that I needed to run rskeymgmt -d to clear our the previously created keys before I could proceed.

Thanks for the help!

|||

I have problems also with Reporting Server SQL 2005 reinstallation. I am using the configurer and have restarted the installation many times, deleting each time the bases and web sites.

When I start the navigator to reach http://localhost/report server, I receive the message that the access to the file intepub/wwwroot/web.config is refused

there no reason that this file be accedded for Report Server and I dont'know what to do to find a solution

Thanks to reply if you have any idea

Gerard

Can't find rsactivate.exe

I've spent a few hours bashing my head into the wall - no matter what I install and uninstall, I can't seem to get setup to put the rsactivate.exe file into my sql server 2005 installation. Without this tool, I can't get sql reporting working. Can anyone tell me step by step what I need to do to get this tool installed?

Thanks!

rsactivate.exe does no longer exist and is no longer needed in RS 2005.

There is a new graphical configuration tool (Reporting Services Configuration Tool) and you can use rsconfig.exe / rskeymgmt.exe to configure the report server.

-- Robert

|||

Thanks - now that I know that I managed to get my server set up, but the ReportServer virtual directory still returns this error:

Reporting Services Error

---

The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError)|||

Most likely the account that is configured to run the RS Web service (typcially Network Service) does not have any file system permissions to access the installation directory and consequently cannot access the configuration file.

In general, setup would set the ACLs correctly on those folders. However, you mentioned that you ran through multiple install/uninstall cycles, so something with the ACLs may be messed up.

One approach you should try is to start the RS configuration tool, go the web service account and (re-)apply the account settings.

-- Robert

|||

Looks like it was a conflict with sharepoint services. I found a KB article on this, and now everything seems to be resolved. I also found that I needed to run rskeymgmt -d to clear our the previously created keys before I could proceed.

Thanks for the help!

|||

I have problems also with Reporting Server SQL 2005 reinstallation. I am using the configurer and have restarted the installation many times, deleting each time the bases and web sites.

When I start the navigator to reach http://localhost/report server, I receive the message that the access to the file intepub/wwwroot/web.config is refused

there no reason that this file be accedded for Report Server and I dont'know what to do to find a solution

Thanks to reply if you have any idea

Gerard

can't find Enterprise Manager and Query Analyzer after setup

I downloaded the trial version of sql server 2005. but after installation, I couldnt find the Enterprise Manager and Query Analyzer. Any idea about that? Thanks.

Hi zhishan,

I believe those services can be configured from control panel (turn windows features on or off). Check the boxes next to enterprise manager services and query analyzer, then ok, and windows wil configure and update for those services.

|||Thanks djartsinc - do you know where on the control panel has the function? I spent a long time trying to find, but couldn't...|||

Which Edition of SQL Server 2005 do you download? If it is SQL Server 2005 Express, such tool is not included. Please try SQL Server 2005 Expree with Advanced Services, which includes tools. You can get it from the same download website as SQL Server 2005 Express.

Cant Export Fields w/ over 255 characters

I have a query where I am trying to export a column that has around
2000 characters and it is truncated. What is not setup in MS SQL
correctly so that DTS will export the csv correctly.

Thanks,
John<quinniii@.yahoo.com> wrote in message
news:1109013962.276779.70380@.o13g2000cwo.googlegro ups.com...
>I have a query where I am trying to export a column that has around
> 2000 characters and it is truncated. What is not setup in MS SQL
> correctly so that DTS will export the csv correctly.
> Thanks,
> John

This might be the issue:

http://www.sqldts.com/?297

If that doesn't help, then I suggest you post more information - what
version of MSSL, what data source and target types do you have, what sort of
task/transformation are you using to move the data etc.

Simon

Can''t Delete Maintenance Report Files (txt) in SQL/2005

I have several maintenance plans setup and working in SQL/2005 (sp2 9.0.3042) on several servers; however, the .txt maint plan output files will not delete on any of the servers. The backups run fine, the old database and transaction log backup files delete fine (.bak and .trn); but, the .txt files won't go away unless I delete them by hand. I tried copy/paste the scripted command (xp_delete_file) and it runs with no errors but does not delete the old .txt files. ( This server was upgraded from SQL/2000 -

EXECUTE master.dbo.xp_delete_file 1,N'E:\Program Files\Microsoft SQL Server\MSSQL\LOG\',N'txt',N'2007-07-09T10:59:38'

)

I do NOT specify a period (.) in the file extension dialog box. Any ideas before I setup a .cmd batch file and schedule it instead?

Thanks in Advance,

DeWayne

did you create a maintenance clean up task and specify the .txt file extension to delete old text files ? but xp_delete_file is corresponding T_SQL of the cleanup task............if you hevent created the cleanup task just try it out and get back

|||

Yes! That's where I got the xp_delete_file script that I quoted in my original post...as it does not delete any .txt files.

Thanks

|||

Same problem here. Is there any hotfix to address this issue?

|||Same here - I've tried on several SQL 2005 servers and none of them delete the .txt files. Any ideas?
|||Same for me, anyone from MS like to comment on this?|||

There is a support article on the subject, http://support.microsoft.com/kb/938085. The problem appears to be the first line of text in the report files. If it says "NEW COMPONENT OUTPUT", then xp_delete_file will not delete it. The stated workaround is to remove this text. That does work, but it's probably simpler to just manually delete the file. Hope a fix comes out soon.

Can''t Delete Maintenance Report Files (txt) in SQL/2005

I have several maintenance plans setup and working in SQL/2005 (sp2 9.0.3042) on several servers; however, the .txt maint plan output files will not delete on any of the servers. The backups run fine, the old database and transaction log backup files delete fine (.bak and .trn); but, the .txt files won't go away unless I delete them by hand. I tried copy/paste the scripted command (xp_delete_file) and it runs with no errors but does not delete the old .txt files. ( This server was upgraded from SQL/2000 -

EXECUTE master.dbo.xp_delete_file 1,N'E:\Program Files\Microsoft SQL Server\MSSQL\LOG\',N'txt',N'2007-07-09T10:59:38'

)

I do NOT specify a period (.) in the file extension dialog box. Any ideas before I setup a .cmd batch file and schedule it instead?

Thanks in Advance,

DeWayne

did you create a maintenance clean up task and specify the .txt file extension to delete old text files ? but xp_delete_file is corresponding T_SQL of the cleanup task............if you hevent created the cleanup task just try it out and get back

|||

Yes! That's where I got the xp_delete_file script that I quoted in my original post...as it does not delete any .txt files.

Thanks

|||

Same problem here. Is there any hotfix to address this issue?

|||Same here - I've tried on several SQL 2005 servers and none of them delete the .txt files. Any ideas?
|||Same for me, anyone from MS like to comment on this?|||

There is a support article on the subject, http://support.microsoft.com/kb/938085. The problem appears to be the first line of text in the report files. If it says "NEW COMPONENT OUTPUT", then xp_delete_file will not delete it. The stated workaround is to remove this text. That does work, but it's probably simpler to just manually delete the file. Hope a fix comes out soon.

Can''t Delete Maintenance Report Files (txt) in SQL/2005

I have several maintenance plans setup and working in SQL/2005 (sp2 9.0.3042) on several servers; however, the .txt maint plan output files will not delete on any of the servers. The backups run fine, the old database and transaction log backup files delete fine (.bak and .trn); but, the .txt files won't go away unless I delete them by hand. I tried copy/paste the scripted command (xp_delete_file) and it runs with no errors but does not delete the old .txt files. ( This server was upgraded from SQL/2000 -

EXECUTE master.dbo.xp_delete_file 1,N'E:\Program Files\Microsoft SQL Server\MSSQL\LOG\',N'txt',N'2007-07-09T10:59:38'

)

I do NOT specify a period (.) in the file extension dialog box. Any ideas before I setup a .cmd batch file and schedule it instead?

Thanks in Advance,

DeWayne

did you create a maintenance clean up task and specify the .txt file extension to delete old text files ? but xp_delete_file is corresponding T_SQL of the cleanup task............if you hevent created the cleanup task just try it out and get back

|||

Yes! That's where I got the xp_delete_file script that I quoted in my original post...as it does not delete any .txt files.

Thanks

|||

Same problem here. Is there any hotfix to address this issue?

|||Same here - I've tried on several SQL 2005 servers and none of them delete the .txt files. Any ideas?
|||

Same for me, anyone from MS like to comment on this?|||

There is a support article on the subject, http://support.microsoft.com/kb/938085. The problem appears to be the first line of text in the report files. If it says "NEW COMPONENT OUTPUT", then xp_delete_file will not delete it. The stated workaround is to remove this text. That does work, but it's probably simpler to just manually delete the file. Hope a fix comes out soon.

Can''t Delete Maintenance Report Files (txt) in SQL/2005

I have several maintenance plans setup and working in SQL/2005 (sp2 9.0.3042) on several servers; however, the .txt maint plan output files will not delete on any of the servers. The backups run fine, the old database and transaction log backup files delete fine (.bak and .trn); but, the .txt files won't go away unless I delete them by hand. I tried copy/paste the scripted command (xp_delete_file) and it runs with no errors but does not delete the old .txt files. ( This server was upgraded from SQL/2000 -

EXECUTE master.dbo.xp_delete_file 1,N'E:\Program Files\Microsoft SQL Server\MSSQL\LOG\',N'txt',N'2007-07-09T10:59:38'

)

I do NOT specify a period (.) in the file extension dialog box. Any ideas before I setup a .cmd batch file and schedule it instead?

Thanks in Advance,

DeWayne

did you create a maintenance clean up task and specify the .txt file extension to delete old text files ? but xp_delete_file is corresponding T_SQL of the cleanup task............if you hevent created the cleanup task just try it out and get back

|||

Yes! That's where I got the xp_delete_file script that I quoted in my original post...as it does not delete any .txt files.

Thanks

|||

Same problem here. Is there any hotfix to address this issue?

|||Same here - I've tried on several SQL 2005 servers and none of them delete the .txt files. Any ideas?
|||Same for me, anyone from MS like to comment on this?|||

There is a support article on the subject, http://support.microsoft.com/kb/938085. The problem appears to be the first line of text in the report files. If it says "NEW COMPONENT OUTPUT", then xp_delete_file will not delete it. The stated workaround is to remove this text. That does work, but it's probably simpler to just manually delete the file. Hope a fix comes out soon.

Can't delete database that has been part of replication

I had a publication (merge) setup for a database. Deleted the publication and tried to delete the database. Sql server says it can't be deleted because it's has replication setup. Bug?

Found the answer. I had to run a stored procedure to get all replication objects removed from my db.

sp_removedbreplication @.dbname = 'dbname', @.type = 'merge'

/Magnus

can't delete a row?

I have transaction replication setup between publisher server and subscriber
server.
I tried to delete a row from publisher's table,
but it looks like it's running forever.
delete from sym_type where type_id=1
And I don't know what to troubleshoot. but if I do an insert, then it's
working. i also see the row being replicated to subscriber when I do an
insert.
insert into sym_type values (-3, 'test', null)
scraching my head hard. replication monitor show no errors.
kevin
Kevin,
sounds like a contention issue - you could use sp_who2 and look for blocking
(use dbcc inputbuffer to see the cause of the block).
If not that, then try running select * from sym_type (nolock) where
type_id=1 to see how many rows there are - it might be a big delete?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||no... there is only 10 rows in the table.
and I inserted a row type_id = 1 to test replication, which it works
fine.
So I tried to delete the same row to rollback the change, but then it failed
to delete the row.
I think it maybe has to do with replication.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OgpkHnn1FHA.3568@.TK2MSFTNGP15.phx.gbl...
> Kevin,
> sounds like a contention issue - you could use sp_who2 and look for
> blocking (use dbcc inputbuffer to see the cause of the block).
> If not that, then try running select * from sym_type (nolock) where
> type_id=1 to see how many rows there are - it might be a big delete?
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Kevin - what about the blocking results from sp_who2 - see any?
Paul Ibison
|||yes, sp_who2 shows BlockBy - spid 60.
Command delete.
interesting huh? why can't I delete it?
I even did dbcc checktable, nothing wrong.
so i go to spid 60
it's command "delete from sym_type where type_id =1"
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OGrJB6n1FHA.2212@.TK2MSFTNGP15.phx.gbl...
> Kevin - what about the blocking results from sp_who2 - see any?
> Paul Ibison
>
|||Kevin,
strange - what's the spid/command command that is blocked by spid 60 - are
you saying it is another spid doing exactly the same command?
Paul
|||no.. there is [BlockBy] column in sp_who2 recordset,
there is value 60
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OuuDpro1FHA.2072@.TK2MSFTNGP14.phx.gbl...
> Kevin,
> strange - what's the spid/command command that is blocked by spid 60 - are
> you saying it is another spid doing exactly the same command?
> Paul
>
|||I'm still a little confused here You have 2 processes, and one blocks the
other. If I understand properly the one which is causing the block is the
delete, and the other one is blocked by the delete. If so, I agree that this
is strange and is the opposite of what I'd have expected. I suppose you
don't have some cunning triggers at work, or cascade deletes in action? -
worth checking out. DBCC OPENTRAN might also reveal something more but I
doubt it (still, worth a try). In your case I'd kill the delete spid, then
confirm that there's no blocking at all, and no open transactions. After
that, do a corresponding select, or perhaps just run the delete again if
it's ok.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||oh... I think I do have cascade delete in action.
my primary table is sym_type, foreign key table is portfolio_position ,
symbol_id is the key on both tables.
- it's enforce relationship for replication.
- it's enforce relationship for INSERTS and DELETES
it's cascading update related fields.
it's cascading delete related fields.
That must be it. when I do INSERT statement, there is no problem.
but when I do update or delete statement, query runs forever.
The next question is, why is this happen? I'm inserting a new symbol_id
which doesn't exist in foreign table,
why would this become a problem?
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eLNLDCN2FHA.2444@.TK2MSFTNGP10.phx.gbl...
> I'm still a little confused here You have 2 processes, and one blocks
> the other. If I understand properly the one which is causing the block is
> the delete, and the other one is blocked by the delete. If so, I agree
> that this is strange and is the opposite of what I'd have expected. I
> suppose you don't have some cunning triggers at work, or cascade deletes
> in action? - worth checking out. DBCC OPENTRAN might also reveal something
> more but I doubt it (still, worth a try). In your case I'd kill the delete
> spid, then confirm that there's no blocking at all, and no open
> transactions. After that, do a corresponding select, or perhaps just run
> the delete again if it's ok.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Kevin,
is there a self join, or a circular-relationship between the tables perhaps?
Do you see the same behaviour in the absence of replication (if this is
possible to test). Actually you could DTS the tables to a test server and
test there.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Cant Create Subscription...

I've got a strange problem that I can't quite figure out. Whenever I go to setup a new subscription for a report (any report) I can't select a schedule or create the subscription.
I get to the Subscription page, but pressing any of the buttons: "Ok", "Cancel", "Select Schedule" does nothing.
Anyone else ever have this issue?
Any feedback would be greatly appreciated.

Hi
can you able to see SubscriptionProperties.aspx Page after clicking on New Subscription.
Thanx
Rohit|||

Yeah, pressing "New Subscription" takes me to the form (SubscriptionProperties.aspx), but not matter what button I press on the form - Ok, Cancel, Select Schedule... nothing happens.
It's as if you were creating an .aspx form and set "AutoPostBack" on a control to false. Clicking on any of the buttons does nothing. Therefore, I'm not able to create a new subscription or alter
any of the subscriptions schedules that I currently have.
I've restarted the reportserver service and I've restarted the application pool. Neither helps.

|||

Just wanted to follow up on this in case that someone else runs accross this. This was a framework issue with SP1. Not really related to Reporting Services, but possibly relevant nonetheless.

http://channel9.msdn.com/showpost.aspx?postid=21650

Can't create linked server

Dear Sir,
I have a remote db server which I can connect using Query Analyzer but can't
setup a linked server to it, using same user account, any suggestion how to
trouble shoot?
HenryHenry
What is an error you are getting?
"Henry" <Henry@.discussions.microsoft.com> wrote in message
news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
> Dear Sir,
> I have a remote db server which I can connect using Query Analyzer but
> can't
> setup a linked server to it, using same user account, any suggestion how
> to
> trouble shoot?
> Henry|||Dear Uri Dimant,
I can create the linked server but whenever I tried to access, e.g. click on
the Security->Linked Server->RemoteServer->Table/View, it return the error of
Error 7399
Both of my local and remote db are SQL 2000.
Henry
"Uri Dimant" wrote:
> Henry
> What is an error you are getting?
> "Henry" <Henry@.discussions.microsoft.com> wrote in message
> news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
> > Dear Sir,
> > I have a remote db server which I can connect using Query Analyzer but
> > can't
> > setup a linked server to it, using same user account, any suggestion how
> > to
> > trouble shoot?
> > Henry
>
>|||Hi Henry,
Do u have sa password on both the server.
if yes then drop ur linked server and create another one
give remote user and local user as sa and sa password.
in the other server type should be sql server if u create linked
server between sql server.
click the remote login option and give sa and sa password.
check the server option
these three should be selected
dataaccess,
RPC and RPC Out.
hope this help u
from
Doller
Henry wrote:
> Dear Uri Dimant,
> I can create the linked server but whenever I tried to access, e.g. click on
> the Security->Linked Server->RemoteServer->Table/View, it return the error of
> Error 7399
> Both of my local and remote db are SQL 2000.
> Henry
> "Uri Dimant" wrote:
> > Henry
> > What is an error you are getting?
> >
> > "Henry" <Henry@.discussions.microsoft.com> wrote in message
> > news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
> > > Dear Sir,
> > > I have a remote db server which I can connect using Query Analyzer but
> > > can't
> > > setup a linked server to it, using same user account, any suggestion how
> > > to
> > > trouble shoot?
> > > Henry
> >
> >
> >|||This has some example syntax for adding a linked server:
http://msdn.microsoft.com/library/en-us/tsqlref/ts_sp_adda_8gqa.asp
-oj
"Henry" <Henry@.discussions.microsoft.com> wrote in message
news:5B480C91-E86A-46FC-AFC3-D59D8CBBBCCA@.microsoft.com...
> Dear Uri Dimant,
> I can create the linked server but whenever I tried to access, e.g. click
> on
> the Security->Linked Server->RemoteServer->Table/View, it return the error
> of
> Error 7399
> Both of my local and remote db are SQL 2000.
> Henry
> "Uri Dimant" wrote:
>> Henry
>> What is an error you are getting?
>> "Henry" <Henry@.discussions.microsoft.com> wrote in message
>> news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
>> > Dear Sir,
>> > I have a remote db server which I can connect using Query Analyzer but
>> > can't
>> > setup a linked server to it, using same user account, any suggestion
>> > how
>> > to
>> > trouble shoot?
>> > Henry
>>|||Dear Doller,
I don't have SA account on remote db right now, but I have other linked
server using account without SA rights, e.g. have dbo rights and can also
make connection. Do you know if there any docuement for the access rights
requirement?
Henry
"doller" wrote:
> Hi Henry,
> Do u have sa password on both the server.
> if yes then drop ur linked server and create another one
> give remote user and local user as sa and sa password.
> in the other server type should be sql server if u create linked
> server between sql server.
> click the remote login option and give sa and sa password.
> check the server option
> these three should be selected
> dataaccess,
> RPC and RPC Out.
> hope this help u
> from
> Doller
>
> Henry wrote:
> > Dear Uri Dimant,
> > I can create the linked server but whenever I tried to access, e.g. click on
> > the Security->Linked Server->RemoteServer->Table/View, it return the error of
> > Error 7399
> >
> > Both of my local and remote db are SQL 2000.
> >
> > Henry
> >
> > "Uri Dimant" wrote:
> >
> > > Henry
> > > What is an error you are getting?
> > >
> > > "Henry" <Henry@.discussions.microsoft.com> wrote in message
> > > news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
> > > > Dear Sir,
> > > > I have a remote db server which I can connect using Query Analyzer but
> > > > can't
> > > > setup a linked server to it, using same user account, any suggestion how
> > > > to
> > > > trouble shoot?
> > > > Henry
> > >
> > >
> > >
>

Can't create linked server

Dear Sir,
I have a remote db server which I can connect using Query Analyzer but can't
setup a linked server to it, using same user account, any suggestion how to
trouble shoot?
HenryHenry
What is an error you are getting?
"Henry" <Henry@.discussions.microsoft.com> wrote in message
news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
> Dear Sir,
> I have a remote db server which I can connect using Query Analyzer but
> can't
> setup a linked server to it, using same user account, any suggestion how
> to
> trouble shoot?
> Henry|||Dear Uri Dimant,
I can create the linked server but whenever I tried to access, e.g. click on
the Security->Linked Server->RemoteServer->Table/View, it return the error o
f
Error 7399
Both of my local and remote db are SQL 2000.
Henry
"Uri Dimant" wrote:

> Henry
> What is an error you are getting?
> "Henry" <Henry@.discussions.microsoft.com> wrote in message
> news:C31AA693-9574-4636-B56E-5E004189F6CF@.microsoft.com...
>
>|||Hi Henry,
Do u have sa password on both the server.
if yes then drop ur linked server and create another one
give remote user and local user as sa and sa password.
in the other server type should be sql server if u create linked
server between sql server.
click the remote login option and give sa and sa password.
check the server option
these three should be selected
dataaccess,
RPC and RPC Out.
hope this help u
from
Doller
Henry wrote:[vbcol=seagreen]
> Dear Uri Dimant,
> I can create the linked server but whenever I tried to access, e.g. click
on
> the Security->Linked Server->RemoteServer->Table/View, it return the error
of
> Error 7399
> Both of my local and remote db are SQL 2000.
> Henry
> "Uri Dimant" wrote:
>|||This has some example syntax for adding a linked server:
http://msdn.microsoft.com/library/e...p_adda_8gqa.asp
-oj
"Henry" <Henry@.discussions.microsoft.com> wrote in message
news:5B480C91-E86A-46FC-AFC3-D59D8CBBBCCA@.microsoft.com...[vbcol=seagreen]
> Dear Uri Dimant,
> I can create the linked server but whenever I tried to access, e.g. click
> on
> the Security->Linked Server->RemoteServer->Table/View, it return the error
> of
> Error 7399
> Both of my local and remote db are SQL 2000.
> Henry
> "Uri Dimant" wrote:
>|||Dear Doller,
I don't have SA account on remote db right now, but I have other linked
server using account without SA rights, e.g. have dbo rights and can also
make connection. Do you know if there any docuement for the access rights
requirement?
Henry
"doller" wrote:

> Hi Henry,
> Do u have sa password on both the server.
> if yes then drop ur linked server and create another one
> give remote user and local user as sa and sa password.
> in the other server type should be sql server if u create linked
> server between sql server.
> click the remote login option and give sa and sa password.
> check the server option
> these three should be selected
> dataaccess,
> RPC and RPC Out.
> hope this help u
> from
> Doller
>
> Henry wrote:
>

Can't create a setup project for project referencing Microsoft.SqlServer.ManagedDTS

I have a very small project written in VB.Net 2005 using the SQL Server 2005 SSiS DTSx package.

I took a SQL Server 2000 dts package and using the SQL Server 3005 legacy tools migrated it so I could still use the package withing SQL 2005 until I can build one using BI/SSIS.

Anyway,I added the reference Microsoft.SqlServer.ManagedDTS so I could then use the Microsoft.SqlServer.Dts.Runtime so I can execute the commands:

Dim oApp As New Application
Dim oPkg As New Package
oPkg = oApp.LoadPackage(g_DTSx_Directory & "AOC copy Generic1 CSV to AOC_verify_file_1.dtsx", Nothing)
Dim oResults As DTSExecResult
oResults = oPkg.Execute

Ok. That works fine. Executes without a hitch. So now I try and create a setup project for this and I use the setup wizard.

During the creation of the setup project I get a message that states:
The following files may have dependencies that cannot be determined automatically. Please confirm that all dependencies have been added to the project.
C:\windows\system32\msxml6.dll

OK. The dll is part of the reference I mentioned above and I have no idea what other dependencies it may have.

How do I find this out?

Has anyone else created a project like this and experenced the same?

I am on a clean build running WinXP Pro with SP2 - VS2005 with SP1 and the SQL Server 2005 tools.

Thank you.

I received the answer to the above problem here:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1195465&SiteID=1

Can't create a setup project for project referencing Microsoft.SqlServer.ManagedDTS

I have a very small project written in VB.Net 2005 using the SQL Server 2005 SSiS DTSx package.

I took a SQL Server 2000 dts package and using the SQL Server 3005 legacy tools migrated it so I could still use the package withing SQL 2005 until I can build one using BI/SSIS.

Anyway,I added the reference Microsoft.SqlServer.ManagedDTS so I could then use the Microsoft.SqlServer.Dts.Runtime so I can execute the commands:

Dim oApp As New Application
Dim oPkg As New Package
oPkg = oApp.LoadPackage(g_DTSx_Directory & "AOC copy Generic1 CSV to AOC_verify_file_1.dtsx", Nothing)
Dim oResults As DTSExecResult
oResults = oPkg.Execute

Ok. That works fine. Executes without a hitch. So now I try and create a setup project for this and I use the setup wizard.

During the creation of the setup project I get a message that states:
The following files may have dependencies that cannot be determined automatically. Please confirm that all dependencies have been added to the project.
C:\windows\system32\msxml6.dll

OK. The dll is part of the reference I mentioned above and I have no idea what other dependencies it may have.

How do I find this out?

Has anyone else created a project like this and experenced the same?

I am on a clean build running WinXP Pro with SP2 - VS2005 with SP1 and the SQL Server 2005 tools.

Thank you.

I received the answer to the above problem here:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1195465&SiteID=1

Can't Connect to Multiple SQL Instances over the Internet with SQL Browser Service

I recently setup mutliple instances of SQL Server Express at my office. I have 1 default instance, and two named instances. I can connect to the named instance of the default port of 1433 with Microsoft SQL Management Studio Express, however the other instances on dynamic TCP ports can not be accessed by the instance name over the internet. I have to specify the dynamic TCP port in this form: xxx.uconn.edu/SQLTEST, Port number. My current thinking is that the SQL Browser service should tell Management Studio Express what dynamic port number each SQL instance is listening to. Any ideas?

hi,

CTJohn23 wrote:

I recently setup mutliple instances of SQL Server Express at my office. I have 1 default instance, and two named instances. I can connect to the named instance of the default port of 1433 with Microsoft SQL Management Studio Express,

TCP/IP 1433 is usually reserved for the default instance...

however the other instances on dynamic TCP ports can not be accessed by the instance name over the internet. I have to specify the dynamic TCP port in this form: xxx.uconn.edu/SQLTEST, Port number. My current thinking is that the SQL Browser service should tell Management Studio Express what dynamic port number each SQL instance is listening to. Any ideas?

the SQLBrowser can not "work" over the internet in that way... all enlistment for instance presence are available via an UDP broadcast call on the local area, when no firewall action is involved...

don't know if the "tool" still relies on SQLBrowseConnect ODBC function, like SQL Server 7.0 and 2000 ListAvailableServer used it, an ODBC function (SQLBrowseConnect()) provided by ODBC libraries installed by Mdac;
this is a mechanism working in broadcast calls, which result never are conclusive and consistent, becouse results are influenced of various servers's answer states, answer time, etc.

Until Mdac 2.5, SQLBrowseConnect function works based on a NetBIOS broadcast, on which SQL Servers respond (Default protocol for SQL Server 7.0), while in SQL Server 2000 the rules changed, because the default client protocol changed to TCP/IP and now a UDP broadcast is used, beside a NetBIOS broadcast, listening on port 1434:
which is using a UDP broadcast on port 1434, if instance do not listen or not respond on time they will not be part of the enumeration.

Some basic rules for 7.0 are:
- SQL Servers have to be running on Windows NT or Windows 2000 and have to listen on Named Pipes, that is why in 7.0 Windows 9x SQL Servers will never show up, because they do not listen on Named Pipes.
- The SQL Server has to be running in order to respond on the broadcast. There is a gray window of 15 minutes after shutdown, where a browse master in the domain may respond on the broadcast and answer.
- If you have routers in your network, that do not pass on NetBIOS broadcasts, this might limit your scope of the broadcast.
- Only servers within the same NT domain (or trust) will get enumerated.

In SQL Server 2000 using MDAC 2.6 this changes a little, because now the default protocol has been changed to be TCP/IP sockets and instead of a NetBIOS broadcast, they use a TCP UDP to detect the servers. The same logic still applies roughly.
- SQL Server that are running
- SQL Server that listening on TCP/IP
- Running on Windows NT or Windows 2000 or Windows 9x
- If you use routers and these are configured not to pass UDP broadcasts, only machines within the same subnet show up.

Upgrading to Service Pack 2 of SQL Server 2000 is required in order to have .ListAvailableServer method to work properly, becouse precding release of Sql-DMO Components of Sql Server 2000 present a bug in this area.

Courtesy of Mr. Gert E.R. Drapers
further Information at
http://sqldev.net/misc.htm

The Service Pack 3a introduced some new amenity in order to prevent MSDE 2000 to be hit by Internet worms like Slammer and Saphire virus and to increase security, so that Microsoft decided to default for disabling SuperSockets Network Protocols on new MSDE 2000 installation.
Instances of SQL Server 2000 SP3a or MSDE 2000 SP3a will stop listening on UDP port 1434 when they are configured to not listen on any network protocols. This will stop enlisting these servers.

Cant connect to MSDE on XPSP1

We are writing a setup program for a customer that requires a MSDE
installation.
Using the following flags for the MSDE setup.exe:
SAPWD = "password" SECURITYMODE=SQL
The setup complete successfully, we are restarting the installed machine
(SQL services restarts as well)
But we cannot connect to the MSDE from any enterprise manager (Enterprise,
Developer versions)
This happens only when the MSDE installed on a WindowsXP SP1 machine.
Can someone help us solve this problem?
Thanks,
Shif
It may be that you don't have any network protocols enabled for MSDE. Run
the tool svrnetcn.exe (you'll find it in C:\Program Files\Microsoft SQL
Server\80\Tools\Binn) and check to make sure that you have the necessary
protocols enabled.
Jim
"Shif Arad" <shif@.inter.net.il> wrote in message
news:Om8nd%23vJEHA.2604@.tk2msftngp13.phx.gbl...
> We are writing a setup program for a customer that requires a MSDE
> installation.
> Using the following flags for the MSDE setup.exe:
> SAPWD = "password" SECURITYMODE=SQL
>
> The setup complete successfully, we are restarting the installed machine
> (SQL services restarts as well)
> But we cannot connect to the MSDE from any enterprise manager (Enterprise,
> Developer versions)
> This happens only when the MSDE installed on a WindowsXP SP1 machine.
>
> Can someone help us solve this problem?
> Thanks,
> Shif
>

Cant connect to MSDE on XPSP1

We are writing a setup program for a customer that requires a MSDE
installation.
Using the following flags for the MSDE setup.exe:
SAPWD = "password" SECURITYMODE=SQL
The setup complete successfully, we are restarting the installed machine
(SQL services restarts as well)
But we cannot connect to the MSDE from any enterprise manager
(Enterprise,Developer versions)
This happens only when the MSDE installed on a WindowsXP SP1 machine.
Can someone help us solve this problem?
Thanks,
Shif
Verify that the MSDE is listening on TCP/IP. Check the NT Application logs
after MSDE is started.
If it's only listening on Shared Memory, then only local connections will
succeed.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Hi,
How can i change this option AND in what menu should i look for it ?
Thank
Javier A. Junca Barreto.
Desarrollo de Sistemas
SICyA Software.
Web: www.sicya.com
Mail: desarrollo@.sicya.com
Tel: (57 1) 272 0738
|||MSDE doesn't ship with any utilities. So, you could change this via the
registry.
Check the following registry key on your server:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSDE Name Here
\MSSQLServer\SuperSocketNetLib
Add np and or tcp to the ProtocolList value.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Cant connect to MSDE on XPSP1

We are writing a setup program for a customer that requires a MSDE
installation.
Using the following flags for the MSDE setup.exe:
SAPWD = "password" SECURITYMODE=SQL
The setup complete successfully, we are restarting the installed machine
(SQL services restarts as well)
But we cannot connect to the MSDE from any enterprise manager
(Enterprise,Developer versions)
This happens only when the MSDE installed on a WindowsXP SP1 machine.
Can someone help us solve this problem?
Thanks,
ShifVerify that the MSDE is listening on TCP/IP. Check the NT Application logs
after MSDE is started.
If it's only listening on Shared Memory, then only local connections will
succeed.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi,
How can i change this option AND in what menu should i look for it ?
Thank
Javier A. Junca Barreto.
Desarrollo de Sistemas
SICyA Software.
Web: www.sicya.com
Mail: desarrollo@.sicya.com
Tel: (57 1) 272 0738|||MSDE doesn't ship with any utilities. So, you could change this via the
registry.
Check the following registry key on your server:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL Server\MSDE Name Here
\MSSQLServer\SuperSocketNetLib
Add np and or tcp to the ProtocolList value.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.