credential problem with sp3a setup

for anybody interested in this issue. The problem was
that the account used for the setup was in a different
domain than the server domain
>--Original Message--
>We just installed a SQL 2000 instance in a 2 nodes W2003
>cluster. The services are running with a domain account
>which is local administrator on both nodes. When we
start
>the setup for the SQL SP3 on the active node, we get to
>the remote setup window, where it asks username,
pasword,
>and domain for the setup on both cluster nodes, we enter
>the info about the same domain account we used for the
>SQL2K setup, if gets backs saying "The caller is not the
>owner of the desired credentials", and won't let us
>continue. Any idea ?
>.
>
I am having the same problem. In my company servers are on one domain and
user accounts are on a different domain. How would you work around this
problem?
thanks
Mike
"anonymous@.discussions.microsoft.com" wrote:

> for anybody interested in this issue. The problem was
> that the account used for the setup was in a different
> domain than the server domain
> start
> pasword,
>

Creation of a Setup Project

Is possible to create a Setup Project of a Reporting Services Project to install it in another Server ?
You may be better asking this Q in the reporting services newsgroup as this
group deals with Replication.
"Asphart" <anonymous@.discussions.microsoft.com> wrote in message
news:EA5A329A-9D6D-4E75-9721-4691A19E8A68@.microsoft.com...
> Is possible to create a Setup Project of a Reporting Services Project to
install it in another Server ?

creating triggers in transactional replication on the subscriber side

Hi all

i have setup default transactional replication using locat distributor scheme. I need to create triggers on tables at subscriber side. Can this be done using transaction replication?

Thanks,

Arslan.

are these triggers defined at the publisher, or were you wanting to create new triggers? Assuming the latter, you can put them in a SQL file and reference @.post_snapshot_script in sp_addpublication.|||

If what you would like to do is to replicate triggers defined on the published table, you can take a look at @.schema_option 0x100 in sp_addarticle. If you are using UI, there is also a "copy user triggers" option in article properties dialog.

Peng

creating SQL at setup

I must install web applications on many servers
how can I create a MS SQL database at setup ?

thank youOne option is to script the db and use OSQL to execute the script.|||what is OSQL ?|||By using osql utility, you can run sql commands from command prompt.

You can run batch scripts that are saved in a text file, and also save the returned results in a text file.|||yes ... that's so unpracticle comparing to access :-))

thank you

Creating Linked Server issues

I have a Merge Replication Setup. With 3 computers. One computer acts has a central publisher. The 2nd one is a subscriber, and republishes its data to the 3rd computer. Every thing is being done using Windows Authentication method. the 1st PC has SQL SERVER 2000 (Enterprise Manager, the works). The other two are SQL Server MSDE (Rel. A). My process is up and running and works, but heres my issue.

I need to script the replication installation process out., For future installations on machines that will be located in remote parts of the world. The will reside on a secure DSL network.

Anyone familiar with Scripting Merge Replication knows that once you've run certain scripts/procedures on your subscriber, you have to run a final procedure on the publisher to activate or initiate the subscriber as a valid one, and the you can start the Merge Agent on the subscriber, and voila! you're good. The procdure you run is called sp_addmergesubscription . It goes something like this :

BEGIN
exec sp_addmergesubscription @.publication = @.publicationname, @.subscriber = @.servername, @.subscriber_db = @.Attachedbname, @.subscription_type = N'pull', @.subscriber_type = N'global', @.subscription_priority = 56.250000, @.sync_type = N'automatic'
END

My intention was to embed this system in a stored proc on the publisher and then call it remotely from the subscriber, before starting the Agent. IT FAILS!!! This is my proc:

Create Procedure RunSp_AM_subscription(@.servername Varchar(30), @.IAdbname Varchar(20), @.Attachedbname Varchar(20))
AS

DECLARE @.publicationname Varchar(30)
SET @.publicationname = 'REPUBLISH-'+@.IAdbname+''

BEGIN
exec sp_addmergesubscription @.publication = @.publicationname, @.subscriber = @.servername, @.subscriber_db = @.Attachedbname, @.subscription_type = N'pull', @.subscriber_type = N'global', @.subscription_priority = 56.250000, @.sync_type = N'automatic'
END

When I call it locally ot works fine, but not otherwise......... :eek:

When I try to create a linked server SQL Server seems to think that one already exists (because Replication has already created the said server as a remote server). I think the fact that I am not using SQL Authentication might be a problem too.

Does anyone have any ideas? I mean seriously, any suggestions on what to do. This is qute Urgent...........

Thanks.

'Walealso how would I even call the proc assuming I'm able to create the linked server.