i am new at this. but i need to do a calculation that has to sum a running
value or running value of a running value . here is my expression.
=sum((((Fields!PART_QTY_ON_HAND.Value
- runningvalue((Fields!REQUIREMENT.Value), sum, "tbl1grp3")
* Fields!Temp_Part_Cost.Value ) + .005) * Fields!ANNUAL_CARRYING_RATE.
Value / 1200))
anyone have another suggestion or at least tell me that it can not be done.
thanx, kerries
--
Message posted via http://www.sqlmonster.comKerrie,
I'm not sure what you are asking here. In principle the expression
looks fine although I think your parantheses are in the wrong place. If
you are after a running total of this expression, I just tried a
RunningValue on a ReportItems object, but it didn't like it.
I'd suggest it would be more efficient to try and do this in the SQL
query if you can.
Chris
Kerrie S via SQLMonster.com wrote:
> i am new at this. but i need to do a calculation that has to sum a
> running value or running value of a running value . here is my
> expression.
> =sum((((Fields!PART_QTY_ON_HAND.Value
> - runningvalue((Fields!REQUIREMENT.Value), sum, "tbl1grp3")
> * Fields!Temp_Part_Cost.Value ) + .005) *
> Fields!ANNUAL_CARRYING_RATE. Value / 1200))
> anyone have another suggestion or at least tell me that it can not be
> done. thanx, kerries
Showing posts with label running. Show all posts
Showing posts with label running. Show all posts
Monday, March 19, 2012
Another SSIS Package Validation Question
We are going to be running a package repeatedly 24/7. The same package against the same data store, filtered using a "stageFlag" so as not to read rows previously processed. We have various timing statistics and have yet to fine tune; but on the surface it appears that it takes approximately three minutes to validate and another three minutes to run. If we have no additional data on the second run it still takes three minutes to complete - to do nothing but skip rows already processed.
Is it possible to set this up to run repeatedly without the validation on each iteration?
Any ideas as to how this would be accomplished would be greatly appreciated.
David,
Try setting DelayValidation=TRUE.
-Jamie
|||I thought this only delayed validation until later - that it still had to be validated before execution. I want it to validate once and then run forever. I will check it out again; but if you've understood my request and could respond that would be great.|||
No this is not possible. We always validate before an execution because the package doesn't "know" that nothing has been changed externally.
Matt
|||Matt,
A small question. If DelayValidation=FALSE will a task get validated twice. i.e. once at package startup and once immediately prior to the task firing? Or is it one or the other?
I only ask because I'm sure I've seen situations where setting DelayValidation=TRUE on a task causes the whole package to run quicker. Perhaps I was mistaken...
Thanks
Jamie
|||Hi Jamie,
Setting DelayValidation to false does cause an extra validation to occur because we always validate right before we execute but if delay validation is false then we also validate it up front. You might wonder why we do this since it does slow package execution. The answer is so we catch problems before the package runs for a long time. If you had a package that took 8 hours to run then it would be very useful to catch the error in the first validation pass than to wait until 7 hours had passed before getting to the task that would fail validation, but we give the option to turn it off as needed.
Matt
|||Dear Matt,
I also have a problem about Pre-Execution Phase that it takes very long time. (Some packages have been taken around 2 minutes, but some is less, and some package could not start execute phase, so I disable it)
Could I have any solution to solve this?
Thank you very much for your help
Nop
Another SSIS Package Validation Question
We are going to be running a package repeatedly 24/7. The same package against the same data store, filtered using a "stageFlag" so as not to read rows previously processed. We have various timing statistics and have yet to fine tune; but on the surface it appears that it takes approximately three minutes to validate and another three minutes to run. If we have no additional data on the second run it still takes three minutes to complete - to do nothing but skip rows already processed.
Is it possible to set this up to run repeatedly without the validation on each iteration?
Any ideas as to how this would be accomplished would be greatly appreciated.
David,
Try setting DelayValidation=TRUE.
-Jamie
|||I thought this only delayed validation until later - that it still had to be validated before execution. I want it to validate once and then run forever. I will check it out again; but if you've understood my request and could respond that would be great.|||No this is not possible. We always validate before an execution because the package doesn't "know" that nothing has been changed externally.
Matt
|||Matt,
A small question. If DelayValidation=FALSE will a task get validated twice. i.e. once at package startup and once immediately prior to the task firing? Or is it one or the other?
I only ask because I'm sure I've seen situations where setting DelayValidation=TRUE on a task causes the whole package to run quicker. Perhaps I was mistaken...
Thanks
Jamie
|||Hi Jamie,
Setting DelayValidation to false does cause an extra validation to occur because we always validate right before we execute but if delay validation is false then we also validate it up front. You might wonder why we do this since it does slow package execution. The answer is so we catch problems before the package runs for a long time. If you had a package that took 8 hours to run then it would be very useful to catch the error in the first validation pass than to wait until 7 hours had passed before getting to the task that would fail validation, but we give the option to turn it off as needed.
Matt
|||Dear Matt,
I also have a problem about Pre-Execution Phase that it takes very long time. (Some packages have been taken around 2 minutes, but some is less, and some package could not start execute phase, so I disable it)
Could I have any solution to solve this?
Thank you very much for your help
Nop
Another Snap shot for publication is running ?
i was doing replication on SQL 7, both my pulisher and subscriber was SQL 7
and the replicatoin was happening without any problem.Then i upgraded it to
SQL 2000 and restore the backup which was taken on SQL7.
After that when i am starting my agent then it is giving thie error "ANOTHER
SNAPSHOT AGENT FOR THE PUBLICATION IS RUNNING"
Please let me know hot to fix this problem as my complete setup is down.
Thanks & Regards
Asif
There are some reports that this was caused by an incomplete application of
a SQL 7 SP.
With this in mind, perhaps the best option is to script out your
publication(s), and subscriber(s), and then drop them, disable replication,
reenable it, and rerun your publication and subscription scripts.
"Asif" <Asif@.discussions.microsoft.com> wrote in message
news:BCCBF6A0-3EFB-459F-9C58-A0FC19FF2F46@.microsoft.com...
> i was doing replication on SQL 7, both my pulisher and subscriber was SQL
7
> and the replicatoin was happening without any problem.Then i upgraded it
to
> SQL 2000 and restore the backup which was taken on SQL7.
> After that when i am starting my agent then it is giving thie error
"ANOTHER
> SNAPSHOT AGENT FOR THE PUBLICATION IS RUNNING"
> Please let me know hot to fix this problem as my complete setup is down.
> Thanks & Regards
> Asif
|||Thanks for the reply.
Our SQL servers are SQL 2000 from ground up. No SQL7 SPs should be around.
In fact, I eventually was able to reproduce it. The tricky option is on the
Snapshot tab on publication properties - If you check "Do not lock tables
during snapshot generation...", that's when it happened. Without check the
option, you get a normal sp_MSins.
But I still couldn't figure out what exactly this has helped not to block
the table.
Richard
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eO#6xBstEHA.2948@.TK2MSFTNGP15.phx.gbl...
> There are some reports that this was caused by an incomplete application
of
> a SQL 7 SP.
> With this in mind, perhaps the best option is to script out your
> publication(s), and subscriber(s), and then drop them, disable
replication,[vbcol=seagreen]
> reenable it, and rerun your publication and subscription scripts.
>
> "Asif" <Asif@.discussions.microsoft.com> wrote in message
> news:BCCBF6A0-3EFB-459F-9C58-A0FC19FF2F46@.microsoft.com...
SQL
> 7
> to
> "ANOTHER
>
|||It still locks the tables with that box checked. You can see the lock
requests if you watch.
"Richard Ding" wrote:
> Thanks for the reply.
> Our SQL servers are SQL 2000 from ground up. No SQL7 SPs should be around.
> In fact, I eventually was able to reproduce it. The tricky option is on the
> Snapshot tab on publication properties - If you check "Do not lock tables
> during snapshot generation...", that's when it happened. Without check the
> option, you get a normal sp_MSins.
> But I still couldn't figure out what exactly this has helped not to block
> the table.
>
> Richard
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eO#6xBstEHA.2948@.TK2MSFTNGP15.phx.gbl...
> of
> replication,
> SQL
>
>
and the replicatoin was happening without any problem.Then i upgraded it to
SQL 2000 and restore the backup which was taken on SQL7.
After that when i am starting my agent then it is giving thie error "ANOTHER
SNAPSHOT AGENT FOR THE PUBLICATION IS RUNNING"
Please let me know hot to fix this problem as my complete setup is down.
Thanks & Regards
Asif
There are some reports that this was caused by an incomplete application of
a SQL 7 SP.
With this in mind, perhaps the best option is to script out your
publication(s), and subscriber(s), and then drop them, disable replication,
reenable it, and rerun your publication and subscription scripts.
"Asif" <Asif@.discussions.microsoft.com> wrote in message
news:BCCBF6A0-3EFB-459F-9C58-A0FC19FF2F46@.microsoft.com...
> i was doing replication on SQL 7, both my pulisher and subscriber was SQL
7
> and the replicatoin was happening without any problem.Then i upgraded it
to
> SQL 2000 and restore the backup which was taken on SQL7.
> After that when i am starting my agent then it is giving thie error
"ANOTHER
> SNAPSHOT AGENT FOR THE PUBLICATION IS RUNNING"
> Please let me know hot to fix this problem as my complete setup is down.
> Thanks & Regards
> Asif
|||Thanks for the reply.
Our SQL servers are SQL 2000 from ground up. No SQL7 SPs should be around.
In fact, I eventually was able to reproduce it. The tricky option is on the
Snapshot tab on publication properties - If you check "Do not lock tables
during snapshot generation...", that's when it happened. Without check the
option, you get a normal sp_MSins.
But I still couldn't figure out what exactly this has helped not to block
the table.
Richard
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eO#6xBstEHA.2948@.TK2MSFTNGP15.phx.gbl...
> There are some reports that this was caused by an incomplete application
of
> a SQL 7 SP.
> With this in mind, perhaps the best option is to script out your
> publication(s), and subscriber(s), and then drop them, disable
replication,[vbcol=seagreen]
> reenable it, and rerun your publication and subscription scripts.
>
> "Asif" <Asif@.discussions.microsoft.com> wrote in message
> news:BCCBF6A0-3EFB-459F-9C58-A0FC19FF2F46@.microsoft.com...
SQL
> 7
> to
> "ANOTHER
>
|||It still locks the tables with that box checked. You can see the lock
requests if you watch.
"Richard Ding" wrote:
> Thanks for the reply.
> Our SQL servers are SQL 2000 from ground up. No SQL7 SPs should be around.
> In fact, I eventually was able to reproduce it. The tricky option is on the
> Snapshot tab on publication properties - If you check "Do not lock tables
> during snapshot generation...", that's when it happened. Without check the
> option, you get a normal sp_MSins.
> But I still couldn't figure out what exactly this has helped not to block
> the table.
>
> Richard
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:eO#6xBstEHA.2948@.TK2MSFTNGP15.phx.gbl...
> of
> replication,
> SQL
>
>
Sunday, March 11, 2012
another question
Hi guys,
please create a table in tempdb running following
USE tempdb
CREATE TABLE delete_me (c1 int, c2 int )
INSERT delete_me (c1, c2)
SELECT 1, 1 UNION SELECT 2, 2 UNION SELECT 3, 3 UNION SELECT 4, 4
Then running the script below you can get (I do) the error message :
Server: Msg 207, Level 16, State 1, Line 1
Invalid column name 'c3'.
But sometimes it works. The workaround seems to be to wrap UPDATE statement
up into EXEC, - it works always. Why is that?
BEGIN TRAN
ALTER TABLE delete_me
ADD c3 int
-- EXEC ('UPDATE delete_me SET c3 = 0')
UPDATE delete_me SET c3 = 0
ALTER TABLE delete_me
ALTER COLUMN c3 int NOT NULL
ROLLBACK TRAN
Thanks
AlexThats quite a normal behaviour. Object resolution takes place if the
object is already know so, this will fail due to the non existing
column. Look for
http://msdn.microsoft.com/library/d...>
_07_5wa6.asp
"Note Deferred Name Resolution can only be used when you reference
nonexistent table objects. All other objects must exist at the time the
stored procedure is created. For example, when you reference an
existing table in a stored procedure you cannot list nonexistent
columns for that table."
HTH, Jens Suessmeyer.|||AlexM
What is your SQL Server version?
It worked fine on my workstation (SS2000,SP3,Personal Edition)
"AlexM" <alex_remove_this_mak@.telus.net> wrote in message
news:CHYDf.157789$AP5.28253@.edtnps84...
> Hi guys,
> please create a table in tempdb running following
> USE tempdb
> CREATE TABLE delete_me (c1 int, c2 int )
> INSERT delete_me (c1, c2)
> SELECT 1, 1 UNION SELECT 2, 2 UNION SELECT 3, 3 UNION SELECT 4, 4
> Then running the script below you can get (I do) the error message :
> Server: Msg 207, Level 16, State 1, Line 1
> Invalid column name 'c3'.
> But sometimes it works. The workaround seems to be to wrap UPDATE
> statement up into EXEC, - it works always. Why is that?
>
> BEGIN TRAN
> ALTER TABLE delete_me
> ADD c3 int
> -- EXEC ('UPDATE delete_me SET c3 = 0')
> UPDATE delete_me SET c3 = 0
> ALTER TABLE delete_me
> ALTER COLUMN c3 int NOT NULL
>
> ROLLBACK TRAN
>
> Thanks
> Alex
>|||Thanks Jens, that note apparently slipped my mind ;-)
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1138778592.061349.312360@.o13g2000cwo.googlegroups.com...
> Thats quite a normal behaviour. Object resolution takes place if the
> object is already know so, this will fail due to the non existing
> column. Look for
> http://msdn.microsoft.com/library/d...
es_07_5wa6.asp
> "Note Deferred Name Resolution can only be used when you reference
> nonexistent table objects. All other objects must exist at the time the
> stored procedure is created. For example, when you reference an
> existing table in a stored procedure you cannot list nonexistent
> columns for that table."
>
> HTH, Jens Suessmeyer.
>|||ss2000, enterprise & developer, sp4
Jens pointed to the note which explains clearly why it happens. What it
worries me though that this behaviour is not consistent. Most of the tine it
acts according to BOL and that particular note, but sometimes the resolution
stage comes through with flying colors when referencing a missing column for
existing table. But this is a bit different story...
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eL4xwIwJGHA.3332@.TK2MSFTNGP11.phx.gbl...
> AlexM
> What is your SQL Server version?
> It worked fine on my workstation (SS2000,SP3,Personal Edition)
>
> "AlexM" <alex_remove_this_mak@.telus.net> wrote in message
> news:CHYDf.157789$AP5.28253@.edtnps84...
>
please create a table in tempdb running following
USE tempdb
CREATE TABLE delete_me (c1 int, c2 int )
INSERT delete_me (c1, c2)
SELECT 1, 1 UNION SELECT 2, 2 UNION SELECT 3, 3 UNION SELECT 4, 4
Then running the script below you can get (I do) the error message :
Server: Msg 207, Level 16, State 1, Line 1
Invalid column name 'c3'.
But sometimes it works. The workaround seems to be to wrap UPDATE statement
up into EXEC, - it works always. Why is that?
BEGIN TRAN
ALTER TABLE delete_me
ADD c3 int
-- EXEC ('UPDATE delete_me SET c3 = 0')
UPDATE delete_me SET c3 = 0
ALTER TABLE delete_me
ALTER COLUMN c3 int NOT NULL
ROLLBACK TRAN
Thanks
AlexThats quite a normal behaviour. Object resolution takes place if the
object is already know so, this will fail due to the non existing
column. Look for
http://msdn.microsoft.com/library/d...>
_07_5wa6.asp
"Note Deferred Name Resolution can only be used when you reference
nonexistent table objects. All other objects must exist at the time the
stored procedure is created. For example, when you reference an
existing table in a stored procedure you cannot list nonexistent
columns for that table."
HTH, Jens Suessmeyer.|||AlexM
What is your SQL Server version?
It worked fine on my workstation (SS2000,SP3,Personal Edition)
"AlexM" <alex_remove_this_mak@.telus.net> wrote in message
news:CHYDf.157789$AP5.28253@.edtnps84...
> Hi guys,
> please create a table in tempdb running following
> USE tempdb
> CREATE TABLE delete_me (c1 int, c2 int )
> INSERT delete_me (c1, c2)
> SELECT 1, 1 UNION SELECT 2, 2 UNION SELECT 3, 3 UNION SELECT 4, 4
> Then running the script below you can get (I do) the error message :
> Server: Msg 207, Level 16, State 1, Line 1
> Invalid column name 'c3'.
> But sometimes it works. The workaround seems to be to wrap UPDATE
> statement up into EXEC, - it works always. Why is that?
>
> BEGIN TRAN
> ALTER TABLE delete_me
> ADD c3 int
> -- EXEC ('UPDATE delete_me SET c3 = 0')
> UPDATE delete_me SET c3 = 0
> ALTER TABLE delete_me
> ALTER COLUMN c3 int NOT NULL
>
> ROLLBACK TRAN
>
> Thanks
> Alex
>|||Thanks Jens, that note apparently slipped my mind ;-)
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1138778592.061349.312360@.o13g2000cwo.googlegroups.com...
> Thats quite a normal behaviour. Object resolution takes place if the
> object is already know so, this will fail due to the non existing
> column. Look for
> http://msdn.microsoft.com/library/d...
es_07_5wa6.asp
> "Note Deferred Name Resolution can only be used when you reference
> nonexistent table objects. All other objects must exist at the time the
> stored procedure is created. For example, when you reference an
> existing table in a stored procedure you cannot list nonexistent
> columns for that table."
>
> HTH, Jens Suessmeyer.
>|||ss2000, enterprise & developer, sp4
Jens pointed to the note which explains clearly why it happens. What it
worries me though that this behaviour is not consistent. Most of the tine it
acts according to BOL and that particular note, but sometimes the resolution
stage comes through with flying colors when referencing a missing column for
existing table. But this is a bit different story...
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eL4xwIwJGHA.3332@.TK2MSFTNGP11.phx.gbl...
> AlexM
> What is your SQL Server version?
> It worked fine on my workstation (SS2000,SP3,Personal Edition)
>
> "AlexM" <alex_remove_this_mak@.telus.net> wrote in message
> news:CHYDf.157789$AP5.28253@.edtnps84...
>
Thursday, March 8, 2012
Another merge agent for the subscription(s) is running
Hi everyone,
We are trying to implement merge replication using a central subscriber
model. When testing this out on 4 test machines, everything seemed fine.
Now, we are running a live test alongside our old system. So far we have the
central subscriber up and running and one publisher. The central subscriber
is using a one-way pull subscription to fetch the data from the publisher.
It pulls data once an hour.
The problem is that after a day or two, things stop working, and the merge
agent keeps failing and retrying to start the merge. The error from the
agent history is:
"Another merge agent for the subscription(s) is running."
Once I stop and start the sql agent service on the publisher, things work
fine for another day or two.
So my question is, why is this happening? I haven't been able to find
anything on the web about this particular error, other than to try using
this:
"select spid from sysprocesses where program_name = 'Your_Agent_Name'"
"Kill <spid>"
The problem with this solution is that I get no results from the select
statement, so there's no process to kill.
We are using MSDE 2000 Release A on Windows 2000 boxes. Any help would be
greatly appreciated.
Thanks,
-Brian
You get this when you are using WSM or the ActiveX controls to manage a pull
subscription and you also have a merge agent running. I have also seen it
when you script out publications and run them in a test environment and
don't change all the parameters.
You have to try to isolate this rouge agent.
"Brian Newtz" <anonymous@.discussions.microsoft.com> wrote in message
news:OP9lCvmEEHA.1128@.TK2MSFTNGP11.phx.gbl...
> Hi everyone,
> We are trying to implement merge replication using a central subscriber
> model. When testing this out on 4 test machines, everything seemed fine.
> Now, we are running a live test alongside our old system. So far we have
the
> central subscriber up and running and one publisher. The central
subscriber
> is using a one-way pull subscription to fetch the data from the publisher.
> It pulls data once an hour.
> The problem is that after a day or two, things stop working, and the merge
> agent keeps failing and retrying to start the merge. The error from the
> agent history is:
> "Another merge agent for the subscription(s) is running."
> Once I stop and start the sql agent service on the publisher, things work
> fine for another day or two.
> So my question is, why is this happening? I haven't been able to find
> anything on the web about this particular error, other than to try using
> this:
> "select spid from sysprocesses where program_name = 'Your_Agent_Name'"
> "Kill <spid>"
> The problem with this solution is that I get no results from the select
> statement, so there's no process to kill.
> We are using MSDE 2000 Release A on Windows 2000 boxes. Any help would be
> greatly appreciated.
> Thanks,
> -Brian
>
>
|||this message is raised after we check the sysprocesses table to see if any
SPID exists for the same application name as the merge agent.
You should try to detemine if the spids are being orphaned even after you
stop the agent, if so we need to determine the cause of that.
thanks
gopal
|||Hilary, Gopal,
I'm not using WSM or ActiveX controls for the pull subscription. What I did
was script out the replication and changed things as necessary in the
scripts to install it on the live servers.
Gopal - like I said, my problem is that when I try to get the spid of the
agent, there are no results returned... so I'm at a loss as to what to try.
Any other suggestions?
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%23EG3DFnEEHA.3788@.TK2MSFTNGP10.phx.gbl...
> You get this when you are using WSM or the ActiveX controls to manage a
pull
> subscription and you also have a merge agent running. I have also seen it
> when you script out publications and run them in a test environment and
> don't change all the parameters.
> You have to try to isolate this rouge agent.
> "Brian Newtz" <anonymous@.discussions.microsoft.com> wrote in message
> news:OP9lCvmEEHA.1128@.TK2MSFTNGP11.phx.gbl...
> the
> subscriber
publisher.
merge
work
be
>
We are trying to implement merge replication using a central subscriber
model. When testing this out on 4 test machines, everything seemed fine.
Now, we are running a live test alongside our old system. So far we have the
central subscriber up and running and one publisher. The central subscriber
is using a one-way pull subscription to fetch the data from the publisher.
It pulls data once an hour.
The problem is that after a day or two, things stop working, and the merge
agent keeps failing and retrying to start the merge. The error from the
agent history is:
"Another merge agent for the subscription(s) is running."
Once I stop and start the sql agent service on the publisher, things work
fine for another day or two.
So my question is, why is this happening? I haven't been able to find
anything on the web about this particular error, other than to try using
this:
"select spid from sysprocesses where program_name = 'Your_Agent_Name'"
"Kill <spid>"
The problem with this solution is that I get no results from the select
statement, so there's no process to kill.
We are using MSDE 2000 Release A on Windows 2000 boxes. Any help would be
greatly appreciated.
Thanks,
-Brian
You get this when you are using WSM or the ActiveX controls to manage a pull
subscription and you also have a merge agent running. I have also seen it
when you script out publications and run them in a test environment and
don't change all the parameters.
You have to try to isolate this rouge agent.
"Brian Newtz" <anonymous@.discussions.microsoft.com> wrote in message
news:OP9lCvmEEHA.1128@.TK2MSFTNGP11.phx.gbl...
> Hi everyone,
> We are trying to implement merge replication using a central subscriber
> model. When testing this out on 4 test machines, everything seemed fine.
> Now, we are running a live test alongside our old system. So far we have
the
> central subscriber up and running and one publisher. The central
subscriber
> is using a one-way pull subscription to fetch the data from the publisher.
> It pulls data once an hour.
> The problem is that after a day or two, things stop working, and the merge
> agent keeps failing and retrying to start the merge. The error from the
> agent history is:
> "Another merge agent for the subscription(s) is running."
> Once I stop and start the sql agent service on the publisher, things work
> fine for another day or two.
> So my question is, why is this happening? I haven't been able to find
> anything on the web about this particular error, other than to try using
> this:
> "select spid from sysprocesses where program_name = 'Your_Agent_Name'"
> "Kill <spid>"
> The problem with this solution is that I get no results from the select
> statement, so there's no process to kill.
> We are using MSDE 2000 Release A on Windows 2000 boxes. Any help would be
> greatly appreciated.
> Thanks,
> -Brian
>
>
|||this message is raised after we check the sysprocesses table to see if any
SPID exists for the same application name as the merge agent.
You should try to detemine if the spids are being orphaned even after you
stop the agent, if so we need to determine the cause of that.
thanks
gopal
|||Hilary, Gopal,
I'm not using WSM or ActiveX controls for the pull subscription. What I did
was script out the replication and changed things as necessary in the
scripts to install it on the live servers.
Gopal - like I said, my problem is that when I try to get the spid of the
agent, there are no results returned... so I'm at a loss as to what to try.
Any other suggestions?
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:%23EG3DFnEEHA.3788@.TK2MSFTNGP10.phx.gbl...
> You get this when you are using WSM or the ActiveX controls to manage a
pull
> subscription and you also have a merge agent running. I have also seen it
> when you script out publications and run them in a test environment and
> don't change all the parameters.
> You have to try to isolate this rouge agent.
> "Brian Newtz" <anonymous@.discussions.microsoft.com> wrote in message
> news:OP9lCvmEEHA.1128@.TK2MSFTNGP11.phx.gbl...
> the
> subscriber
publisher.
merge
work
be
>
Another merge agent for the subscription is running
When trying to replicate I get the message "Another merge agent for the
subscription(s) is running."
Both publisher/distributor and subscriber are SQL2K SP3.
There is no orphan process for the agent in the sysprocesses table.
I monitored the sysprocesses while the agent is connecting: for few
seconds several processes added to the list with the host name of the
subscriber, all start and gone in the same time, and then I get the
message above.
Please help
Yes, the ActiveX is in use, but only it. No other agent for the
subscription is running.
The publication was created by hand with the wizard.
Rgds,
Orr
Paul Ibison wrote:
> It doesn't sound as though this applies, but have you
> used the ActiveX control or windows synchronization
> manager to initiate a pull when the merge agent was
> already running? Was your publication created by hand
> from scripts?
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
|||Problem solved!
The application that is using the ActiveX was started twice
automatically when computer booted.
Thanks,
Orr
subscription(s) is running."
Both publisher/distributor and subscriber are SQL2K SP3.
There is no orphan process for the agent in the sysprocesses table.
I monitored the sysprocesses while the agent is connecting: for few
seconds several processes added to the list with the host name of the
subscriber, all start and gone in the same time, and then I get the
message above.
Please help
Yes, the ActiveX is in use, but only it. No other agent for the
subscription is running.
The publication was created by hand with the wizard.
Rgds,
Orr
Paul Ibison wrote:
> It doesn't sound as though this applies, but have you
> used the ActiveX control or windows synchronization
> manager to initiate a pull when the merge agent was
> already running? Was your publication created by hand
> from scripts?
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
|||Problem solved!
The application that is using the ActiveX was started twice
automatically when computer booted.
Thanks,
Orr
Another Domain
Hi,
We have SQL Server 7.0 running on NT 4.0 ( I know we should have moved on
but that's another story).
We also have VB6 apps accessing the SQL Server using Windows authentication
.
Until now only users within our domain needed to use the apps.
There are a number of NT security groups to which we add our users depending
on their required permission levels.
However we now have a situation where users from an external domain need
access to the VB6 apps. They will also need to synchronise data using merge
replication.
Is there a way of mapping such users to our NT Security groups even though
they are members of an external domain. There will be co-operation from the
administrators of the other domain.
We would rather stick with Windows Authentication rather than Mixed Mode.
Any help greatly appreciated.
DDHi
You would need to setup trusts between the 2 domains. This is done at OS
level. Get your admins to look if it is something they really want to do. An
external company, unless it is in the same legal entity group, should not be
trusted as you have no control over their admins.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave52" wrote:
> Hi,
> We have SQL Server 7.0 running on NT 4.0 ( I know we should have moved on
> but that's another story).
> We also have VB6 apps accessing the SQL Server using Windows authenticati
on.
> Until now only users within our domain needed to use the apps.
> There are a number of NT security groups to which we add our users dependi
ng
> on their required permission levels.
> However we now have a situation where users from an external domain need
> access to the VB6 apps. They will also need to synchronise data using mer
ge
> replication.
> Is there a way of mapping such users to our NT Security groups even though
> they are members of an external domain. There will be co-operation from th
e
> administrators of the other domain.
> We would rather stick with Windows Authentication rather than Mixed Mode.
> Any help greatly appreciated.
> DD
>|||The way I'd handle this is to create a local group on the SQL Server box tha
t
contains a global group from the remote domain. Then I'd simply give permiss
ions
inside SQL Server to this local group. For this to happen of course, there m
ust
be a trust between the domain that contains the SQL Server and the "external
"
domain that wants access to it.
HTH
Thomas
"Dave52" <Dave52@.discussions.microsoft.com> wrote in message
news:D40BC61F-A792-4442-BF6B-FF29BFAB9258@.microsoft.com...
> Hi,
> We have SQL Server 7.0 running on NT 4.0 ( I know we should have moved on
> but that's another story).
> We also have VB6 apps accessing the SQL Server using Windows authenticati
on.
> Until now only users within our domain needed to use the apps.
> There are a number of NT security groups to which we add our users dependi
ng
> on their required permission levels.
> However we now have a situation where users from an external domain need
> access to the VB6 apps. They will also need to synchronise data using mer
ge
> replication.
> Is there a way of mapping such users to our NT Security groups even though
> they are members of an external domain. There will be co-operation from th
e
> administrators of the other domain.
> We would rather stick with Windows Authentication rather than Mixed Mode.
> Any help greatly appreciated.
> DD
>
We have SQL Server 7.0 running on NT 4.0 ( I know we should have moved on
but that's another story).
We also have VB6 apps accessing the SQL Server using Windows authentication
.
Until now only users within our domain needed to use the apps.
There are a number of NT security groups to which we add our users depending
on their required permission levels.
However we now have a situation where users from an external domain need
access to the VB6 apps. They will also need to synchronise data using merge
replication.
Is there a way of mapping such users to our NT Security groups even though
they are members of an external domain. There will be co-operation from the
administrators of the other domain.
We would rather stick with Windows Authentication rather than Mixed Mode.
Any help greatly appreciated.
DDHi
You would need to setup trusts between the 2 domains. This is done at OS
level. Get your admins to look if it is something they really want to do. An
external company, unless it is in the same legal entity group, should not be
trusted as you have no control over their admins.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dave52" wrote:
> Hi,
> We have SQL Server 7.0 running on NT 4.0 ( I know we should have moved on
> but that's another story).
> We also have VB6 apps accessing the SQL Server using Windows authenticati
on.
> Until now only users within our domain needed to use the apps.
> There are a number of NT security groups to which we add our users dependi
ng
> on their required permission levels.
> However we now have a situation where users from an external domain need
> access to the VB6 apps. They will also need to synchronise data using mer
ge
> replication.
> Is there a way of mapping such users to our NT Security groups even though
> they are members of an external domain. There will be co-operation from th
e
> administrators of the other domain.
> We would rather stick with Windows Authentication rather than Mixed Mode.
> Any help greatly appreciated.
> DD
>|||The way I'd handle this is to create a local group on the SQL Server box tha
t
contains a global group from the remote domain. Then I'd simply give permiss
ions
inside SQL Server to this local group. For this to happen of course, there m
ust
be a trust between the domain that contains the SQL Server and the "external
"
domain that wants access to it.
HTH
Thomas
"Dave52" <Dave52@.discussions.microsoft.com> wrote in message
news:D40BC61F-A792-4442-BF6B-FF29BFAB9258@.microsoft.com...
> Hi,
> We have SQL Server 7.0 running on NT 4.0 ( I know we should have moved on
> but that's another story).
> We also have VB6 apps accessing the SQL Server using Windows authenticati
on.
> Until now only users within our domain needed to use the apps.
> There are a number of NT security groups to which we add our users dependi
ng
> on their required permission levels.
> However we now have a situation where users from an external domain need
> access to the VB6 apps. They will also need to synchronise data using mer
ge
> replication.
> Is there a way of mapping such users to our NT Security groups even though
> they are members of an external domain. There will be co-operation from th
e
> administrators of the other domain.
> We would rather stick with Windows Authentication rather than Mixed Mode.
> Any help greatly appreciated.
> DD
>
Another distribution agents for the Subcription
sql2k sp3
Im getting a message on replication that has been running
for a while:
Another distribution agent for the subscription(s) is
running. NOTE: The step was retried the requested number
of times (10) without succeeding. The step failed.
Any ideas?
ThanksOriginally posted by dschuster
sql2k sp3
Im getting a message on replication that has been running
for a while:
Another distribution agent for the subscription(s) is
running. NOTE: The step was retried the requested number
of times (10) without succeeding. The step failed.
Any ideas?
Thanks
What this means is that another replication step is running while this step was executed. Check all the steps that are Running in Replication Monitor -> Publishers/Subscribers and check if any other steps are running. If they are then you will have either wait for them to be done or you can force them to stop. Once all the steps are stopped then you can run your replication step.
Hope this helps
Im getting a message on replication that has been running
for a while:
Another distribution agent for the subscription(s) is
running. NOTE: The step was retried the requested number
of times (10) without succeeding. The step failed.
Any ideas?
ThanksOriginally posted by dschuster
sql2k sp3
Im getting a message on replication that has been running
for a while:
Another distribution agent for the subscription(s) is
running. NOTE: The step was retried the requested number
of times (10) without succeeding. The step failed.
Any ideas?
Thanks
What this means is that another replication step is running while this step was executed. Check all the steps that are Running in Replication Monitor -> Publishers/Subscribers and check if any other steps are running. If they are then you will have either wait for them to be done or you can force them to stop. Once all the steps are stopped then you can run your replication step.
Hope this helps
Wednesday, March 7, 2012
Anonymous connection to a remote server
I have a SQL server running on a Win2k Domain Controller set for Windows Aut
hentication only.
I have a Windows 2003 Web Edition server that is a member of the domain.
When permissions are correct I can open and update databases on the server f
rom the Web Edition server.
I want to allow anyone that hits a web site on the 2003 server to be able to
update a specific database on the SQL server. The
users on that site are running under the local IIS anonymous user id.
I tried the obvious and simple connection
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Ini
tial Catalog=WebRedirectLog;Data Source=ZEUS;
Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=ROY;Use Encryption for Data=False;
Tag with column collation when possible=False");
(which I expected to fail) and it did telling me
Microsoft OLE DB Provider for SQL Server error '80004005'
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Se
rver connection.
(I did NOT supply a userid in the call to ADODB.Connection.Open
What is the correct way to do one of the following.
1) - Allow all users (authenticated or not) to update a database?
2) - Set up the SQL server so that it can treat the 2003 local account (not
a domain account) as authenticated.
I do NOT want to allowed mixed mode authentication on this server.
Please bear in mind, I am still a novice at administering SQL, so please mak
e your response a little detailed.
Thanks
---
Roy Chastain
KMSystems, Inc.Hi Roy,
Welcome to MSDN newsgroup.
Regarding on the problem you mentioned, I think the it'll be a bit
difficult to meet all your requirement. Here are some of my understandings:
First, ASP will always impersonate the anonymous account( IIS's default
IUSR_machine account) if we enable anonymous access in our IIS virtual dir.
Then, when our asp page try accessing any protected resource, the
IUSR_machine account will be the authenticated and executing account of our
asp page's thread. Then, return back to the quesitons you mentioned:
==============
What is the correct way to do one of the following.
1) - Allow all users (authenticated or not) to update a database?
2) - Set up the SQL server so that it can treat the 2003 local account (not
a domain account) as authenticated
==============
1) I think the most standard means for allow all users to access db is to
use SQLServer Autehntcaiton(provide the username account in
connectionstring. This will require the SQLServer db to allow SQL
authentication. In fact, this is limited by the ASP , in asp.net we can
impersonate a certain fixed account so as to use t hat account to access
the database through integrated windows authentication.
2) If the webserver and SqlServer's database server is the same box, we
can simply grant the IIS's IUSR_MACHINE account the permisson to access
sqlserver db. However, as you said the DB server is a remote server to the
webserver, the IUSR_machine(local account ) on webserver is not valid on DB
server. For such scenario, there are two options:
a. use a Domain Account as your IIS virtual dir's anonymous account.
(Seems you didn't want to use DomainAcount
)
b. create a duplicate local account on the SQLServer 's machine which has
the same username and password with the IIS virtual dir's anonymous account
(on the webserver box). However, the IIS's default anonymous account(
IUSR_MACHINE) 'S password is controled by machine rather than ourself. So
we need to either explicitly set IUSR_MACHINE's password or create a
custom local account and replace the IUSR_machine as the virtual dir's
anonymous account.
Anyway, since there hasn't any means which will satisfy all the
requirement, we may need to make our decision according to the actual
situation. Please have a look of all the above things and feel free to let
us know if you have any ideas.
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Here is what I did and it is working and I think secure for what I want.
I created a new domain account and gave it insert and select access to the d
atabase.
I set anonymous access for the web site to that account.
I created a Application Pool on the web server and have it running under tha
t account.
I set the web site to use the newly created Application Pool.
From my point of view that gives all anonymous users of this one web site an
onymous access to the SQL database for the purposes of
inserting and selecting. I would have been easier is SQL supported some sor
t of anonymous access setting that said don't validate
this user, just let them do this, but...
Please let me know if you see any flaws in my reasoning.
Thanks
On Thu, 14 Apr 2005 05:18:35 GMT, v-schang@.online.microsoft.com (Steven Chen
g[MSFT]) wrote:
>Hi Roy,
>Welcome to MSDN newsgroup.
>Regarding on the problem you mentioned, I think the it'll be a bit
>difficult to meet all your requirement. Here are some of my understandings:
>First, ASP will always impersonate the anonymous account( IIS's default
>IUSR_machine account) if we enable anonymous access in our IIS virtual dir.
>Then, when our asp page try accessing any protected resource, the
>IUSR_machine account will be the authenticated and executing account of our
>asp page's thread. Then, return back to the quesitons you mentioned:
>==============
>What is the correct way to do one of the following.
>1) - Allow all users (authenticated or not) to update a database?
>2) - Set up the SQL server so that it can treat the 2003 local account (not
>a domain account) as authenticated
>==============
>1) I think the most standard means for allow all users to access db is to
>use SQLServer Autehntcaiton(provide the username account in
>connectionstring. This will require the SQLServer db to allow SQL
>authentication. In fact, this is limited by the ASP , in asp.net we can
>impersonate a certain fixed account so as to use t hat account to access
>the database through integrated windows authentication.
>2) If the webserver and SqlServer's database server is the same box, we
>can simply grant the IIS's IUSR_MACHINE account the permisson to access
>sqlserver db. However, as you said the DB server is a remote server to the
>webserver, the IUSR_machine(local account ) on webserver is not valid on DB
>server. For such scenario, there are two options:
>a. use a Domain Account as your IIS virtual dir's anonymous account.
>(Seems you didn't want to use DomainAcount )
>b. create a duplicate local account on the SQLServer 's machine which has
>the same username and password with the IIS virtual dir's anonymous account
>(on the webserver box). However, the IIS's default anonymous account(
>IUSR_MACHINE) 'S password is controled by machine rather than ourself. So
>we need to either explicitly set IUSR_MACHINE's password or create a
>custom local account and replace the IUSR_machine as the virtual dir's
>anonymous account.
>Anyway, since there hasn't any means which will satisfy all the
>requirement, we may need to make our decision according to the actual
>situation. Please have a look of all the above things and feel free to let
>us know if you have any ideas.
>Thanks,
>Steven Cheng
>Microsoft Online Support
>Get Secure! www.microsoft.com/security
>(This posting is provided "AS IS", with no warranties, and confers no
>rights.)
>
>
---
Roy Chastain
KMSystems, Inc.|||Glad to hear from you Roy,
I think it's OK since ASP will impersonate the authenticated user by
default( if allow anonymous then impersonate the anonymous user). And
using Integrated windows authentication at back end db is also what we
recommend.
BTW, is there any future action plan that you'll migrate your web
application from classic ASP to ASP.NET. The asp.net web app framework will
have more strong support for stable and high performance web application.
Also, as for security, the asp.net can let the asp.net running under the
process idenity (the application pool identity in IIS6) together with allow
anonymous in IIS. Thus, we can still keep the IIS's anonymous account as a
very restricted account.
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
hentication only.
I have a Windows 2003 Web Edition server that is a member of the domain.
When permissions are correct I can open and update databases on the server f
rom the Web Edition server.
I want to allow anyone that hits a web site on the 2003 server to be able to
update a specific database on the SQL server. The
users on that site are running under the local IIS anonymous user id.
I tried the obvious and simple connection
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Ini
tial Catalog=WebRedirectLog;Data Source=ZEUS;
Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation
ID=ROY;Use Encryption for Data=False;
Tag with column collation when possible=False");
(which I expected to fail) and it did telling me
Microsoft OLE DB Provider for SQL Server error '80004005'
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Se
rver connection.
(I did NOT supply a userid in the call to ADODB.Connection.Open
What is the correct way to do one of the following.
1) - Allow all users (authenticated or not) to update a database?
2) - Set up the SQL server so that it can treat the 2003 local account (not
a domain account) as authenticated.
I do NOT want to allowed mixed mode authentication on this server.
Please bear in mind, I am still a novice at administering SQL, so please mak
e your response a little detailed.
Thanks
---
Roy Chastain
KMSystems, Inc.Hi Roy,
Welcome to MSDN newsgroup.
Regarding on the problem you mentioned, I think the it'll be a bit
difficult to meet all your requirement. Here are some of my understandings:
First, ASP will always impersonate the anonymous account( IIS's default
IUSR_machine account) if we enable anonymous access in our IIS virtual dir.
Then, when our asp page try accessing any protected resource, the
IUSR_machine account will be the authenticated and executing account of our
asp page's thread. Then, return back to the quesitons you mentioned:
==============
What is the correct way to do one of the following.
1) - Allow all users (authenticated or not) to update a database?
2) - Set up the SQL server so that it can treat the 2003 local account (not
a domain account) as authenticated
==============
1) I think the most standard means for allow all users to access db is to
use SQLServer Autehntcaiton(provide the username account in
connectionstring. This will require the SQLServer db to allow SQL
authentication. In fact, this is limited by the ASP , in asp.net we can
impersonate a certain fixed account so as to use t hat account to access
the database through integrated windows authentication.
2) If the webserver and SqlServer's database server is the same box, we
can simply grant the IIS's IUSR_MACHINE account the permisson to access
sqlserver db. However, as you said the DB server is a remote server to the
webserver, the IUSR_machine(local account ) on webserver is not valid on DB
server. For such scenario, there are two options:
a. use a Domain Account as your IIS virtual dir's anonymous account.
(Seems you didn't want to use DomainAcount
)b. create a duplicate local account on the SQLServer 's machine which has
the same username and password with the IIS virtual dir's anonymous account
(on the webserver box). However, the IIS's default anonymous account(
IUSR_MACHINE) 'S password is controled by machine rather than ourself. So
we need to either explicitly set IUSR_MACHINE's password or create a
custom local account and replace the IUSR_machine as the virtual dir's
anonymous account.
Anyway, since there hasn't any means which will satisfy all the
requirement, we may need to make our decision according to the actual
situation. Please have a look of all the above things and feel free to let
us know if you have any ideas.
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Here is what I did and it is working and I think secure for what I want.
I created a new domain account and gave it insert and select access to the d
atabase.
I set anonymous access for the web site to that account.
I created a Application Pool on the web server and have it running under tha
t account.
I set the web site to use the newly created Application Pool.
From my point of view that gives all anonymous users of this one web site an
onymous access to the SQL database for the purposes of
inserting and selecting. I would have been easier is SQL supported some sor
t of anonymous access setting that said don't validate
this user, just let them do this, but...
Please let me know if you see any flaws in my reasoning.
Thanks
On Thu, 14 Apr 2005 05:18:35 GMT, v-schang@.online.microsoft.com (Steven Chen
g[MSFT]) wrote:
>Hi Roy,
>Welcome to MSDN newsgroup.
>Regarding on the problem you mentioned, I think the it'll be a bit
>difficult to meet all your requirement. Here are some of my understandings:
>First, ASP will always impersonate the anonymous account( IIS's default
>IUSR_machine account) if we enable anonymous access in our IIS virtual dir.
>Then, when our asp page try accessing any protected resource, the
>IUSR_machine account will be the authenticated and executing account of our
>asp page's thread. Then, return back to the quesitons you mentioned:
>==============
>What is the correct way to do one of the following.
>1) - Allow all users (authenticated or not) to update a database?
>2) - Set up the SQL server so that it can treat the 2003 local account (not
>a domain account) as authenticated
>==============
>1) I think the most standard means for allow all users to access db is to
>use SQLServer Autehntcaiton(provide the username account in
>connectionstring. This will require the SQLServer db to allow SQL
>authentication. In fact, this is limited by the ASP , in asp.net we can
>impersonate a certain fixed account so as to use t hat account to access
>the database through integrated windows authentication.
>2) If the webserver and SqlServer's database server is the same box, we
>can simply grant the IIS's IUSR_MACHINE account the permisson to access
>sqlserver db. However, as you said the DB server is a remote server to the
>webserver, the IUSR_machine(local account ) on webserver is not valid on DB
>server. For such scenario, there are two options:
>a. use a Domain Account as your IIS virtual dir's anonymous account.
>(Seems you didn't want to use DomainAcount
)>b. create a duplicate local account on the SQLServer 's machine which has
>the same username and password with the IIS virtual dir's anonymous account
>(on the webserver box). However, the IIS's default anonymous account(
>IUSR_MACHINE) 'S password is controled by machine rather than ourself. So
>we need to either explicitly set IUSR_MACHINE's password or create a
>custom local account and replace the IUSR_machine as the virtual dir's
>anonymous account.
>Anyway, since there hasn't any means which will satisfy all the
>requirement, we may need to make our decision according to the actual
>situation. Please have a look of all the above things and feel free to let
>us know if you have any ideas.
>Thanks,
>Steven Cheng
>Microsoft Online Support
>Get Secure! www.microsoft.com/security
>(This posting is provided "AS IS", with no warranties, and confers no
>rights.)
>
>
---
Roy Chastain
KMSystems, Inc.|||Glad to hear from you Roy,
I think it's OK since ASP will impersonate the authenticated user by
default( if allow anonymous then impersonate the anonymous user). And
using Integrated windows authentication at back end db is also what we
recommend.
BTW, is there any future action plan that you'll migrate your web
application from classic ASP to ASP.NET. The asp.net web app framework will
have more strong support for stable and high performance web application.
Also, as for security, the asp.net can let the asp.net running under the
process idenity (the application pool identity in IIS6) together with allow
anonymous in IIS. Thus, we can still keep the IIS's anonymous account as a
very restricted account.
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Anonymous connection to a remote server
I have a SQL server running on a Win2k Domain Controller set for Windows Authentication only.
I have a Windows 2003 Web Edition server that is a member of the domain.
When permissions are correct I can open and update databases on the server from the Web Edition server.
I want to allow anyone that hits a web site on the 2003 server to be able to update a specific database on the SQL server. The
users on that site are running under the local IIS anonymous user id.
I tried the obvious and simple connection
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=WebRedirectLog;Data Source=ZEUS;
Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=ROY;Use Encryption for Data=False;
Tag with column collation when possible=False");
(which I expected to fail) and it did telling me
Microsoft OLE DB Provider for SQL Server error '80004005'
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
(I did NOT supply a userid in the call to ADODB.Connection.Open
What is the correct way to do one of the following.
1) - Allow all users (authenticated or not) to update a database?
2) - Set up the SQL server so that it can treat the 2003 local account (not a domain account) as authenticated.
I do NOT want to allowed mixed mode authentication on this server.
Please bear in mind, I am still a novice at administering SQL, so please make your response a little detailed.
Thanks
Roy Chastain
KMSystems, Inc.
Hi Roy,
Welcome to MSDN newsgroup.
Regarding on the problem you mentioned, I think the it'll be a bit
difficult to meet all your requirement. Here are some of my understandings:
First, ASP will always impersonate the anonymous account( IIS's default
IUSR_machine account) if we enable anonymous access in our IIS virtual dir.
Then, when our asp page try accessing any protected resource, the
IUSR_machine account will be the authenticated and executing account of our
asp page's thread. Then, return back to the quesitons you mentioned:
==============
What is the correct way to do one of the following.
1) - Allow all users (authenticated or not) to update a database?
2) - Set up the SQL server so that it can treat the 2003 local account (not
a domain account) as authenticated
==============
1) I think the most standard means for allow all users to access db is to
use SQLServer Autehntcaiton(provide the username account in
connectionstring. This will require the SQLServer db to allow SQL
authentication. In fact, this is limited by the ASP , in asp.net we can
impersonate a certain fixed account so as to use t hat account to access
the database through integrated windows authentication.
2) If the webserver and SqlServer's database server is the same box, we
can simply grant the IIS's IUSR_MACHINE account the permisson to access
sqlserver db. However, as you said the DB server is a remote server to the
webserver, the IUSR_machine(local account ) on webserver is not valid on DB
server. For such scenario, there are two options:
a. use a Domain Account as your IIS virtual dir's anonymous account.
(Seems you didn't want to use DomainAcount )
b. create a duplicate local account on the SQLServer 's machine which has
the same username and password with the IIS virtual dir's anonymous account
(on the webserver box). However, the IIS's default anonymous account(
IUSR_MACHINE) 'S password is controled by machine rather than ourself. So
we need to either explicitly set IUSR_MACHINE's password or create a
custom local account and replace the IUSR_machine as the virtual dir's
anonymous account.
Anyway, since there hasn't any means which will satisfy all the
requirement, we may need to make our decision according to the actual
situation. Please have a look of all the above things and feel free to let
us know if you have any ideas.
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
|||Here is what I did and it is working and I think secure for what I want.
I created a new domain account and gave it insert and select access to the database.
I set anonymous access for the web site to that account.
I created a Application Pool on the web server and have it running under that account.
I set the web site to use the newly created Application Pool.
From my point of view that gives all anonymous users of this one web site anonymous access to the SQL database for the purposes of
inserting and selecting. I would have been easier is SQL supported some sort of anonymous access setting that said don't validate
this user, just let them do this, but...
Please let me know if you see any flaws in my reasoning.
Thanks
On Thu, 14 Apr 2005 05:18:35 GMT, v-schang@.online.microsoft.com (Steven Cheng[MSFT]) wrote:
>Hi Roy,
>Welcome to MSDN newsgroup.
>Regarding on the problem you mentioned, I think the it'll be a bit
>difficult to meet all your requirement. Here are some of my understandings:
>First, ASP will always impersonate the anonymous account( IIS's default
>IUSR_machine account) if we enable anonymous access in our IIS virtual dir.
>Then, when our asp page try accessing any protected resource, the
>IUSR_machine account will be the authenticated and executing account of our
>asp page's thread. Then, return back to the quesitons you mentioned:
>==============
>What is the correct way to do one of the following.
>1) - Allow all users (authenticated or not) to update a database?
>2) - Set up the SQL server so that it can treat the 2003 local account (not
>a domain account) as authenticated
>==============
>1) I think the most standard means for allow all users to access db is to
>use SQLServer Autehntcaiton(provide the username account in
>connectionstring. This will require the SQLServer db to allow SQL
>authentication. In fact, this is limited by the ASP , in asp.net we can
>impersonate a certain fixed account so as to use t hat account to access
>the database through integrated windows authentication.
>2) If the webserver and SqlServer's database server is the same box, we
>can simply grant the IIS's IUSR_MACHINE account the permisson to access
>sqlserver db. However, as you said the DB server is a remote server to the
>webserver, the IUSR_machine(local account ) on webserver is not valid on DB
>server. For such scenario, there are two options:
>a. use a Domain Account as your IIS virtual dir's anonymous account.
>(Seems you didn't want to use DomainAcount )
>b. create a duplicate local account on the SQLServer 's machine which has
>the same username and password with the IIS virtual dir's anonymous account
>(on the webserver box). However, the IIS's default anonymous account(
>IUSR_MACHINE) 'S password is controled by machine rather than ourself. So
>we need to either explicitly set IUSR_MACHINE's password or create a
>custom local account and replace the IUSR_machine as the virtual dir's
>anonymous account.
>Anyway, since there hasn't any means which will satisfy all the
>requirement, we may need to make our decision according to the actual
>situation. Please have a look of all the above things and feel free to let
>us know if you have any ideas.
>Thanks,
>Steven Cheng
>Microsoft Online Support
>Get Secure! www.microsoft.com/security
>(This posting is provided "AS IS", with no warranties, and confers no
>rights.)
>
>
Roy Chastain
KMSystems, Inc.
|||Glad to hear from you Roy,
I think it's OK since ASP will impersonate the authenticated user by
default( if allow anonymous then impersonate the anonymous user). And
using Integrated windows authentication at back end db is also what we
recommend.
BTW, is there any future action plan that you'll migrate your web
application from classic ASP to ASP.NET. The asp.net web app framework will
have more strong support for stable and high performance web application.
Also, as for security, the asp.net can let the asp.net running under the
process idenity (the application pool identity in IIS6) together with allow
anonymous in IIS. Thus, we can still keep the IIS's anonymous account as a
very restricted account.
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
I have a Windows 2003 Web Edition server that is a member of the domain.
When permissions are correct I can open and update databases on the server from the Web Edition server.
I want to allow anyone that hits a web site on the 2003 server to be able to update a specific database on the SQL server. The
users on that site are running under the local IIS anonymous user id.
I tried the obvious and simple connection
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=WebRedirectLog;Data Source=ZEUS;
Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=ROY;Use Encryption for Data=False;
Tag with column collation when possible=False");
(which I expected to fail) and it did telling me
Microsoft OLE DB Provider for SQL Server error '80004005'
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
(I did NOT supply a userid in the call to ADODB.Connection.Open
What is the correct way to do one of the following.
1) - Allow all users (authenticated or not) to update a database?
2) - Set up the SQL server so that it can treat the 2003 local account (not a domain account) as authenticated.
I do NOT want to allowed mixed mode authentication on this server.
Please bear in mind, I am still a novice at administering SQL, so please make your response a little detailed.
Thanks
Roy Chastain
KMSystems, Inc.
Hi Roy,
Welcome to MSDN newsgroup.
Regarding on the problem you mentioned, I think the it'll be a bit
difficult to meet all your requirement. Here are some of my understandings:
First, ASP will always impersonate the anonymous account( IIS's default
IUSR_machine account) if we enable anonymous access in our IIS virtual dir.
Then, when our asp page try accessing any protected resource, the
IUSR_machine account will be the authenticated and executing account of our
asp page's thread. Then, return back to the quesitons you mentioned:
==============
What is the correct way to do one of the following.
1) - Allow all users (authenticated or not) to update a database?
2) - Set up the SQL server so that it can treat the 2003 local account (not
a domain account) as authenticated
==============
1) I think the most standard means for allow all users to access db is to
use SQLServer Autehntcaiton(provide the username account in
connectionstring. This will require the SQLServer db to allow SQL
authentication. In fact, this is limited by the ASP , in asp.net we can
impersonate a certain fixed account so as to use t hat account to access
the database through integrated windows authentication.
2) If the webserver and SqlServer's database server is the same box, we
can simply grant the IIS's IUSR_MACHINE account the permisson to access
sqlserver db. However, as you said the DB server is a remote server to the
webserver, the IUSR_machine(local account ) on webserver is not valid on DB
server. For such scenario, there are two options:
a. use a Domain Account as your IIS virtual dir's anonymous account.
(Seems you didn't want to use DomainAcount
)b. create a duplicate local account on the SQLServer 's machine which has
the same username and password with the IIS virtual dir's anonymous account
(on the webserver box). However, the IIS's default anonymous account(
IUSR_MACHINE) 'S password is controled by machine rather than ourself. So
we need to either explicitly set IUSR_MACHINE's password or create a
custom local account and replace the IUSR_machine as the virtual dir's
anonymous account.
Anyway, since there hasn't any means which will satisfy all the
requirement, we may need to make our decision according to the actual
situation. Please have a look of all the above things and feel free to let
us know if you have any ideas.
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
|||Here is what I did and it is working and I think secure for what I want.
I created a new domain account and gave it insert and select access to the database.
I set anonymous access for the web site to that account.
I created a Application Pool on the web server and have it running under that account.
I set the web site to use the newly created Application Pool.
From my point of view that gives all anonymous users of this one web site anonymous access to the SQL database for the purposes of
inserting and selecting. I would have been easier is SQL supported some sort of anonymous access setting that said don't validate
this user, just let them do this, but...
Please let me know if you see any flaws in my reasoning.
Thanks
On Thu, 14 Apr 2005 05:18:35 GMT, v-schang@.online.microsoft.com (Steven Cheng[MSFT]) wrote:
>Hi Roy,
>Welcome to MSDN newsgroup.
>Regarding on the problem you mentioned, I think the it'll be a bit
>difficult to meet all your requirement. Here are some of my understandings:
>First, ASP will always impersonate the anonymous account( IIS's default
>IUSR_machine account) if we enable anonymous access in our IIS virtual dir.
>Then, when our asp page try accessing any protected resource, the
>IUSR_machine account will be the authenticated and executing account of our
>asp page's thread. Then, return back to the quesitons you mentioned:
>==============
>What is the correct way to do one of the following.
>1) - Allow all users (authenticated or not) to update a database?
>2) - Set up the SQL server so that it can treat the 2003 local account (not
>a domain account) as authenticated
>==============
>1) I think the most standard means for allow all users to access db is to
>use SQLServer Autehntcaiton(provide the username account in
>connectionstring. This will require the SQLServer db to allow SQL
>authentication. In fact, this is limited by the ASP , in asp.net we can
>impersonate a certain fixed account so as to use t hat account to access
>the database through integrated windows authentication.
>2) If the webserver and SqlServer's database server is the same box, we
>can simply grant the IIS's IUSR_MACHINE account the permisson to access
>sqlserver db. However, as you said the DB server is a remote server to the
>webserver, the IUSR_machine(local account ) on webserver is not valid on DB
>server. For such scenario, there are two options:
>a. use a Domain Account as your IIS virtual dir's anonymous account.
>(Seems you didn't want to use DomainAcount
)>b. create a duplicate local account on the SQLServer 's machine which has
>the same username and password with the IIS virtual dir's anonymous account
>(on the webserver box). However, the IIS's default anonymous account(
>IUSR_MACHINE) 'S password is controled by machine rather than ourself. So
>we need to either explicitly set IUSR_MACHINE's password or create a
>custom local account and replace the IUSR_machine as the virtual dir's
>anonymous account.
>Anyway, since there hasn't any means which will satisfy all the
>requirement, we may need to make our decision according to the actual
>situation. Please have a look of all the above things and feel free to let
>us know if you have any ideas.
>Thanks,
>Steven Cheng
>Microsoft Online Support
>Get Secure! www.microsoft.com/security
>(This posting is provided "AS IS", with no warranties, and confers no
>rights.)
>
>
Roy Chastain
KMSystems, Inc.
|||Glad to hear from you Roy,
I think it's OK since ASP will impersonate the authenticated user by
default( if allow anonymous then impersonate the anonymous user). And
using Integrated windows authentication at back end db is also what we
recommend.
BTW, is there any future action plan that you'll migrate your web
application from classic ASP to ASP.NET. The asp.net web app framework will
have more strong support for stable and high performance web application.
Also, as for security, the asp.net can let the asp.net running under the
process idenity (the application pool identity in IIS6) together with allow
anonymous in IIS. Thus, we can still keep the IIS's anonymous account as a
very restricted account.
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Friday, February 24, 2012
Annon Merge over VPN: WSM Insanity
I have my replication "working", though I would like to script as much
of the client installation as possible, and running into mega
headaches.
Here's the setup:
Client - MSDE
connects to Publisher/Distributor via VPN
annonymous pull subscription
I can install my MSDE, create the db, logins, etc.
1) Through EM, I can create the subscription through wizard. (selecting
"Available to Synch Manager", "Start immediately"). It works.
Syncronization Manager (type in passwords) synch works.
2) I script the subscription created in 1). Delete subscription and run
script with osql (doesn't run Merge Agent job automatically. Why not? I
even put in an extra line: EXEC sp_start_job @.job_name =
'MERGE_AGENT_JOBNAME'). Go back to EM, right click on subsrciption -
Start Synchronizing. It works. WSM (type in passwords) synch works.
3). Delete subcription and recreate with same script as above. Go
straight to WSM. The subscription is in the list. Synch (type in
passwords). DOES NOT WORK!!! I get the error "the schema script <blah
blah blah> could not be propagated to the subscriber."
Why should I have to run the subscription once through EM before it
will work with WSM? I guess it has something to do with that Merge
Agent job and it needs to be fired off first?
Obviously EM will not be distributed to my end users in far off lands.
I want them to be able to run a script and then synch through WSM. What
is the best way to achieve this?
Much Thanks
answers in line.
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
<richerwin@.ubs-europe.org> wrote in message
news:1109180376.620053.87490@.o13g2000cwo.googlegro ups.com...
> I have my replication "working", though I would like to script as much
> of the client installation as possible, and running into mega
> headaches.
> Here's the setup:
> Client - MSDE
> connects to Publisher/Distributor via VPN
> annonymous pull subscription
> I can install my MSDE, create the db, logins, etc.
> 1) Through EM, I can create the subscription through wizard. (selecting
> "Available to Synch Manager", "Start immediately"). It works.
> Syncronization Manager (type in passwords) synch works.
I take it you are using SQL Authentication in WSM. If so your user will have
to enter the password each time WSM runs. You might want to use intergrated
authentication and enter the user account in the pal on the publisher.
> 2) I script the subscription created in 1). Delete subscription and run
> script with osql (doesn't run Merge Agent job automatically. Why not? I
> even put in an extra line: EXEC sp_start_job @.job_name =
> 'MERGE_AGENT_JOBNAME'). Go back to EM, right click on subsrciption -
> Start Synchronizing. It works. WSM (type in passwords) synch works.
The merge agent doesn't start automatically because you have defined it to
start on demand.
> 3). Delete subcription and recreate with same script as above. Go
> straight to WSM. The subscription is in the list. Synch (type in
> passwords). DOES NOT WORK!!! I get the error "the schema script <blah
> blah blah> could not be propagated to the subscriber."
This means that the subscriber does not have rights to read the snapshot
share. You will have to craft a new snapshot share which does not use the
administrative share (ie \\servername\c$\Program Files\Microsoft SQL
Server\MSSQL\ReplData\UNC). Make sure this new snapshot share has read
permission for the accounts or a group which the merge users are in, and
that this group or user has rights to read the underlying files and folders.
> Why should I have to run the subscription once through EM before it
> will work with WSM? I guess it has something to do with that Merge
> Agent job and it needs to be fired off first?
This does sound odd. Perhaps it is a rights issue.
> Obviously EM will not be distributed to my end users in far off lands.
> I want them to be able to run a script and then synch through WSM. What
> is the best way to achieve this?
> Much Thanks
>
|||
> This does sound odd. Perhaps it is a rights issue.
I create my subscription. Local machine is RICH-VAIO,
Publisher/Distributor is WSCLAN08; database is TMS. At both ends, the
SQL Server is the default instance.
1) I run the following Win2000 DOS BATCH command:
"C:\Program Files\Microsoft SQL Server\80\COM\replmerg.exe" -Publisher
[WSCLAN08] -PublisherDB [TMS] -Publication [pubUser100] -PublisherLogin
[tmsuser] -PublisherPassword [tmsuser] -Distributor [WSCLAN08]
-DistributorLogin [tmsuser] -DistributorPassword [tmsuser] -Subscriber
[RICH-VAIO] -SubscriberDB [TMS] -SubscriptionType 2
-SubscriberSecurityMode 0 -SubscriberLogin [tmsuser]
-SubscriberPassword []
and get the following log:
Microsoft SQL Server Merge Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Connecting to Subscriber 'RICH-VAIO'
Connecting to Distributor 'WSCLAN08'
Initializing
Connecting to Publisher 'WSCLAN08'
Retrieving publication information
Retrieving subscription information
The subscription has been marked for reinitialization. Reinitialization
will occur the next time you synchronize this subscription.
The schema script
'\\WSCLAN08\ReplData\unc\WSCLAN08_TMS_pubUser100\2 0050224042747\snapshot.pre'
could not be propagated to the subscriber.
Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script
'\\WSCLAN08\ReplData\unc\WSCLAN08_TMS_pubUser100\2 0050224042747\snapshot.pre'
could not be propagated to the subscriber.
Category:AGENT
Source: RICH-VAIO
Number: 0
Message: The process could not read file
'\\WSCLAN08\ReplData\unc\WSCLAN08_TMS_pubUser100\2 0050224042747\snapshot.pre'
due to OS error 1326.
Category:OS
Source:
Number: 1326
Message: Logon failure: unknown user name or bad password.
2) Immediately, I go to EM, right click on my subscription, and select
Start Synchronizing. The last entry in the log history is:
The job succeeded. The Job was invoked by User tmsuser. The last step
to run was step 1 (Run agent.).
3) Immediately, I run the same batch file as above. I get the following
log:
Microsoft SQL Server Merge Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Connecting to Subscriber 'RICH-VAIO'
Connecting to Distributor 'WSCLAN08'
Initializing
Connecting to Publisher 'WSCLAN08'
Retrieving publication information
Retrieving subscription information
The merge process is cleaning up meta data in database 'TMS'.
The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s)
in MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
The merge process is cleaning up meta data in database 'TMS'.
The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s)
in MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
Uploading data changes to the Publisher
No data needed to be merged.
Downloading data changes to the Subscriber
4) Successive changes to the data at the subscriber are successfully
uploaded as in 3).
WHAT THE FREAK IS GOING ON WITH Merge Agent?
Please, please, please help. My kindom for a solution.
It must be noted I am not logged into Win2000 as tmsuser, though
tmsuser is a domain user under which SQLSERVER AGENT runs at the
subscriber, and tmsuser has full rights on the snapshot share at the
Publisher (as evident by the successful replications above).
|||just a wild thought here - why are you running the merge binary from the
command line?
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
<richerwin@.ubs-europe.org> wrote in message
news:1109221256.951320.175930@.f14g2000cwb.googlegr oups.com...
>
> I create my subscription. Local machine is RICH-VAIO,
> Publisher/Distributor is WSCLAN08; database is TMS. At both ends, the
> SQL Server is the default instance.
>
> 1) I run the following Win2000 DOS BATCH command:
> "C:\Program Files\Microsoft SQL Server\80\COM\replmerg.exe" -Publisher
> [WSCLAN08] -PublisherDB [TMS] -Publication [pubUser100] -PublisherLogin
> [tmsuser] -PublisherPassword [tmsuser] -Distributor [WSCLAN08]
> -DistributorLogin [tmsuser] -DistributorPassword [tmsuser] -Subscriber
> [RICH-VAIO] -SubscriberDB [TMS] -SubscriptionType 2
> -SubscriberSecurityMode 0 -SubscriberLogin [tmsuser]
> -SubscriberPassword []
> and get the following log:
> Microsoft SQL Server Merge Agent 8.00.760
> Copyright (c) 2000 Microsoft Corporation
> Connecting to Subscriber 'RICH-VAIO'
> Connecting to Distributor 'WSCLAN08'
> Initializing
> Connecting to Publisher 'WSCLAN08'
> Retrieving publication information
> Retrieving subscription information
> The subscription has been marked for reinitialization. Reinitialization
> will occur the next time you synchronize this subscription.
> The schema script
>
'\\WSCLAN08\ReplData\unc\WSCLAN08_TMS_pubUser100\2 0050224042747\snapshot.pre
'
> could not be propagated to the subscriber.
> Category:NULL
> Source: Merge Replication Provider
> Number: -2147201001
> Message: The schema script
>
'\\WSCLAN08\ReplData\unc\WSCLAN08_TMS_pubUser100\2 0050224042747\snapshot.pre
'
> could not be propagated to the subscriber.
> Category:AGENT
> Source: RICH-VAIO
> Number: 0
> Message: The process could not read file
>
'\\WSCLAN08\ReplData\unc\WSCLAN08_TMS_pubUser100\2 0050224042747\snapshot.pre
'
> due to OS error 1326.
> Category:OS
> Source:
> Number: 1326
> Message: Logon failure: unknown user name or bad password.
> 2) Immediately, I go to EM, right click on my subscription, and select
> Start Synchronizing. The last entry in the log history is:
> The job succeeded. The Job was invoked by User tmsuser. The last step
> to run was step 1 (Run agent.).
> 3) Immediately, I run the same batch file as above. I get the following
> log:
> Microsoft SQL Server Merge Agent 8.00.760
> Copyright (c) 2000 Microsoft Corporation
> Connecting to Subscriber 'RICH-VAIO'
> Connecting to Distributor 'WSCLAN08'
> Initializing
> Connecting to Publisher 'WSCLAN08'
> Retrieving publication information
> Retrieving subscription information
> The merge process is cleaning up meta data in database 'TMS'.
> The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s)
> in MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
> The merge process is cleaning up meta data in database 'TMS'.
> The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s)
> in MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
> Uploading data changes to the Publisher
> No data needed to be merged.
> Downloading data changes to the Subscriber
> 4) Successive changes to the data at the subscriber are successfully
> uploaded as in 3).
>
> WHAT THE FREAK IS GOING ON WITH Merge Agent?
> Please, please, please help. My kindom for a solution.
> It must be noted I am not logged into Win2000 as tmsuser, though
> tmsuser is a domain user under which SQLSERVER AGENT runs at the
> subscriber, and tmsuser has full rights on the snapshot share at the
> Publisher (as evident by the successful replications above).
>
|||
> why are you running the merge binary from the command line?
1) To show I'm getting the same results as from WSM.
2) So I can write the results to a log file with the >> redirect
command (so I can post them here) and show the group what I am doing.
3) End users won't have EM, so they need a way to start replication
(which isn't working from WSM, which is why I started this thread)
4) Proof of concept - it SHOULD work, shouldn't it?
thanks
|||[vbcol=seagreen]
This must have to do with accounts / permissions.
I have a couple of theories.
1) Why would executing the Merge agent job from within EM work, while
neither command-line nor WSM work? After all, I generated the
command-line args from the job from EM.
Is EM firing off the merge job under the same userID that I am when I
fire off the command line? (In the example above, both should be
'tmsuser'). How can I tell?
2) When I execute synchronize from WSM, do I have to be logged in to
Windows with the same domain ID that SQLSERVER AGENT (Windows service)
runs under?
Any help appreciated.
Thanks
of the client installation as possible, and running into mega
headaches.
Here's the setup:
Client - MSDE
connects to Publisher/Distributor via VPN
annonymous pull subscription
I can install my MSDE, create the db, logins, etc.
1) Through EM, I can create the subscription through wizard. (selecting
"Available to Synch Manager", "Start immediately"). It works.
Syncronization Manager (type in passwords) synch works.
2) I script the subscription created in 1). Delete subscription and run
script with osql (doesn't run Merge Agent job automatically. Why not? I
even put in an extra line: EXEC sp_start_job @.job_name =
'MERGE_AGENT_JOBNAME'). Go back to EM, right click on subsrciption -
Start Synchronizing. It works. WSM (type in passwords) synch works.
3). Delete subcription and recreate with same script as above. Go
straight to WSM. The subscription is in the list. Synch (type in
passwords). DOES NOT WORK!!! I get the error "the schema script <blah
blah blah> could not be propagated to the subscriber."
Why should I have to run the subscription once through EM before it
will work with WSM? I guess it has something to do with that Merge
Agent job and it needs to be fired off first?
Obviously EM will not be distributed to my end users in far off lands.
I want them to be able to run a script and then synch through WSM. What
is the best way to achieve this?
Much Thanks
answers in line.
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
<richerwin@.ubs-europe.org> wrote in message
news:1109180376.620053.87490@.o13g2000cwo.googlegro ups.com...
> I have my replication "working", though I would like to script as much
> of the client installation as possible, and running into mega
> headaches.
> Here's the setup:
> Client - MSDE
> connects to Publisher/Distributor via VPN
> annonymous pull subscription
> I can install my MSDE, create the db, logins, etc.
> 1) Through EM, I can create the subscription through wizard. (selecting
> "Available to Synch Manager", "Start immediately"). It works.
> Syncronization Manager (type in passwords) synch works.
I take it you are using SQL Authentication in WSM. If so your user will have
to enter the password each time WSM runs. You might want to use intergrated
authentication and enter the user account in the pal on the publisher.
> 2) I script the subscription created in 1). Delete subscription and run
> script with osql (doesn't run Merge Agent job automatically. Why not? I
> even put in an extra line: EXEC sp_start_job @.job_name =
> 'MERGE_AGENT_JOBNAME'). Go back to EM, right click on subsrciption -
> Start Synchronizing. It works. WSM (type in passwords) synch works.
The merge agent doesn't start automatically because you have defined it to
start on demand.
> 3). Delete subcription and recreate with same script as above. Go
> straight to WSM. The subscription is in the list. Synch (type in
> passwords). DOES NOT WORK!!! I get the error "the schema script <blah
> blah blah> could not be propagated to the subscriber."
This means that the subscriber does not have rights to read the snapshot
share. You will have to craft a new snapshot share which does not use the
administrative share (ie \\servername\c$\Program Files\Microsoft SQL
Server\MSSQL\ReplData\UNC). Make sure this new snapshot share has read
permission for the accounts or a group which the merge users are in, and
that this group or user has rights to read the underlying files and folders.
> Why should I have to run the subscription once through EM before it
> will work with WSM? I guess it has something to do with that Merge
> Agent job and it needs to be fired off first?
This does sound odd. Perhaps it is a rights issue.
> Obviously EM will not be distributed to my end users in far off lands.
> I want them to be able to run a script and then synch through WSM. What
> is the best way to achieve this?
> Much Thanks
>
|||
> This does sound odd. Perhaps it is a rights issue.
I create my subscription. Local machine is RICH-VAIO,
Publisher/Distributor is WSCLAN08; database is TMS. At both ends, the
SQL Server is the default instance.
1) I run the following Win2000 DOS BATCH command:
"C:\Program Files\Microsoft SQL Server\80\COM\replmerg.exe" -Publisher
[WSCLAN08] -PublisherDB [TMS] -Publication [pubUser100] -PublisherLogin
[tmsuser] -PublisherPassword [tmsuser] -Distributor [WSCLAN08]
-DistributorLogin [tmsuser] -DistributorPassword [tmsuser] -Subscriber
[RICH-VAIO] -SubscriberDB [TMS] -SubscriptionType 2
-SubscriberSecurityMode 0 -SubscriberLogin [tmsuser]
-SubscriberPassword []
and get the following log:
Microsoft SQL Server Merge Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Connecting to Subscriber 'RICH-VAIO'
Connecting to Distributor 'WSCLAN08'
Initializing
Connecting to Publisher 'WSCLAN08'
Retrieving publication information
Retrieving subscription information
The subscription has been marked for reinitialization. Reinitialization
will occur the next time you synchronize this subscription.
The schema script
'\\WSCLAN08\ReplData\unc\WSCLAN08_TMS_pubUser100\2 0050224042747\snapshot.pre'
could not be propagated to the subscriber.
Category:NULL
Source: Merge Replication Provider
Number: -2147201001
Message: The schema script
'\\WSCLAN08\ReplData\unc\WSCLAN08_TMS_pubUser100\2 0050224042747\snapshot.pre'
could not be propagated to the subscriber.
Category:AGENT
Source: RICH-VAIO
Number: 0
Message: The process could not read file
'\\WSCLAN08\ReplData\unc\WSCLAN08_TMS_pubUser100\2 0050224042747\snapshot.pre'
due to OS error 1326.
Category:OS
Source:
Number: 1326
Message: Logon failure: unknown user name or bad password.
2) Immediately, I go to EM, right click on my subscription, and select
Start Synchronizing. The last entry in the log history is:
The job succeeded. The Job was invoked by User tmsuser. The last step
to run was step 1 (Run agent.).
3) Immediately, I run the same batch file as above. I get the following
log:
Microsoft SQL Server Merge Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Connecting to Subscriber 'RICH-VAIO'
Connecting to Distributor 'WSCLAN08'
Initializing
Connecting to Publisher 'WSCLAN08'
Retrieving publication information
Retrieving subscription information
The merge process is cleaning up meta data in database 'TMS'.
The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s)
in MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
The merge process is cleaning up meta data in database 'TMS'.
The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s)
in MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
Uploading data changes to the Publisher
No data needed to be merged.
Downloading data changes to the Subscriber
4) Successive changes to the data at the subscriber are successfully
uploaded as in 3).
WHAT THE FREAK IS GOING ON WITH Merge Agent?
Please, please, please help. My kindom for a solution.
It must be noted I am not logged into Win2000 as tmsuser, though
tmsuser is a domain user under which SQLSERVER AGENT runs at the
subscriber, and tmsuser has full rights on the snapshot share at the
Publisher (as evident by the successful replications above).
|||just a wild thought here - why are you running the merge binary from the
command line?
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
<richerwin@.ubs-europe.org> wrote in message
news:1109221256.951320.175930@.f14g2000cwb.googlegr oups.com...
>
> I create my subscription. Local machine is RICH-VAIO,
> Publisher/Distributor is WSCLAN08; database is TMS. At both ends, the
> SQL Server is the default instance.
>
> 1) I run the following Win2000 DOS BATCH command:
> "C:\Program Files\Microsoft SQL Server\80\COM\replmerg.exe" -Publisher
> [WSCLAN08] -PublisherDB [TMS] -Publication [pubUser100] -PublisherLogin
> [tmsuser] -PublisherPassword [tmsuser] -Distributor [WSCLAN08]
> -DistributorLogin [tmsuser] -DistributorPassword [tmsuser] -Subscriber
> [RICH-VAIO] -SubscriberDB [TMS] -SubscriptionType 2
> -SubscriberSecurityMode 0 -SubscriberLogin [tmsuser]
> -SubscriberPassword []
> and get the following log:
> Microsoft SQL Server Merge Agent 8.00.760
> Copyright (c) 2000 Microsoft Corporation
> Connecting to Subscriber 'RICH-VAIO'
> Connecting to Distributor 'WSCLAN08'
> Initializing
> Connecting to Publisher 'WSCLAN08'
> Retrieving publication information
> Retrieving subscription information
> The subscription has been marked for reinitialization. Reinitialization
> will occur the next time you synchronize this subscription.
> The schema script
>
'\\WSCLAN08\ReplData\unc\WSCLAN08_TMS_pubUser100\2 0050224042747\snapshot.pre
'
> could not be propagated to the subscriber.
> Category:NULL
> Source: Merge Replication Provider
> Number: -2147201001
> Message: The schema script
>
'\\WSCLAN08\ReplData\unc\WSCLAN08_TMS_pubUser100\2 0050224042747\snapshot.pre
'
> could not be propagated to the subscriber.
> Category:AGENT
> Source: RICH-VAIO
> Number: 0
> Message: The process could not read file
>
'\\WSCLAN08\ReplData\unc\WSCLAN08_TMS_pubUser100\2 0050224042747\snapshot.pre
'
> due to OS error 1326.
> Category:OS
> Source:
> Number: 1326
> Message: Logon failure: unknown user name or bad password.
> 2) Immediately, I go to EM, right click on my subscription, and select
> Start Synchronizing. The last entry in the log history is:
> The job succeeded. The Job was invoked by User tmsuser. The last step
> to run was step 1 (Run agent.).
> 3) Immediately, I run the same batch file as above. I get the following
> log:
> Microsoft SQL Server Merge Agent 8.00.760
> Copyright (c) 2000 Microsoft Corporation
> Connecting to Subscriber 'RICH-VAIO'
> Connecting to Distributor 'WSCLAN08'
> Initializing
> Connecting to Publisher 'WSCLAN08'
> Retrieving publication information
> Retrieving subscription information
> The merge process is cleaning up meta data in database 'TMS'.
> The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s)
> in MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
> The merge process is cleaning up meta data in database 'TMS'.
> The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s)
> in MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
> Uploading data changes to the Publisher
> No data needed to be merged.
> Downloading data changes to the Subscriber
> 4) Successive changes to the data at the subscriber are successfully
> uploaded as in 3).
>
> WHAT THE FREAK IS GOING ON WITH Merge Agent?
> Please, please, please help. My kindom for a solution.
> It must be noted I am not logged into Win2000 as tmsuser, though
> tmsuser is a domain user under which SQLSERVER AGENT runs at the
> subscriber, and tmsuser has full rights on the snapshot share at the
> Publisher (as evident by the successful replications above).
>
|||
> why are you running the merge binary from the command line?
1) To show I'm getting the same results as from WSM.
2) So I can write the results to a log file with the >> redirect
command (so I can post them here) and show the group what I am doing.
3) End users won't have EM, so they need a way to start replication
(which isn't working from WSM, which is why I started this thread)
4) Proof of concept - it SHOULD work, shouldn't it?
thanks
|||[vbcol=seagreen]
This must have to do with accounts / permissions.
I have a couple of theories.
1) Why would executing the Merge agent job from within EM work, while
neither command-line nor WSM work? After all, I generated the
command-line args from the job from EM.
Is EM firing off the merge job under the same userID that I am when I
fire off the command line? (In the example above, both should be
'tmsuser'). How can I tell?
2) When I execute synchronize from WSM, do I have to be logged in to
Windows with the same domain ID that SQLSERVER AGENT (Windows service)
runs under?
Any help appreciated.
Thanks
Thursday, February 16, 2012
Analysis Services upgrade to Enterprise Edition
I was running SQL 2000 Standard with the Analysis Services
repository in a SQL database.
I upgraded SQL to Enterprise. When a user tried to create
a partitioned cube he got: user-defined partitions are
available only if you install Analysis Services SQL Server
2000 Enterprise Edition
I "upgraded" to Analysis Services Enterprise - actually
all it did was reinstall. Since I had already migrated
the repository to SQL, my cubes did not exist.
Here is probably where my mistake occurred: I "re-
migraded" the repository to SQL ... my cubes are still not
there.
I have since restored the repository database from a pre-
upgraded Analysis Services version ... my cubes are still
not there.
I have a large project that is waiting for these cubes.
Please tell me I have a chance of getting these cubes back!
Does anyone have any suggestiongs?
TIA
WadeIf you were using SQL Database A as repository before upgrading and
migrating repsitory to SQL Database B after upgrading, then restore the
backup to Database A won't help. You need to edit the repository connection
string so it points to the database holds the right meta data for OLAP.
Thanks
Wei Zhang
Microsoft OLAP Support
repository in a SQL database.
I upgraded SQL to Enterprise. When a user tried to create
a partitioned cube he got: user-defined partitions are
available only if you install Analysis Services SQL Server
2000 Enterprise Edition
I "upgraded" to Analysis Services Enterprise - actually
all it did was reinstall. Since I had already migrated
the repository to SQL, my cubes did not exist.
Here is probably where my mistake occurred: I "re-
migraded" the repository to SQL ... my cubes are still not
there.
I have since restored the repository database from a pre-
upgraded Analysis Services version ... my cubes are still
not there.
I have a large project that is waiting for these cubes.
Please tell me I have a chance of getting these cubes back!
Does anyone have any suggestiongs?
TIA
WadeIf you were using SQL Database A as repository before upgrading and
migrating repsitory to SQL Database B after upgrading, then restore the
backup to Database A won't help. You need to edit the repository connection
string so it points to the database holds the right meta data for OLAP.
Thanks
Wei Zhang
Microsoft OLAP Support
Analysis Services upgrade to Enterprise Edition
I was running SQL 2000 Standard with the Analysis Services
repository in a SQL database.
I upgraded SQL to Enterprise. When a user tried to create
a partitioned cube he got: user-defined partitions are
available only if you install Analysis Services SQL Server
2000 Enterprise Edition
I "upgraded" to Analysis Services Enterprise - actually
all it did was reinstall. Since I had already migrated
the repository to SQL, my cubes did not exist.
Here is probably where my mistake occurred: I "re-
migraded" the repository to SQL ... my cubes are still not
there.
I have since restored the repository database from a pre-
upgraded Analysis Services version ... my cubes are still
not there.
I have a large project that is waiting for these cubes.
Please tell me I have a chance of getting these cubes back!
Does anyone have any suggestiongs?
TIA
Wade
If you were using SQL Database A as repository before upgrading and
migrating repsitory to SQL Database B after upgrading, then restore the
backup to Database A won't help. You need to edit the repository connection
string so it points to the database holds the right meta data for OLAP.
Thanks
Wei Zhang
Microsoft OLAP Support
repository in a SQL database.
I upgraded SQL to Enterprise. When a user tried to create
a partitioned cube he got: user-defined partitions are
available only if you install Analysis Services SQL Server
2000 Enterprise Edition
I "upgraded" to Analysis Services Enterprise - actually
all it did was reinstall. Since I had already migrated
the repository to SQL, my cubes did not exist.
Here is probably where my mistake occurred: I "re-
migraded" the repository to SQL ... my cubes are still not
there.
I have since restored the repository database from a pre-
upgraded Analysis Services version ... my cubes are still
not there.
I have a large project that is waiting for these cubes.
Please tell me I have a chance of getting these cubes back!
Does anyone have any suggestiongs?
TIA
Wade
If you were using SQL Database A as repository before upgrading and
migrating repsitory to SQL Database B after upgrading, then restore the
backup to Database A won't help. You need to edit the repository connection
string so it points to the database holds the right meta data for OLAP.
Thanks
Wei Zhang
Microsoft OLAP Support
Analysis Services Rolling Date reports
I have a Time and Billing OLAP cube which I'm running RS against. I'm
stumped on a date issue.
How can I run a report which selects the last 7 days worth of data and rolls
forward each week? I've tried using an MDX query with the Tail funtion.
This pulls the last date which has data in it. (Effectively yesterday's
date) When I run it in MDX builder it gives me the desired results. However
when I use it in VS.Net to build my report, it pulls the last 7 days over,
but it's static and doesn't roll forward.
I can make a report with a date drop down parameter which is described in
the AS and RS article on Technet, but I'd really like the parameter to be
automatically selected based off of the date when the report is run.
My date formats in my cube are [Year].[Quarter].[Month].[Day]
Can anybody help me with this?
Thanks, MattTry setting defaults for your start and end date parameters. For
example, you can set the end date to
DateTime.Now.AddDays(-1).ToString("MM/dd/yyyy") and the start date to
DateTime.Now.AddDays(-7).ToString("MM/dd/yyyy"). When you see the
parameters in subscription creation, it may look like they are
hard-coded, but they aren't as long as the default checkbox is selected.|||Thanks for the suggestion... I think I'm close...
The problem is that my date needs to be in a [Time].[FY Calendar].[All
Time].[Year].[Quarter].[Month].[Day] format.
As you probably can tell, I'm a newbie to VB Scripting. How can I convert
your suggestion "DateTime.Now.AddDays(-1).ToString("MM/dd/yyyy")" to my cube
format? I think if I can do that, I can get it to work.
Thanks,
Matt
"Kenny" wrote:
> Try setting defaults for your start and end date parameters. For
> example, you can set the end date to
> DateTime.Now.AddDays(-1).ToString("MM/dd/yyyy") and the start date to
> DateTime.Now.AddDays(-7).ToString("MM/dd/yyyy"). When you see the
> parameters in subscription creation, it may look like they are
> hard-coded, but they aren't as long as the default checkbox is selected.
>
stumped on a date issue.
How can I run a report which selects the last 7 days worth of data and rolls
forward each week? I've tried using an MDX query with the Tail funtion.
This pulls the last date which has data in it. (Effectively yesterday's
date) When I run it in MDX builder it gives me the desired results. However
when I use it in VS.Net to build my report, it pulls the last 7 days over,
but it's static and doesn't roll forward.
I can make a report with a date drop down parameter which is described in
the AS and RS article on Technet, but I'd really like the parameter to be
automatically selected based off of the date when the report is run.
My date formats in my cube are [Year].[Quarter].[Month].[Day]
Can anybody help me with this?
Thanks, MattTry setting defaults for your start and end date parameters. For
example, you can set the end date to
DateTime.Now.AddDays(-1).ToString("MM/dd/yyyy") and the start date to
DateTime.Now.AddDays(-7).ToString("MM/dd/yyyy"). When you see the
parameters in subscription creation, it may look like they are
hard-coded, but they aren't as long as the default checkbox is selected.|||Thanks for the suggestion... I think I'm close...
The problem is that my date needs to be in a [Time].[FY Calendar].[All
Time].[Year].[Quarter].[Month].[Day] format.
As you probably can tell, I'm a newbie to VB Scripting. How can I convert
your suggestion "DateTime.Now.AddDays(-1).ToString("MM/dd/yyyy")" to my cube
format? I think if I can do that, I can get it to work.
Thanks,
Matt
"Kenny" wrote:
> Try setting defaults for your start and end date parameters. For
> example, you can set the end date to
> DateTime.Now.AddDays(-1).ToString("MM/dd/yyyy") and the start date to
> DateTime.Now.AddDays(-7).ToString("MM/dd/yyyy"). When you see the
> parameters in subscription creation, it may look like they are
> hard-coded, but they aren't as long as the default checkbox is selected.
>
Monday, February 13, 2012
Analysis Services Project - A connection cannot be made. Ensure the server is running.
Hi there
I have created an Analysis services project on a laptop running developer edition SQL 2005. The database is hosted on the local machine. When I attempt to debug or deploy the project I get an error;
Error 1 The project could not be deployed to the 'localhost' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.
It seems bizarre as I can view tables, create dimensions, cubes etc also I have database as a connection in the server explorer.
I have checked that the services are running, I've restarted them also just in case.
Any ideas would be much appreciated.
Regards,
Derek
Hello derek
I got the same problem yesterday and the solution to this problem is to right click on the project in solution explorer.say MovieSample is a project right click on it and then go to Properties.In properties on th left hand side select deployment and change the server name.By default the server name is localHost so replace it with your machine name and then instance of sql server 2005 like aliraza/sqlserver2005.
try this and i am pretty sure that this will work fine for you.
ali
|||This post looks old but for those of you just looking now you might also try making sure you have Analysis Services started.|||Hi,
What is Analysis Serves? How can I start it? And I entered my server name but still it is saying me same error. Error 1 The project could not be deployed to the 'xxxx(my server name)' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.
I am totally new in this area..
Please solve it.. Thanks.
Analysis Services Project - A connection cannot be made. Ensure the server is running.
Hi there
I have created an Analysis services project on a laptop running developer edition SQL 2005. The database is hosted on the local machine. When I attempt to debug or deploy the project I get an error;
Error 1 The project could not be deployed to the 'localhost' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.
It seems bizarre as I can view tables, create dimensions, cubes etc also I have database as a connection in the server explorer.
I have checked that the services are running, I've restarted them also just in case.
Any ideas would be much appreciated.
Regards,
Derek
Hello derek
I got the same problem yesterday and the solution to this problem is to right click on the project in solution explorer.say MovieSample is a project right click on it and then go to Properties.In properties on th left hand side select deployment and change the server name.By default the server name is localHost so replace it with your machine name and then instance of sql server 2005 like aliraza/sqlserver2005.
try this and i am pretty sure that this will work fine for you.
ali
|||This post looks old but for those of you just looking now you might also try making sure you have Analysis Services started.|||Hi,
What is Analysis Serves? How can I start it? And I entered my server name but still it is saying me same error. Error 1 The project could not be deployed to the 'xxxx(my server name)' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.
I am totally new in this area..
Please solve it.. Thanks.
|||
Hi,
1.Make sure you have entered the server name correctly and
2.if you are connecting to a remote server its fine or if you are connecting to the SSAS through http then you may have to configure that(hit google 4 more help)
I think in your case the SSAS service is not started,mostly SSAS service when installed is tagged as 'manual'
so please 'start' the SSAS service and try deploying !!
|||I'm having the similar problem as stated above. how bout i've got both SSAS running already but still doesnt seems working. what should I do?|||In solutions Explorer
Click Name of the project and right click and go to properties.Expand Configuration Properties and click deployment.Change the server to the correct name of the server with any instance.
Expand Data Sources and double click your data source.Go to imprsonate Information and check use a specific user name and password radio button and enter domain user having sysadmin rights of your database and password.
Analysis Services Project - A connection cannot be made. Ensure the server is running.
Hi there
I have created an Analysis services project on a laptop running developer edition SQL 2005. The database is hosted on the local machine. When I attempt to debug or deploy the project I get an error;
Error 1 The project could not be deployed to the 'localhost' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.
It seems bizarre as I can view tables, create dimensions, cubes etc also I have database as a connection in the server explorer.
I have checked that the services are running, I've restarted them also just in case.
Any ideas would be much appreciated.
Regards,
Derek
Hello derek
I got the same problem yesterday and the solution to this problem is to right click on the project in solution explorer.say MovieSample is a project right click on it and then go to Properties.In properties on th left hand side select deployment and change the server name.By default the server name is localHost so replace it with your machine name and then instance of sql server 2005 like aliraza/sqlserver2005.
try this and i am pretty sure that this will work fine for you.
ali
|||This post looks old but for those of you just looking now you might also try making sure you have Analysis Services started.Analysis Services Project - A connection cannot be made. Ensure the server is running.
Hi there
I have created an Analysis services project on a laptop running developer edition SQL 2005. The database is hosted on the local machine. When I attempt to debug or deploy the project I get an error;
Error 1 The project could not be deployed to the 'localhost' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.
It seems bizarre as I can view tables, create dimensions, cubes etc also I have database as a connection in the server explorer.
I have checked that the services are running, I've restarted them also just in case.
Any ideas would be much appreciated.
Regards,
Derek
Hello derek
I got the same problem yesterday and the solution to this problem is to right click on the project in solution explorer.say MovieSample is a project right click on it and then go to Properties.In properties on th left hand side select deployment and change the server name.By default the server name is localHost so replace it with your machine name and then instance of sql server 2005 like aliraza/sqlserver2005.
try this and i am pretty sure that this will work fine for you.
ali
|||This post looks old but for those of you just looking now you might also try making sure you have Analysis Services started.|||Hi,
What is Analysis Serves? How can I start it? And I entered my server name but still it is saying me same error. Error 1 The project could not be deployed to the 'xxxx(my server name)' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.
I am totally new in this area..
Please solve it.. Thanks.
|||
Hi,
1.Make sure you have entered the server name correctly and
2.if you are connecting to a remote server its fine or if you are connecting to the SSAS through http then you may have to configure that(hit google 4 more help)
I think in your case the SSAS service is not started,mostly SSAS service when installed is tagged as 'manual'
so please 'start' the SSAS service and try deploying !!
|||I'm having the similar problem as stated above. how bout i've got both SSAS running already but still doesnt seems working. what should I do?|||In solutions Explorer
Click Name of the project and right click and go to properties.Expand Configuration Properties and click deployment.Change the server to the correct name of the server with any instance.
Expand Data Sources and double click your data source.Go to imprsonate Information and check use a specific user name and password radio button and enter domain user having sysadmin rights of your database and password.
Analysis Services Project - A connection cannot be made. Ensure the server is running.
Hi there
I have created an Analysis services project on a laptop running developer edition SQL 2005. The database is hosted on the local machine. When I attempt to debug or deploy the project I get an error;
Error 1 The project could not be deployed to the 'localhost' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.
It seems bizarre as I can view tables, create dimensions, cubes etc also I have database as a connection in the server explorer.
I have checked that the services are running, I've restarted them also just in case.
Any ideas would be much appreciated.
Regards,
Derek
Hello derek
I got the same problem yesterday and the solution to this problem is to right click on the project in solution explorer.say MovieSample is a project right click on it and then go to Properties.In properties on th left hand side select deployment and change the server name.By default the server name is localHost so replace it with your machine name and then instance of sql server 2005 like aliraza/sqlserver2005.
try this and i am pretty sure that this will work fine for you.
ali
|||This post looks old but for those of you just looking now you might also try making sure you have Analysis Services started.|||Hi,
What is Analysis Serves? How can I start it? And I entered my server name but still it is saying me same error. Error 1 The project could not be deployed to the 'xxxx(my server name)' server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.
I am totally new in this area..
Please solve it.. Thanks.
|||
Hi,
1.Make sure you have entered the server name correctly and
2.if you are connecting to a remote server its fine or if you are connecting to the SSAS through http then you may have to configure that(hit google 4 more help)
I think in your case the SSAS service is not started,mostly SSAS service when installed is tagged as 'manual'
so please 'start' the SSAS service and try deploying !!
|||I'm having the similar problem as stated above. how bout i've got both SSAS running already but still doesnt seems working. what should I do?|||In solutions Explorer
Click Name of the project and right click and go to properties.Expand Configuration Properties and click deployment.Change the server to the correct name of the server with any instance.
Expand Data Sources and double click your data source.Go to imprsonate Information and check use a specific user name and password radio button and enter domain user having sysadmin rights of your database and password.
Subscribe to:
Posts (Atom)