|
Anil, the script I sent before was in error,
I really need to review better before I hit send. This has the proper corrections if you
need the script --Start Script use Master go exec sp_configure 'allow updates',
1 reconfigure WITH
OVERRIDE go Begin Transaction update sysObjects set uid = user_id('INFORMATION_SCHEMA') where name in( 'SCHEMATA', 'TABLES', 'TABLE_CONSTRAINTS', 'TABLE_PRIVILEGES', 'COLUMNS', 'COLUMN_DOMAIN_USAGE', 'COLUMN_PRIVILEGES', 'DOMAINS', 'DOMAIN_CONSTRAINTS', 'KEY_COLUMN_USAGE', 'REFERENTIAL_CONSTRAINTS', 'CHECK_CONSTRAINTS', 'CONSTRAINT_TABLE_USAGE', 'CONSTRAINT_COLUMN_USAGE', 'VIEWS', 'VIEW_TABLE_USAGE', 'VIEW_COLUMN_USAGE', 'ROUTINES', 'PARAMETERS', 'ROUTINE_COLUMNS' ) Commit Transaction go exec sp_configure 'allow updates', 0 reconfigure WITH
OVERRIDE --End Script -----Original Message----- Anil, Look on your SQL server
at the Master data base views there should be approximately 20 views with the
owner listed as INFORMATION_SCHEMA, in particular the one view named VIEWS is
what Axapta is trying to use, If
the owner is DBO it would be my guess you at some time accidentally ran a
script against the Master DB that changed the owner of all objects to DBO. If this is your problem here’s a
SQL script to fix it, Have a
good back up of the MASTER db and then run this against the MASTER db using query
analyzer, it will set all of the views in sql standard that are supposed to
belong to Information_Schema ownership. Best regards - use
Master go exec
sp_configure 'allow updates', 1 reconfigure WITH OVERRIDE go Begin Transaction update sysObject set uid = user_id('INFORMATION_SCHEMA') where name in( SCHEMATA, TABLES, TABLE_CONSTRAINTS, TABLE_PRIVILEGES, COLUMNS, COLUMN_DOMAIN_USAGE, COLUMN_PRIVILEGES, DOMAINS, DOMAIN_CONSTRAINTS, KEY_COLUMN_USAGE, REFERENTIAL_CONSTRAINTS, CHECK_CONSTRAINTS, CONSTRAINT_TABLE_USAGE, CONSTRAINT_COLUMN_USAGE, VIEWS, VIEW_TABLE_USAGE, VIEW_COLUMN_USAGE, ROUTINES, PARAMETERS, ROUTINE_COLUMNS) Commit Transaction exec sp_configure 'allow updates', 0 reconfigure WITH OVERRIDE -----Original Message----- Thanks for all replies.. I checked user rights on SQL
Server, owner of the views is the same owner of the tables. But i can’t
find any solution. I use a clear solution, i reinstall the Axapta. No
matters now.. Regards, Anil Ozay From: ax
[mailto:[EMAIL PROTECTED] The problem may include user
rights in MS Sql . Check if sql is configured
Yahoo! Groups Links
|
- RE: [development-axapta] AX ... Kim Truelsen \(MICROSOFT BUSINESS SOLUTIONS\)
- Re: [development-axapta... ax
- RE: [development-axapta... Anil Ozay
- RE: [development-ax... Preston A. Larimer
- [development-ax... Preston A. Larimer
- [development-ax... James Flavell
- Re: [develo... Pascal Dutour Geerling
- RE: [d... James Flavell
- RE: [development-axapta... Anil Ozay

