Recently upgraded from CR XI to CR XI R2, and have a major irritation with it. Not a show stopper, but it slows us down.
Every time it starts up, it goes through a "Please wait whilst Windows Installs Crystal Reports". Typically adds a good 2-3 minutes to the app startup time.
Our main application development is on the Remedy AR System, and I went through an update to the user tool last night. The Remedy User tool ships with Crystal Redistributables, and on an update you don't have any options as to what gets installed. It should normally take a couple of minutes to update, but every time the install touched anything even vaguely Crystal, it went through the "Please wait whilst Windows installs CR". Took over 90 minutes to install.
So, its not a show stopper, but the behaviour of R2 is totally different to the prior CR XI release. Anyone else experienced this, and found a solution?Yes i am also facing the same problem.
Every time i open crystal report XI R2 it configures itself.
May be a bug.
Showing posts with label major. Show all posts
Showing posts with label major. Show all posts
Monday, March 19, 2012
Friday, March 9, 2012
Issue with Installation SQL 2005
We are running some tests here to evaluate whether to upgrade and switch som
e
of the databases from Oracle to SQL 2005, but running into a major issue.
We have a W2003 server where we used to have SQL 2000 running. We upgraded
that to SQL 2005 server. So far, so good, but the client tool (Management
Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
return anything.
However trying to install the client tools gives a friendly that it is
already there, but it isn't. I tried a client install on a laptop which
works, but on the server it gives a problem.
Are you not able to install the client tools on the server?
We tried to remove SQL 2005 from Remove Programs which removes it from the
list, but SQL server remains installed and we have no way to access the
databases.
Hopefully someone can help here, because it isn't anything good on the
perception of the product, while from a functionality perspective the produc
t
looks promising. We tried to install SQL 2005 Standard Edition.
Thanks in advance.
MattTry uninstalling and reinstalling the client tools.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> We are running some tests here to evaluate whether to upgrade and switch
> some
> of the databases from Oracle to SQL 2005, but running into a major issue.
> We have a W2003 server where we used to have SQL 2000 running. We upgraded
> that to SQL 2005 server. So far, so good, but the client tool (Management
> Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> return anything.
> However trying to install the client tools gives a friendly that it is
> already there, but it isn't. I tried a client install on a laptop which
> works, but on the server it gives a problem.
> Are you not able to install the client tools on the server?
> We tried to remove SQL 2005 from Remove Programs which removes it from the
> list, but SQL server remains installed and we have no way to access the
> databases.
> Hopefully someone can help here, because it isn't anything good on the
> perception of the product, while from a functionality perspective the
> product
> looks promising. We tried to install SQL 2005 Standard Edition.
> Thanks in advance.
> Matt|||YES, it worked. Thank you!
"Roger Wolter[MSFT]" wrote:
> Try uninstalling and reinstalling the client tools.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
>
>
e
of the databases from Oracle to SQL 2005, but running into a major issue.
We have a W2003 server where we used to have SQL 2000 running. We upgraded
that to SQL 2005 server. So far, so good, but the client tool (Management
Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
return anything.
However trying to install the client tools gives a friendly that it is
already there, but it isn't. I tried a client install on a laptop which
works, but on the server it gives a problem.
Are you not able to install the client tools on the server?
We tried to remove SQL 2005 from Remove Programs which removes it from the
list, but SQL server remains installed and we have no way to access the
databases.
Hopefully someone can help here, because it isn't anything good on the
perception of the product, while from a functionality perspective the produc
t
looks promising. We tried to install SQL 2005 Standard Edition.
Thanks in advance.
MattTry uninstalling and reinstalling the client tools.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> We are running some tests here to evaluate whether to upgrade and switch
> some
> of the databases from Oracle to SQL 2005, but running into a major issue.
> We have a W2003 server where we used to have SQL 2000 running. We upgraded
> that to SQL 2005 server. So far, so good, but the client tool (Management
> Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> return anything.
> However trying to install the client tools gives a friendly that it is
> already there, but it isn't. I tried a client install on a laptop which
> works, but on the server it gives a problem.
> Are you not able to install the client tools on the server?
> We tried to remove SQL 2005 from Remove Programs which removes it from the
> list, but SQL server remains installed and we have no way to access the
> databases.
> Hopefully someone can help here, because it isn't anything good on the
> perception of the product, while from a functionality perspective the
> product
> looks promising. We tried to install SQL 2005 Standard Edition.
> Thanks in advance.
> Matt|||YES, it worked. Thank you!
"Roger Wolter[MSFT]" wrote:
> Try uninstalling and reinstalling the client tools.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
>
>
Issue with Installation SQL 2005
We are running some tests here to evaluate whether to upgrade and switch some
of the databases from Oracle to SQL 2005, but running into a major issue.
We have a W2003 server where we used to have SQL 2000 running. We upgraded
that to SQL 2005 server. So far, so good, but the client tool (Management
Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
return anything.
However trying to install the client tools gives a friendly that it is
already there, but it isn't. I tried a client install on a laptop which
works, but on the server it gives a problem.
Are you not able to install the client tools on the server?
We tried to remove SQL 2005 from Remove Programs which removes it from the
list, but SQL server remains installed and we have no way to access the
databases.
Hopefully someone can help here, because it isn't anything good on the
perception of the product, while from a functionality perspective the product
looks promising. We tried to install SQL 2005 Standard Edition.
Thanks in advance.
Matt
Try uninstalling and reinstalling the client tools.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> We are running some tests here to evaluate whether to upgrade and switch
> some
> of the databases from Oracle to SQL 2005, but running into a major issue.
> We have a W2003 server where we used to have SQL 2000 running. We upgraded
> that to SQL 2005 server. So far, so good, but the client tool (Management
> Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> return anything.
> However trying to install the client tools gives a friendly that it is
> already there, but it isn't. I tried a client install on a laptop which
> works, but on the server it gives a problem.
> Are you not able to install the client tools on the server?
> We tried to remove SQL 2005 from Remove Programs which removes it from the
> list, but SQL server remains installed and we have no way to access the
> databases.
> Hopefully someone can help here, because it isn't anything good on the
> perception of the product, while from a functionality perspective the
> product
> looks promising. We tried to install SQL 2005 Standard Edition.
> Thanks in advance.
> Matt
|||YES, it worked. Thank you!
"Roger Wolter[MSFT]" wrote:
> Try uninstalling and reinstalling the client tools.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
>
>
of the databases from Oracle to SQL 2005, but running into a major issue.
We have a W2003 server where we used to have SQL 2000 running. We upgraded
that to SQL 2005 server. So far, so good, but the client tool (Management
Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
return anything.
However trying to install the client tools gives a friendly that it is
already there, but it isn't. I tried a client install on a laptop which
works, but on the server it gives a problem.
Are you not able to install the client tools on the server?
We tried to remove SQL 2005 from Remove Programs which removes it from the
list, but SQL server remains installed and we have no way to access the
databases.
Hopefully someone can help here, because it isn't anything good on the
perception of the product, while from a functionality perspective the product
looks promising. We tried to install SQL 2005 Standard Edition.
Thanks in advance.
Matt
Try uninstalling and reinstalling the client tools.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> We are running some tests here to evaluate whether to upgrade and switch
> some
> of the databases from Oracle to SQL 2005, but running into a major issue.
> We have a W2003 server where we used to have SQL 2000 running. We upgraded
> that to SQL 2005 server. So far, so good, but the client tool (Management
> Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> return anything.
> However trying to install the client tools gives a friendly that it is
> already there, but it isn't. I tried a client install on a laptop which
> works, but on the server it gives a problem.
> Are you not able to install the client tools on the server?
> We tried to remove SQL 2005 from Remove Programs which removes it from the
> list, but SQL server remains installed and we have no way to access the
> databases.
> Hopefully someone can help here, because it isn't anything good on the
> perception of the product, while from a functionality perspective the
> product
> looks promising. We tried to install SQL 2005 Standard Edition.
> Thanks in advance.
> Matt
|||YES, it worked. Thank you!
"Roger Wolter[MSFT]" wrote:
> Try uninstalling and reinstalling the client tools.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
>
>
Issue with Installation SQL 2005
We are running some tests here to evaluate whether to upgrade and switch some
of the databases from Oracle to SQL 2005, but running into a major issue.
We have a W2003 server where we used to have SQL 2000 running. We upgraded
that to SQL 2005 server. So far, so good, but the client tool (Management
Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
return anything.
However trying to install the client tools gives a friendly that it is
already there, but it isn't. I tried a client install on a laptop which
works, but on the server it gives a problem.
Are you not able to install the client tools on the server?
We tried to remove SQL 2005 from Remove Programs which removes it from the
list, but SQL server remains installed and we have no way to access the
databases.
Hopefully someone can help here, because it isn't anything good on the
perception of the product, while from a functionality perspective the product
looks promising. We tried to install SQL 2005 Standard Edition.
Thanks in advance.
MattTry uninstalling and reinstalling the client tools.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> We are running some tests here to evaluate whether to upgrade and switch
> some
> of the databases from Oracle to SQL 2005, but running into a major issue.
> We have a W2003 server where we used to have SQL 2000 running. We upgraded
> that to SQL 2005 server. So far, so good, but the client tool (Management
> Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> return anything.
> However trying to install the client tools gives a friendly that it is
> already there, but it isn't. I tried a client install on a laptop which
> works, but on the server it gives a problem.
> Are you not able to install the client tools on the server?
> We tried to remove SQL 2005 from Remove Programs which removes it from the
> list, but SQL server remains installed and we have no way to access the
> databases.
> Hopefully someone can help here, because it isn't anything good on the
> perception of the product, while from a functionality perspective the
> product
> looks promising. We tried to install SQL 2005 Standard Edition.
> Thanks in advance.
> Matt|||YES, it worked. Thank you!
"Roger Wolter[MSFT]" wrote:
> Try uninstalling and reinstalling the client tools.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> > We are running some tests here to evaluate whether to upgrade and switch
> > some
> > of the databases from Oracle to SQL 2005, but running into a major issue.
> >
> > We have a W2003 server where we used to have SQL 2000 running. We upgraded
> > that to SQL 2005 server. So far, so good, but the client tool (Management
> > Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> > return anything.
> >
> > However trying to install the client tools gives a friendly that it is
> > already there, but it isn't. I tried a client install on a laptop which
> > works, but on the server it gives a problem.
> >
> > Are you not able to install the client tools on the server?
> >
> > We tried to remove SQL 2005 from Remove Programs which removes it from the
> > list, but SQL server remains installed and we have no way to access the
> > databases.
> >
> > Hopefully someone can help here, because it isn't anything good on the
> > perception of the product, while from a functionality perspective the
> > product
> > looks promising. We tried to install SQL 2005 Standard Edition.
> >
> > Thanks in advance.
> >
> > Matt
>
>
of the databases from Oracle to SQL 2005, but running into a major issue.
We have a W2003 server where we used to have SQL 2000 running. We upgraded
that to SQL 2005 server. So far, so good, but the client tool (Management
Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
return anything.
However trying to install the client tools gives a friendly that it is
already there, but it isn't. I tried a client install on a laptop which
works, but on the server it gives a problem.
Are you not able to install the client tools on the server?
We tried to remove SQL 2005 from Remove Programs which removes it from the
list, but SQL server remains installed and we have no way to access the
databases.
Hopefully someone can help here, because it isn't anything good on the
perception of the product, while from a functionality perspective the product
looks promising. We tried to install SQL 2005 Standard Edition.
Thanks in advance.
MattTry uninstalling and reinstalling the client tools.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> We are running some tests here to evaluate whether to upgrade and switch
> some
> of the databases from Oracle to SQL 2005, but running into a major issue.
> We have a W2003 server where we used to have SQL 2000 running. We upgraded
> that to SQL 2005 server. So far, so good, but the client tool (Management
> Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> return anything.
> However trying to install the client tools gives a friendly that it is
> already there, but it isn't. I tried a client install on a laptop which
> works, but on the server it gives a problem.
> Are you not able to install the client tools on the server?
> We tried to remove SQL 2005 from Remove Programs which removes it from the
> list, but SQL server remains installed and we have no way to access the
> databases.
> Hopefully someone can help here, because it isn't anything good on the
> perception of the product, while from a functionality perspective the
> product
> looks promising. We tried to install SQL 2005 Standard Edition.
> Thanks in advance.
> Matt|||YES, it worked. Thank you!
"Roger Wolter[MSFT]" wrote:
> Try uninstalling and reinstalling the client tools.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Matt" <Matt@.discussions.microsoft.com> wrote in message
> news:DD66D067-60E6-4B2B-8574-1C3DE32A4FFA@.microsoft.com...
> > We are running some tests here to evaluate whether to upgrade and switch
> > some
> > of the databases from Oracle to SQL 2005, but running into a major issue.
> >
> > We have a W2003 server where we used to have SQL 2000 running. We upgraded
> > that to SQL 2005 server. So far, so good, but the client tool (Management
> > Studio) doesn't show up in the menu list. Running sqlwb.exe also doesn't
> > return anything.
> >
> > However trying to install the client tools gives a friendly that it is
> > already there, but it isn't. I tried a client install on a laptop which
> > works, but on the server it gives a problem.
> >
> > Are you not able to install the client tools on the server?
> >
> > We tried to remove SQL 2005 from Remove Programs which removes it from the
> > list, but SQL server remains installed and we have no way to access the
> > databases.
> >
> > Hopefully someone can help here, because it isn't anything good on the
> > perception of the product, while from a functionality perspective the
> > product
> > looks promising. We tried to install SQL 2005 Standard Edition.
> >
> > Thanks in advance.
> >
> > Matt
>
>
Issue with Identity Columns after replication Changes
Dear all,
We have an application that use merge replication between MSDE and Devices with SQL CE.
Due to a major application changes, we have to change our replication on all our workstation. Our process is the following:
- drop current replication
- recreate our replication
After first check our replication seems to work but after some test we have identify that all identity ranges have been reset on the workstation. As side effect, device start to reuse existing range and also existing value in the range.
- Have you ever encounter this type of issue?
- What can create it?
- Is our approach fully inappropriate?
Please let me know if you need more information,
Best regards,
I have a client (SQL2000<->SqlCE) that is experiencing similar problems. We have been unable to determine a cause as yet.
Symptoms:
-"duplicate key on insert" errors during replication for one table (two subscribers appearing to be sharing the same number range)
-"duplicate key on insert" error with a back-end process inserting data into a publisher table (diff to the one above)
The tables are using automatic identity range management and have been synchronising happily for a long time prior to this.
Does anyone know of any actions that might cause the automatic identity range management to go screwy like this?
|||You can try re-adjusting your identity ranges, look at sp_adjustpublisheridentityrange. Otherwise i'm not sure what could have caused the issue, maybe someone manually reset the identity seed on the dbs?Issue with Identity Columns after replication Changes
Dear all,
We have an application that use merge replication between MSDE and Devices with SQL CE.
Due to a major application changes, we have to change our replication on all our workstation. Our process is the following:
- drop current replication
- recreate our replication
After first check our replication seems to work but after some test we have identify that all identity ranges have been reset on the workstation. As side effect, device start to reuse existing range and also existing value in the range.
- Have you ever encounter this type of issue?
- What can create it?
- Is our approach fully inappropriate?
Please let me know if you need more information,
Best regards,
I have a client (SQL2000<->SqlCE) that is experiencing similar problems. We have been unable to determine a cause as yet.
Symptoms:
-"duplicate key on insert" errors during replication for one table (two subscribers appearing to be sharing the same number range)
-"duplicate key on insert" error with a back-end process inserting data into a publisher table (diff to the one above)
The tables are using automatic identity range management and have been synchronising happily for a long time prior to this.
Does anyone know of any actions that might cause the automatic identity range management to go screwy like this?
|||You can try re-adjusting your identity ranges, look at sp_adjustpublisheridentityrange. Otherwise i'm not sure what could have caused the issue, maybe someone manually reset the identity seed on the dbs?
Subscribe to:
Posts (Atom)