Rusty was correct! Follow his posts, do a little reading and you shouldn't have any issues. Substring ( cast ( SERVERPROPERTY ( 'productversion' ) as varchar ), 0, CHARINDEX ( '.', cast ( SERVERPROPERTY ( 'productversion' ) as varchar ), 0 )) Do we know if anyone at Microsoft looking at this? Allow me to show these folks how it is done (version independent): Microsoft needs to fire those foreign contractors.oh wait.they already DID! Even SP1 doesn't fix this issue.you'd think that DB connectivity and version checking would be easy in the year 2009. Great find! I ran into the EXACT issue this evening. I think MSOA reports this as the generic error: "The database that you requested could not be opened, or access denied." Was MSOA 2009 even tested against SQL 2008?
The substring() logic in this statement doesn't expect the version number to start with 2 digits so the statement errors out. SQL 2008 has an internal version number of 10.x.x.x while SQL 2005 has an internal version number of 9.x.x.x. If I run this same statement against a SQL 2005 instance it returns a single value of "9". I can see MSOA connect to SQL and execute the following statement: SELECT CASE WHEN patindex ( '%.%.%.%', ) > 0 THEN cast ( substring (, patindex ( '%.%.%.%', )-2, charindex ( '.', ltrim ( substring (, patindex ( '%.%.%.%', )- 2, 8 )))) as int ) ELSE 0 END If I take this statement and run it in SSMS directly, I get an error: Conversion failed when converting the nvarchar value '10.' to data type int. While running the restore from MSOA Data Tools, I also ran a SQL trace. I have a local SQL 2008 SP1 default (MSSQLSERVER) instance running and have set the MSOA instance name to MSSQLSERVER.
#MICROSOFT ACCOUNTING EXPRESS 2009 REVIEW PRO#
I'm attempting to restore a company backup in MSOA Pro 2009 SP1. I'm experiencing the same problem and I think I have a clue as to why, but I'm afraid it's going to require a fix from MS.
0 kommentar(er)
