Has anyone seen this?
Within 'Business Intelligence Development Studio' (BIDS) with a cube opened and the calculations tab selected, the design surface displays a message that reads:
Unexpected error occurred: 'Error in the application.'
This occurs in any project I open and it still occurs when I restart BIDS or the computer itself.
Any ideas? Can anyone suggest a remedy?
hello,
this might be caused by version mismatch between some binaries. i'd suggest checking the versions of msmdlocal.dll and msmgdsrv.dll and making sure that the ones installed into %ProgramFiles%\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\ are the same as those in %ProgramFiles%\Common Files\System\Ole DB\ (if they are not then try updating the ones in the PrivateAssemblies with the ones from ole db; you might want to save the original ones as to be able to get back to original state just in case...)
hope this helps,
|||
I had already seen a similar post noting this as the possible cause so I checked the file versions in the appropriate folders an found no missmatch.
From there I went on to install the latest hotfix (2153) to see if that would clear up the problem. It did not.
After consulting with a friend I decided do a complete reinstall of SQL Server 2005 and related tools and such.
After the complete reinstall (and before a SP1 update) the problem still existed. I still recieve the error on the design surface of the Calculation tab for any cube I open.
I am currently trying to install SP1 and encounterring problems.
With my first attempt the 'Installation Progress' window for Service Pack 1 Setup showed product 'Analysis Services' status as "Failed". Here are the contents of the log file after it completed.
09/27/2006 09:26:44.282 ================================================================================
09/27/2006 09:26:44.314 Hotfix package launched
09/27/2006 09:31:58.503 Attempting to install instance: SQL Server Native Client
09/27/2006 09:31:58.534 Attempting to install target: L-0960
09/27/2006 09:31:58.581 Attempting to install file: sqlncli.msi
09/27/2006 09:31:58.675 Attempting to install file: \\L-0960\c$\06f6082a049155a5f4e3ece3b75f69\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 09:31:58.722 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
09/27/2006 09:31:58.737 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 09:31:58.753 Failed to read registry key: Debug
09/27/2006 09:32:01.329 MSP returned 0: The action completed successfully.
09/27/2006 09:32:01.501 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 09:32:01.689 Failed to read registry key: Debug
09/27/2006 09:32:01.704 Successfully installed file: \\L-0960\c$\06f6082a049155a5f4e3ece3b75f69\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 09:32:01.720 Successfully installed target: L-0960
09/27/2006 09:32:01.735 Successfully installed instance: SQL Server Native Client
09/27/2006 09:32:01.751
09/27/2006 09:32:01.751 Product Status Summary:
09/27/2006 09:32:01.767 Product: SQL Server Native Client
09/27/2006 09:32:01.782 SQL Server Native Client (RTM ) - Success
09/27/2006 09:32:01.782
09/27/2006 09:32:01.798 Product: Setup Support Files
09/27/2006 09:32:01.814 Setup Support Files (RTM ) - Not Applied
09/27/2006 09:32:01.829
09/27/2006 09:32:01.829 Product: Database Services
09/27/2006 09:32:01.845 Database Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:01.892 Analysis Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:01.923 Reporting Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:01.970
09/27/2006 09:32:01.985 Product: Notification Services
09/27/2006 09:32:02.017 Notification Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:02.048
09/27/2006 09:32:02.110 Product: Integration Services
09/27/2006 09:32:02.141 Integration Services (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:02.173
09/27/2006 09:32:02.204 Product: Client Components
09/27/2006 09:32:02.251 Client Components (RTM 1399 ENU) - Not Applied
09/27/2006 09:32:02.282
09/27/2006 09:32:02.313 Product: MSXML 6.0 Parser
09/27/2006 09:32:02.360 MSXML 6.0 Parser (RTM ) - Not Applied
09/27/2006 09:32:02.391
09/27/2006 09:32:02.547 Product: SQLXML4
09/27/2006 09:32:02.641 SQLXML4 (RTM ) - Not Applied
09/27/2006 09:32:02.704
09/27/2006 09:32:02.735 Product: Backward Compatibility
09/27/2006 09:32:02.782 Backward Compatibility (RTM ) - Not Applied
09/27/2006 09:32:02.813
09/27/2006 09:32:02.844 Product: Microsoft SQL Server VSS Writer
09/27/2006 09:32:02.875 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
09/27/2006 09:32:02.907
After a restart I tried the Service Pack 1 installation again.
On this second attempt the 'Installation Progress' window for Service Pack 1 Setup showed product 'Analysis Services' status as "Warning".
Here are the contents of the log file after it completed.
09/27/2006 10:55:37.182 ================================================================================
09/27/2006 10:55:37.260 Hotfix package launched
09/27/2006 11:01:04.649 Attempting to install instance: SQL Server Native Client
09/27/2006 11:01:04.696 Attempting to install target: L-0960
09/27/2006 11:01:04.727 Attempting to install file: sqlncli.msi
09/27/2006 11:01:04.805 Attempting to install file: \\L-0960\c$\c13f3012d4415b5c63bc\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 11:01:04.868 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
09/27/2006 11:01:04.868 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 11:01:04.884 Failed to read registry key: Debug
09/27/2006 11:01:10.185 MSP returned 0: The action completed successfully.
09/27/2006 11:01:10.498 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
09/27/2006 11:01:10.545 Failed to read registry key: Debug
09/27/2006 11:01:10.576 Successfully installed file: \\L-0960\c$\c13f3012d4415b5c63bc\HotFixSqlncli\Files\sqlncli.msi
09/27/2006 11:01:10.608 Successfully installed target: L-0960
09/27/2006 11:01:10.608 Successfully installed instance: SQL Server Native Client
09/27/2006 11:01:10.623
09/27/2006 11:01:10.639 Product Status Summary:
09/27/2006 11:01:10.639 Product: SQL Server Native Client
09/27/2006 11:01:10.655 SQL Server Native Client (RTM ) - Success
09/27/2006 11:01:10.670
09/27/2006 11:01:10.686 Product: Setup Support Files
09/27/2006 11:01:10.686 Setup Support Files (RTM ) - Not Applied
09/27/2006 11:01:10.701
09/27/2006 11:01:10.717 Product: Database Services
09/27/2006 11:01:10.717 Database Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.733 Analysis Services (RTM 1399 ENU) - Not Applied
09/27/2006 11:01:10.748 Reporting Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.764
09/27/2006 11:01:10.764 Product: Notification Services
09/27/2006 11:01:10.780 Notification Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.795
09/27/2006 11:01:10.795 Product: Integration Services
09/27/2006 11:01:10.811 Integration Services (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.827
09/27/2006 11:01:10.842 Product: Client Components
09/27/2006 11:01:10.842 Client Components (SP1 2047 ENU) - Not Applied
09/27/2006 11:01:10.858
09/27/2006 11:01:10.873 Product: MSXML 6.0 Parser
09/27/2006 11:01:10.873 MSXML 6.0 Parser (RTM ) - Not Applied
09/27/2006 11:01:10.889
09/27/2006 11:01:10.905 Product: SQLXML4
09/27/2006 11:01:10.920 SQLXML4 (RTM ) - Not Applied
09/27/2006 11:01:10.920
09/27/2006 11:01:10.936 Product: Backward Compatibility
09/27/2006 11:01:10.952 Backward Compatibility (RTM ) - Not Applied
09/27/2006 11:01:10.952
09/27/2006 11:01:10.967 Product: Microsoft SQL Server VSS Writer
09/27/2006 11:01:10.983 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
09/27/2006 11:01:10.983
What doe all this mean? How do I fix the Business Intelligence Development Studio (BIDS) in its working with Analysis Services cubes?
|||
By the way the files noted earlier "msmgdsrv.dll" and "msmdlocal.dll" are still consistant in date betwee tne two folders.
Within BIDS I can make a connection to the database server. I know this because on the Browser tab of the cube I can drag different measures and dimensions onto the design surface and get results returned but I cannot view the cube's calculations. The design surface tells me;
"Unexpected error occurred: 'Error in the application.'"
At the bottom of the design window starts out with a message that says:
Unable to query the 'Adventure Works DW' cube: 'A connection cannot be made. Ensure that he server is running.'. The cube must be queried for you to browse data or meta data. Click here to retry the connection.
When I click the message at the bottom of the screen goes away, but the message on the design surface remains.
It appears that the needed connection for the calucations tabe is made because the Metadata tab, is populated with the proper measures and dimensions of the cube.
What is the cause of all this?
|||hello,
the symptoms of the error definitely suggest files got mismatched... so, if the 2 files are consistent between PrivateAssemblies and the Ole Db folder, then perhaps the 2 files are inconsistent between themselves in both places. what are the file versions/modification dates on msmgdsrv.dll and msmdlocal.dll (in both places) ?
i'm not sure why setup fails for you...
thanks,
|||> what are the file versions/modification dates on msmgdsrv.dll and msmdlocal.dll (in both places) ?
Here are the locations, filenames, versions, and date\time
C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\
Filename: msmgdsrv.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM
Filename: msmdlocal.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\
Filename: msmgdsrv.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM
Filename: msmdlocal.dll, Version: 9.0.2047.0, Date: 4/14/2006 9:55 AM
Before the complete Re-load of SQLS2k5 I had updated to the most recent hotfix (9.0.2153.0). At that time these files were also consistent in version and date and the same problem I now experience was there.
|||hello,
actually, as i mentioned before, it's important to check the versions compared to: %ProgramFiles%\Common Files\System\Ole DB\ (and not %ProgramFiles%\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\). i.e. can you please check the files in that (Ole Db) directory?
thanks,
|||
Here it is:
C:\Program Files\Common Files\System\Ole DB\
Filename: msmgdsrv.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM
Filename: msmdlocal.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM
So what action do I take? Do I rename the existing (older) files (to something like msmgdsrv.dll.old and msmdlocal.dll.old) and copy the above files into both following locations?
C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\
Then when install any new hotfixes (such as 2153) do make sure I review these three folders again with the newest of all files?
Thank you.
|||hello,
here is what i would try:
- save out old files that you will replace (possibly rename just as you suggested), so that you can get back to original state if needed.
- copy both dlls from C:\Program Files\Common Files\System\Ole DB\ to the other folders (PrivateAssemblies, IDE)
start new BIDS and see if this helped solve the issue with the tab.
as of now, if you see an issue like this, it would usually mean files got mismatched and to fix this you'd need to make sure they are all consistent again. i guess, you could also proactivelly monitor the versions and update if needed. just be careful, and make sure you can get to the previous good state if something.
hope this helps,
|||
Hello,
Not resolved - Crashes Now.
1.) I have mad the recommended changes, reviewed and confirmed the file changes I made;
In all of these locations;
C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\
C:\Program Files\Common Files\System\Ole DB\
I have these files;
Filename: msmgdsrv.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM
Filename: msmdlocal.dll, Version: 9.0.3009.0, Date: 8/16/2006 10:36 AM
2.) I created a new project, and deployed it. Then to test it I went to the calculations page.
Now what I encounter are crashes! I receive an error that says;
========================
Microsoft Visual Studio
========================
Microsoft Visual Studio has encountered a problem and needs to close.
--
If you had files open....
[x] Restart Microsoft Visual Studio
Send an error report to Microsoft
A report has been created that includes more information about the cause of this error. Submitting this report helps Microsoft improve Visual Studio.
What information is contained in this report?
========================
[Debug] [Send Error Report]
========================
3.) I have tried many times and encoutered the crashes repeatedly. This includes restarting Windows.
What is my next step?
|||Hi,I have the same problem on 1 machine. A fresh install of SQL 2005 SP1 (no hotfixes). and Office 2007 Beta 2 TR. I don't know, mayby this has something to do with Office?
Frederik|||
I have the same exact problem, and SQL 2005 SP1 & Office 2007 Beta TR. I didnt have this problem with office 2007 Beta.
Also I tried updating the dll's as advised in the two locations and visual studio crashes when I go to calculations tab, so I have rolled back to the old versions, but this comes with the error message on calculations tab and wont let me create any new calcs on a exisiting or any new cubes. It loads the existing calcs when I refresh the cube data, but just wont let me see it or edit it in design.
Any advise on how to fix this might help ?
|||Yes, my system too has has Office 2007 Beta 2 TR installed. Is there a pattern here?
|||Seems like it because it worked perfectly fine before I refreshed it with Office 2007 TR, that must have upgraded the dll's on the oledb folder to the 3009 release making it out of sync with the dll's on the tools / SQL Server.|||I wonder if it will help, if Office 2007 Beta TR is uninstalled and Office 2007 beta is installed again.....(No TR) since it was working before?
No comments:
Post a Comment