From: Michelle on 21 Dec 2006 10:27 Workaround: Use http://<servername>/reportserver for the server name in Management Studio. This bypasses WMI. Michelle "rob(a)robearl.com" wrote: > Michelle wrote: > > Hi, > > > > We have a user in the System Administrator and System User roles of 2005 > > SSRS. He is able to connect to the website (http://<servername>/Reports) and > > do whatever he needs to do. But, when he tries to connect to Reporting > > Services in Management Studio, he receives the following error: > > > > =================================== > > > > Cannot connect to <servername>. > > > > > > =================================== > > > > The machine could not be found (Microsoft.SqlServer.Management.UI.RSClient) > > > > ------------------------------ > > > > Program Location: > > > > > > > > at > > Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.ParseServerName(String serverName) > > > > at > > Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.CreateSqlOlapConnectionInfoBase(UIConnectionInfo ci) > > > > at > > Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci) > > > > at > > Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci) > > > > at > > Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server) > > > > at > > Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser() > > I added him to the Distributed COM Users group, in DCOM security I added him > > to the Default Launch and Activation Permissions (Local Launch, Remote > > Launch, Local Activation, Remote Activation), I gave him all permissions to > > the root namespace (and sub-namespaces) in wmi. After giving him these > > permissions, the error message changes slightly (no longer does he get 'the > > machine name cannot be found'): > > > > Program Location: > > > > > > > > at > > System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 > > errorCode, IntPtr errorInfo) > > > > at > > System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext() > > > > at > > Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.ParseServerName(String serverName) > > > > at > > Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.CreateSqlOlapConnectionInfoBase(UIConnectionInfo ci) > > > > at > > Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci) > > > > at > > Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci) > > > > at > > Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server) > > > > at > > Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser() > > > > If I add him to the local administrators group, he can connect using > > Management Studio. But, that is not what we want to do. And, in fact, we want > > to revoke any of these extra permissions that we have assigned in order to > > try to get this working. Does anyone know what permissions a person needs > > (likely in the OS) for connecting to Reporting Services in Management Studio? > > > > Thanks, > > > > Michelle > > Hi Michelle, > > I'm having a very similiar problem to yours and I was wondering if you > ever found a solution to your problem. I haven't found much about it > on the internet yet, but I'm going to continue my search today. I'll > let you know if I find anything. > > Thanks, > Rob > >
|
Pages: 1 Prev: Reporting services vs. Active Reports Next: Need help with the Reportviewer in .NET |