Hi,
We're running SQL server 2000 standard edition on Windows 2003. I logged in
using my domain account which is member of an admin group. But in Enterprise
Manger, under SQL Server Group, I got 'no items'. How come? I used to be
able to use another domain account in the same admin group to log on and had
no problem. What did I miss?
Thanks in advance for any help.
Bing
Hi
"bing" wrote:
> Hi,
> We're running SQL server 2000 standard edition on Windows 2003. I logged in
> using my domain account which is member of an admin group. But in Enterprise
> Manger, under SQL Server Group, I got 'no items'. How come? I used to be
> able to use another domain account in the same admin group to log on and had
> no problem. What did I miss?
> Thanks in advance for any help.
> Bing
When you run SQL Server Enterprise Manager for the first time, it should
automatically registers all instances of a local SQL Server, but any
instances that are added afterwards will be not be automatically registered.
You must be on the server where the instance is installed for this to occur.
If you have removed the registration you will need to manually add it again.
Also check that the registry has not been changed/corrupted.
John
Showing posts with label domain. Show all posts
Showing posts with label domain. Show all posts
Friday, March 30, 2012
No items under SQL server group
Hi,
We're running SQL server 2000 standard edition on Windows 2003. I logged in
using my domain account which is member of an admin group. But in Enterpris
e
Manger, under SQL Server Group, I got 'no items'. How come? I used to be
able to use another domain account in the same admin group to log on and had
no problem. What did I miss?
Thanks in advance for any help.
BingHi
"bing" wrote:
> Hi,
> We're running SQL server 2000 standard edition on Windows 2003. I logged
in
> using my domain account which is member of an admin group. But in Enterpr
ise
> Manger, under SQL Server Group, I got 'no items'. How come? I used to be
> able to use another domain account in the same admin group to log on and h
ad
> no problem. What did I miss?
> Thanks in advance for any help.
> Bing
When you run SQL Server Enterprise Manager for the first time, it should
automatically registers all instances of a local SQL Server, but any
instances that are added afterwards will be not be automatically registered.
You must be on the server where the instance is installed for this to occur.
If you have removed the registration you will need to manually add it again.
Also check that the registry has not been changed/corrupted.
John
We're running SQL server 2000 standard edition on Windows 2003. I logged in
using my domain account which is member of an admin group. But in Enterpris
e
Manger, under SQL Server Group, I got 'no items'. How come? I used to be
able to use another domain account in the same admin group to log on and had
no problem. What did I miss?
Thanks in advance for any help.
BingHi
"bing" wrote:
> Hi,
> We're running SQL server 2000 standard edition on Windows 2003. I logged
in
> using my domain account which is member of an admin group. But in Enterpr
ise
> Manger, under SQL Server Group, I got 'no items'. How come? I used to be
> able to use another domain account in the same admin group to log on and h
ad
> no problem. What did I miss?
> Thanks in advance for any help.
> Bing
When you run SQL Server Enterprise Manager for the first time, it should
automatically registers all instances of a local SQL Server, but any
instances that are added afterwards will be not be automatically registered.
You must be on the server where the instance is installed for this to occur.
If you have removed the registration you will need to manually add it again.
Also check that the registry has not been changed/corrupted.
John
No items under SQL server group
Hi,
We're running SQL server 2000 standard edition on Windows 2003. I logged in
using my domain account which is member of an admin group. But in Enterprise
Manger, under SQL Server Group, I got 'no items'. How come? I used to be
able to use another domain account in the same admin group to log on and had
no problem. What did I miss?
Thanks in advance for any help.
BingHi
"bing" wrote:
> Hi,
> We're running SQL server 2000 standard edition on Windows 2003. I logged in
> using my domain account which is member of an admin group. But in Enterprise
> Manger, under SQL Server Group, I got 'no items'. How come? I used to be
> able to use another domain account in the same admin group to log on and had
> no problem. What did I miss?
> Thanks in advance for any help.
> Bing
When you run SQL Server Enterprise Manager for the first time, it should
automatically registers all instances of a local SQL Server, but any
instances that are added afterwards will be not be automatically registered.
You must be on the server where the instance is installed for this to occur.
If you have removed the registration you will need to manually add it again.
Also check that the registry has not been changed/corrupted.
Johnsql
We're running SQL server 2000 standard edition on Windows 2003. I logged in
using my domain account which is member of an admin group. But in Enterprise
Manger, under SQL Server Group, I got 'no items'. How come? I used to be
able to use another domain account in the same admin group to log on and had
no problem. What did I miss?
Thanks in advance for any help.
BingHi
"bing" wrote:
> Hi,
> We're running SQL server 2000 standard edition on Windows 2003. I logged in
> using my domain account which is member of an admin group. But in Enterprise
> Manger, under SQL Server Group, I got 'no items'. How come? I used to be
> able to use another domain account in the same admin group to log on and had
> no problem. What did I miss?
> Thanks in advance for any help.
> Bing
When you run SQL Server Enterprise Manager for the first time, it should
automatically registers all instances of a local SQL Server, but any
instances that are added afterwards will be not be automatically registered.
You must be on the server where the instance is installed for this to occur.
If you have removed the registration you will need to manually add it again.
Also check that the registry has not been changed/corrupted.
Johnsql
Monday, March 26, 2012
No Email
Hello.
I have created a domain account, granted the account Administrator access on
the report server machine, have changed the two windows services to run as
that account, and have created an Exchange mailbox for the domain account.
I created a simple report that has no data source. I created a shared
calendar that runs every 1 minute. I subscribed to the report on that
schedule, no report.
The report is not being emailed.
Any thoughts?
Thanks in advance,
MikeAlso, SQL server instance is on a different machine.
I don't think that the report is even running. Does reporting services use
the SQL agent?
"mike" <milop@.slomins.com> wrote in message
news:Or03HXtuFHA.2076@.TK2MSFTNGP14.phx.gbl...
> Hello.
> I have created a domain account, granted the account Administrator access
> on the report server machine, have changed the two windows services to run
> as that account, and have created an Exchange mailbox for the domain
> account.
> I created a simple report that has no data source. I created a shared
> calendar that runs every 1 minute. I subscribed to the report on that
> schedule, no report.
> The report is not being emailed.
> Any thoughts?
> Thanks in advance,
> Mike
>|||No,Mike it does not.
"mike" wrote:
> Also, SQL server instance is on a different machine.
> I don't think that the report is even running. Does reporting services use
> the SQL agent?
> "mike" <milop@.slomins.com> wrote in message
> news:Or03HXtuFHA.2076@.TK2MSFTNGP14.phx.gbl...
> > Hello.
> >
> > I have created a domain account, granted the account Administrator access
> > on the report server machine, have changed the two windows services to run
> > as that account, and have created an Exchange mailbox for the domain
> > account.
> >
> > I created a simple report that has no data source. I created a shared
> > calendar that runs every 1 minute. I subscribed to the report on that
> > schedule, no report.
> >
> > The report is not being emailed.
> >
> > Any thoughts?
> >
> > Thanks in advance,
> >
> > Mike
> >
>
>|||As Per my knowledge an SQL Agent job is created for each schedule. SQL Server
Agent is very much required to run the Scheduled SRS Reports.
Ashish
"ProJester" wrote:
> No,Mike it does not.
>
> "mike" wrote:
> > Also, SQL server instance is on a different machine.
> >
> > I don't think that the report is even running. Does reporting services use
> > the SQL agent?
> >
> > "mike" <milop@.slomins.com> wrote in message
> > news:Or03HXtuFHA.2076@.TK2MSFTNGP14.phx.gbl...
> > > Hello.
> > >
> > > I have created a domain account, granted the account Administrator access
> > > on the report server machine, have changed the two windows services to run
> > > as that account, and have created an Exchange mailbox for the domain
> > > account.
> > >
> > > I created a simple report that has no data source. I created a shared
> > > calendar that runs every 1 minute. I subscribed to the report on that
> > > schedule, no report.
> > >
> > > The report is not being emailed.
> > >
> > > Any thoughts?
> > >
> > > Thanks in advance,
> > >
> > > Mike
> > >
> >
> >
> >sql
I have created a domain account, granted the account Administrator access on
the report server machine, have changed the two windows services to run as
that account, and have created an Exchange mailbox for the domain account.
I created a simple report that has no data source. I created a shared
calendar that runs every 1 minute. I subscribed to the report on that
schedule, no report.
The report is not being emailed.
Any thoughts?
Thanks in advance,
MikeAlso, SQL server instance is on a different machine.
I don't think that the report is even running. Does reporting services use
the SQL agent?
"mike" <milop@.slomins.com> wrote in message
news:Or03HXtuFHA.2076@.TK2MSFTNGP14.phx.gbl...
> Hello.
> I have created a domain account, granted the account Administrator access
> on the report server machine, have changed the two windows services to run
> as that account, and have created an Exchange mailbox for the domain
> account.
> I created a simple report that has no data source. I created a shared
> calendar that runs every 1 minute. I subscribed to the report on that
> schedule, no report.
> The report is not being emailed.
> Any thoughts?
> Thanks in advance,
> Mike
>|||No,Mike it does not.
"mike" wrote:
> Also, SQL server instance is on a different machine.
> I don't think that the report is even running. Does reporting services use
> the SQL agent?
> "mike" <milop@.slomins.com> wrote in message
> news:Or03HXtuFHA.2076@.TK2MSFTNGP14.phx.gbl...
> > Hello.
> >
> > I have created a domain account, granted the account Administrator access
> > on the report server machine, have changed the two windows services to run
> > as that account, and have created an Exchange mailbox for the domain
> > account.
> >
> > I created a simple report that has no data source. I created a shared
> > calendar that runs every 1 minute. I subscribed to the report on that
> > schedule, no report.
> >
> > The report is not being emailed.
> >
> > Any thoughts?
> >
> > Thanks in advance,
> >
> > Mike
> >
>
>|||As Per my knowledge an SQL Agent job is created for each schedule. SQL Server
Agent is very much required to run the Scheduled SRS Reports.
Ashish
"ProJester" wrote:
> No,Mike it does not.
>
> "mike" wrote:
> > Also, SQL server instance is on a different machine.
> >
> > I don't think that the report is even running. Does reporting services use
> > the SQL agent?
> >
> > "mike" <milop@.slomins.com> wrote in message
> > news:Or03HXtuFHA.2076@.TK2MSFTNGP14.phx.gbl...
> > > Hello.
> > >
> > > I have created a domain account, granted the account Administrator access
> > > on the report server machine, have changed the two windows services to run
> > > as that account, and have created an Exchange mailbox for the domain
> > > account.
> > >
> > > I created a simple report that has no data source. I created a shared
> > > calendar that runs every 1 minute. I subscribed to the report on that
> > > schedule, no report.
> > >
> > > The report is not being emailed.
> > >
> > > Any thoughts?
> > >
> > > Thanks in advance,
> > >
> > > Mike
> > >
> >
> >
> >sql
Friday, March 9, 2012
Next Range Starting Value Too High
Hi, I've got a push merge replication set up between two sql servers on the
same domain. I have a table with about 1200 records in it. For some reason
when I publish the article and set the identity range values it chooses a
Next Range Starting Value of over 7000000 when there are only the 1200
records in the table (identity range of 100).
The table constraints at the publisher show the range of 1200 to 1300 but at
the subscriber it shows like 7000000 to 7000100.
Can I change it so that it forces it use a more reasonable number like 1300
to 1400?
When you setup the publication what did you specify as the values of
@.pub_identity_range and @.identity_range parameter to sp_addmergearticle?What
did you set as the identity range values in the UI? I believe you must have
set a very high value for the pub identity range and that is the reason you
are seeing these huge numbers on the subscriber. You can change the
pub_identity_range parameter by using sp_changemergearticle. However that
will not affect the max number that has already been allocated. Next time
you setup the publication use lower values for the @.pub_identity_range
parameter.
Thanks,
Jayanthi
"MBurns" <MBurns@.discussions.microsoft.com> wrote in message
news:577A372C-C296-4214-80D1-2D2BE5A25F97@.microsoft.com...
> Hi, I've got a push merge replication set up between two sql servers on
the
> same domain. I have a table with about 1200 records in it. For some reason
> when I publish the article and set the identity range values it chooses a
> Next Range Starting Value of over 7000000 when there are only the 1200
> records in the table (identity range of 100).
> The table constraints at the publisher show the range of 1200 to 1300 but
at
> the subscriber it shows like 7000000 to 7000100.
> Can I change it so that it forces it use a more reasonable number like
1300
> to 1400?
same domain. I have a table with about 1200 records in it. For some reason
when I publish the article and set the identity range values it chooses a
Next Range Starting Value of over 7000000 when there are only the 1200
records in the table (identity range of 100).
The table constraints at the publisher show the range of 1200 to 1300 but at
the subscriber it shows like 7000000 to 7000100.
Can I change it so that it forces it use a more reasonable number like 1300
to 1400?
When you setup the publication what did you specify as the values of
@.pub_identity_range and @.identity_range parameter to sp_addmergearticle?What
did you set as the identity range values in the UI? I believe you must have
set a very high value for the pub identity range and that is the reason you
are seeing these huge numbers on the subscriber. You can change the
pub_identity_range parameter by using sp_changemergearticle. However that
will not affect the max number that has already been allocated. Next time
you setup the publication use lower values for the @.pub_identity_range
parameter.
Thanks,
Jayanthi
"MBurns" <MBurns@.discussions.microsoft.com> wrote in message
news:577A372C-C296-4214-80D1-2D2BE5A25F97@.microsoft.com...
> Hi, I've got a push merge replication set up between two sql servers on
the
> same domain. I have a table with about 1200 records in it. For some reason
> when I publish the article and set the identity range values it chooses a
> Next Range Starting Value of over 7000000 when there are only the 1200
> records in the table (identity range of 100).
> The table constraints at the publisher show the range of 1200 to 1300 but
at
> the subscriber it shows like 7000000 to 7000100.
> Can I change it so that it forces it use a more reasonable number like
1300
> to 1400?
Wednesday, March 7, 2012
Newly created witness server only connects to one of the partners?
We've been running a mirrored database (using certificates since we don't have a domain) and it's all working well. Last week we decided to add a witness for automatic failovers, but for some reason I just can not get the witness to connect to the Partner2 server.
See screenshot here
Please help me troubleshoot this - I re-created the endpoints / users / certificates but it's still not working. Where can I get more information on what exactly the problem is? Can I test the endpoints somehow?
Hello. I started from scratch on a test environment and I get the exact same problem. On the mirror I get that Witness Connection status as Disconnected.
I don't use certificates and also no encrypton as in this tutorial: http://wiki.cdyne.com/index.php/Mirroring_SQL_Server_2005
The direct result is that automatic failover does not work.
Some help will be great!
|||I have the exact problem. I don't use certificates and encryption is off as suggested in this article: http://wiki.cdyne.com/index.php/Mirroring_SQL_Server_2005
I get status disconnected and the automatic failover does not work.
|||I have the exact problem. I don't use certificates and encryption is off as suggested in this article: http://wiki.cdyne.com/index.php/Mirroring_SQL_Server_2005
I get status disconnected and the automatic failover does not work.
|||I managed to make it work, but my solution is really convoluted and made me feel really uneasy:
- Setup a HOSTS file entry on Partner1 and Partner2 to point the witness IP address to the name WITNESS:
10.1.0.123 WITNESS
- Add the witness to the DB using the HOSTS entry (in TSQL)
alter database MyDatabase set witness = 'tcp://WITNESS:5022'
- Check mirroring monitor. Monitor confirms that the winess is only connected to Partner1
- Change the HOSTS entry on Partner1 to the wrong IP address for WITNESS:
0.0.0.0 WITNESS
- Restart the SQL Service on the Witness server. After the restart, mirroring monitor shows that the witness is now connected to Partner2, and not to Partner1
- Fix the HOSTS entry on Partner1 to the correct IP address again
- Wait 10 mins
- Check mirroring monitor - it now shows the witness connected to both servers! (if it's still not connected to Partner1, restart the witness again)
What? This makes no sense, but it worked for me.
|||You know what. I followed your instructions step by step and indeed it works. But this is not a way I declare myself satisfied either...
It makes no sense... I wonder how anyone was able to make this work as it seems that this is a clear bug.
|||If someone wants the step by step to reproduce this I can tell it. It's a fairly basic process, following the instructions and still it doesn't work...|||Anyway just to let you know I downloaded from Microsoft their SQL2005 in VHD (virtual hard drive) format and ran it under virtual server. And I tried step by step and it's giving the exact problem... there is something wrong there for sure.
No one willing to comment on this so far?
|||I found that simply restarting SQL Server on the witness server solves this issue.
-dta
|||how exactlly do you do that? add entry to the hosts file? be exact please, i'm new and not very good with t-sqlNewly created witness server only connects to one of the partners?
We've been running a mirrored database (using certificates since we don't have a domain) and it's all working well. Last week we decided to add a witness for automatic failovers, but for some reason I just can not get the witness to connect to the Partner2 server.
See screenshot here
Please help me troubleshoot this - I re-created the endpoints / users / certificates but it's still not working. Where can I get more information on what exactly the problem is? Can I test the endpoints somehow?
Hello. I started from scratch on a test environment and I get the exact same problem. On the mirror I get that Witness Connection status as Disconnected.
I don't use certificates and also no encrypton as in this tutorial: http://wiki.cdyne.com/index.php/Mirroring_SQL_Server_2005
The direct result is that automatic failover does not work.
Some help will be great!
|||I have the exact problem. I don't use certificates and encryption is off as suggested in this article: http://wiki.cdyne.com/index.php/Mirroring_SQL_Server_2005
I get status disconnected and the automatic failover does not work.
|||I have the exact problem. I don't use certificates and encryption is off as suggested in this article: http://wiki.cdyne.com/index.php/Mirroring_SQL_Server_2005
I get status disconnected and the automatic failover does not work.
|||I managed to make it work, but my solution is really convoluted and made me feel really uneasy:
- Setup a HOSTS file entry on Partner1 and Partner2 to point the witness IP address to the name WITNESS:
10.1.0.123 WITNESS
- Add the witness to the DB using the HOSTS entry (in TSQL)
alter database MyDatabase set witness = 'tcp://WITNESS:5022'
- Check mirroring monitor. Monitor confirms that the winess is only connected to Partner1
- Change the HOSTS entry on Partner1 to the wrong IP address for WITNESS:
0.0.0.0 WITNESS
- Restart the SQL Service on the Witness server. After the restart, mirroring monitor shows that the witness is now connected to Partner2, and not to Partner1
- Fix the HOSTS entry on Partner1 to the correct IP address again
- Wait 10 mins
- Check mirroring monitor - it now shows the witness connected to both servers! (if it's still not connected to Partner1, restart the witness again)
What? This makes no sense, but it worked for me.
|||You know what. I followed your instructions step by step and indeed it works. But this is not a way I declare myself satisfied either...
It makes no sense... I wonder how anyone was able to make this work as it seems that this is a clear bug.
|||If someone wants the step by step to reproduce this I can tell it. It's a fairly basic process, following the instructions and still it doesn't work...|||Anyway just to let you know I downloaded from Microsoft their SQL2005 in VHD (virtual hard drive) format and ran it under virtual server. And I tried step by step and it's giving the exact problem... there is something wrong there for sure.
No one willing to comment on this so far?
|||I found that simply restarting SQL Server on the witness server solves this issue.
-dta
|||how exactlly do you do that? add entry to the hosts file? be exact please, i'm new and not very good with t-sql
Subscribe to:
Posts (Atom)