Just wondering if anyone has run into any problems while trying to test the
.700 SP for 9.05.
I am running into some odd errors while trying to run the Schema changes and
wasn't sure if this was something particular to the database I happen to be
working on, or if anyone else has run into errors as well?
I am not sure exactly where the error is located, but I am getting this
right now running the 905.700DF.SQL schema change.
Msg 102, Level 15, State 1, Server SSMDB, Line 1
Incorrect syntax near '-'.
Msg 156, Level 15, State 1, Server SSMDB, Line 1
Incorrect syntax near the keyword 'SET'.
I have gotten it both running through the Schema Change Icon, as well as
running directly in SQL. Oddly, I actually needed to have both identical
32-bit and 64-bit System DSNs setup in order to run the Schema Change at all
with the Icons.
[Non-text portions of this message have been removed]
I ran the schema change from 9.05.607b to 9.06.700 without any errors. I used the schema update on my 64-bit server, I do have both the 32-bit & 64-bit ODBC DSNs set. We're SQL 64-bit, non unicode.
--- In vantage@yahoogroups.com, Ned <TechnoBabbly@...> wrote:
Just wondering if anyone has run into any problems while trying to test the .700 SP for 9.05.
Hi,
I too am in the process of performing test upgrades from 606a to 700b. I have not seen this problem with the schema change. Not wanting to sound rude, but what is your environment setup like? If you are attempting to run the upgrade from a machine which is acting as you app server and you have SQL on another machine, I’ve been told you need to have at least the SQL Express installed on the app server machine (not just the client connectivity). Once again I don’t think that is your problem. The only other thing I can suggest is check for the latest download of the install. the 700b2 patch is now available.
Hope this helps.
[Non-text portions of this message have been removed]
There is no issue with the setup. I can run the conversion on the same server for a different database and it runs fine. I was just checking here to see if anyone else had a similar problem, Epicor is stumped right now as well, so I am in the process of uploading the DB to them.
Also, there is absolutely no need for SQL Express on an Appserver if the SQL is on a different server, anyone who told you that was probably just trying to go the easy way in making sure the SQL Native Client was located on the Appserver.
Only major hitch I have run into, other than this, was needing to have both a 32 and 64-bit DSN setup to run the schema changes and admin tools.
Hi,
I too am in the process of performing test upgrades from 606a to 700b. I have not seen this problem with the schema change. Not wanting to sound rude, but what is your environment setup like? If you are attempting to run the upgrade from a machine which is acting as you app server and you have SQL on another machine, I’ve been told you need to have at least the SQL Express installed on the app server machine (not just the client connectivity). Once again I don’t think that is your problem. The only other thing I can suggest is check for the latest download of the install. the 700b2 patch is now available.
Hope this helps.
[Non-text portions of this message have been removed]
I've done a few upgrades on different machines now since my last post and I've had mixed errors from the initial one that bombed completely to one I just did this evening that went through perfectly, that being said our Finance team were testing service contracts and have come up with a few anomalies.
With regards to SQL, all I can say is that although the Native client showed in available list of ODBC drivers, it was not until I installed SQL on that App server could I get the conversion to go through without error. Very weird. I can only say that the documentation does say to run the conversion from the SQL server...
If you have Epicors attention then I guess stick with that, the only other thing I can suggest is you could perhaps restore your database, do a prorest and attempt the schema change and conversion again. I'm sure you would have already done that by the sounds if it. Make sure you check the cs\*TCP.pf files for the correct DSN
--- In vantage@yahoogroups.com, Ned <TechnoBabbly@...> wrote:
>
> There is no issue with the setup. I can run the conversion on the same server for a different database and it runs fine. I was just checking here to see if anyone else had a similar problem, Epicor is stumped right now as well, so I am in the process of uploading the DB to them.
>
> Also, there is absolutely no need for SQL Express on an Appserver if the SQL is on a different server, anyone who told you that was probably just trying to go the easy way in making sure the SQL Native Client was located on the Appserver.
>
> Only major hitch I have run into, other than this, was needing to have both a 32 and 64-bit DSN setup to run the schema changes and admin tools.
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Simon Hall
> Sent: Friday, July 06, 2012 7:25 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Testing .700 - Schema Change errors
>
> Hi,
> I too am in the process of performing test upgrades from 606a to 700b. I have not seen this problem with the schema change. Not wanting to sound rude, but what is your environment setup like? If you are attempting to run the upgrade from a machine which is acting as you app server and you have SQL on another machine, I’ve been told you need to have at least the SQL Express installed on the app server machine (not just the client connectivity). Once again I don’t think that is your problem. The only other thing I can suggest is check for the latest download of the install. the 700b2 patch is now available.
>
> Hope this helps.
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have already linked your email address to a yahoo id to enable access. )
> (1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
> (2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>
I have seen that error when upgrading to 700 from 9.05.604a. I was advised to install SQL Express on the server. After installing SQL Express on the server the schema converted.
Sent from my iPad
On Jul 6, 2012, at 7:24 PM, "Simon Hall" <s1mhall@...> wrote:
> Hi,
> I too am in the process of performing test upgrades from 606a to 700b. I have not seen this problem with the schema change. Not wanting to sound rude, but what is your environment setup like? If you are attempting to run the upgrade from a machine which is acting as you app server and you have SQL on another machine, I’ve been told you need to have at least the SQL Express installed on the app server machine (not just the client connectivity). Once again I don’t think that is your problem. The only other thing I can suggest is check for the latest download of the install. the 700b2 patch is now available.
>
> Hope this helps.
>
> [Non-text portions of this message have been removed]
>
>
[Non-text portions of this message have been removed]
Did you try reindexing the database before converting?
Sent from my iPad
On Jul 10, 2012, at 7:25 AM, "s1mhall" <s1mhall@...> wrote:
> I've done a few upgrades on different machines now since my last post and I've had mixed errors from the initial one that bombed completely to one I just did this evening that went through perfectly, that being said our Finance team were testing service contracts and have come up with a few anomalies.
>
> With regards to SQL, all I can say is that although the Native client showed in available list of ODBC drivers, it was not until I installed SQL on that App server could I get the conversion to go through without error. Very weird. I can only say that the documentation does say to run the conversion from the SQL server...
>
> If you have Epicors attention then I guess stick with that, the only other thing I can suggest is you could perhaps restore your database, do a prorest and attempt the schema change and conversion again. I'm sure you would have already done that by the sounds if it. Make sure you check the cs\*TCP.pf files for the correct DSN
>
> --- In vantage@yahoogroups.com, Ned <TechnoBabbly@...> wrote:
> >
> > There is no issue with the setup. I can run the conversion on the same server for a different database and it runs fine. I was just checking here to see if anyone else had a similar problem, Epicor is stumped right now as well, so I am in the process of uploading the DB to them.
> >
> > Also, there is absolutely no need for SQL Express on an Appserver if the SQL is on a different server, anyone who told you that was probably just trying to go the easy way in making sure the SQL Native Client was located on the Appserver.
> >
> > Only major hitch I have run into, other than this, was needing to have both a 32 and 64-bit DSN setup to run the schema changes and admin tools.
> >
> > -----Original Message-----
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Simon Hall
> > Sent: Friday, July 06, 2012 7:25 PM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] Re: Testing .700 - Schema Change errors
> >
> > Hi,
> > I too am in the process of performing test upgrades from 606a to 700b. I have not seen this problem with the schema change. Not wanting to sound rude, but what is your environment setup like? If you are attempting to run the upgrade from a machine which is acting as you app server and you have SQL on another machine, I’ve been told you need to have at least the SQL Express installed on the app server machine (not just the client connectivity). Once again I don’t think that is your problem. The only other thing I can suggest is check for the latest download of the install. the 700b2 patch is now available.
> >
> > Hope this helps.
> >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> > ------------------------------------
> >
> > Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have already linked your email address to a yahoo id to enable access. )
> > (1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
> > (2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
> > (3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
> >
>
>
[Non-text portions of this message have been removed]
I have to say I didn't try reindexing the database, but I do have database management plans on the SQL server that keep things sorted.
Cheers
--- In vantage@yahoogroups.com, Brinda Whitaker <bkw_mail@...> wrote:
>
> Did you try reindexing the database before converting?
>
> Sent from my iPad
>
> On Jul 10, 2012, at 7:25 AM, "s1mhall" <s1mhall@...> wrote:
>
> > I've done a few upgrades on different machines now since my last post and I've had mixed errors from the initial one that bombed completely to one I just did this evening that went through perfectly, that being said our Finance team were testing service contracts and have come up with a few anomalies.
> >
> > With regards to SQL, all I can say is that although the Native client showed in available list of ODBC drivers, it was not until I installed SQL on that App server could I get the conversion to go through without error. Very weird. I can only say that the documentation does say to run the conversion from the SQL server...
> >
> > If you have Epicors attention then I guess stick with that, the only other thing I can suggest is you could perhaps restore your database, do a prorest and attempt the schema change and conversion again. I'm sure you would have already done that by the sounds if it. Make sure you check the cs\*TCP.pf files for the correct DSN
> >
> > --- In vantage@yahoogroups.com, Ned <TechnoBabbly@> wrote:
> > >
> > > There is no issue with the setup. I can run the conversion on the same server for a different database and it runs fine. I was just checking here to see if anyone else had a similar problem, Epicor is stumped right now as well, so I am in the process of uploading the DB to them.
> > >
> > > Also, there is absolutely no need for SQL Express on an Appserver if the SQL is on a different server, anyone who told you that was probably just trying to go the easy way in making sure the SQL Native Client was located on the Appserver.
> > >
> > > Only major hitch I have run into, other than this, was needing to have both a 32 and 64-bit DSN setup to run the schema changes and admin tools.
> > >
> > > -----Original Message-----
> > > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of Simon Hall
> > > Sent: Friday, July 06, 2012 7:25 PM
> > > To: vantage@yahoogroups.com
> > > Subject: [Vantage] Re: Testing .700 - Schema Change errors
> > >
> > > Hi,
> > > I too am in the process of performing test upgrades from 606a to 700b. I have not seen this problem with the schema change. Not wanting to sound rude, but what is your environment setup like? If you are attempting to run the upgrade from a machine which is acting as you app server and you have SQL on another machine, I’ve been told you need to have at least the SQL Express installed on the app server machine (not just the client connectivity). Once again I don’t think that is your problem. The only other thing I can suggest is check for the latest download of the install. the 700b2 patch is now available.
> > >
> > > Hope this helps.
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> > >
> > >
> > > ------------------------------------
> > >
> > > Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must have already linked your email address to a yahoo id to enable access. )
> > > (1) To access the Files Section of our Yahoo!Group for Report Builder and Crystal Reports and other 'goodies', please goto: http://groups.yahoo.com/group/vantage/files/.
> > > (2) To search through old msg's goto: http://groups.yahoo.com/group/vantage/messages
> > > (3) To view links to Vendors that provide Vantage services goto: http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
> > >
> >
> >
>
> [Non-text portions of this message have been removed]
>