Search This Blog

We cannot locate a server to load the workbook data model

We cannot locate a server to load the workbook data model

Issue-The Error was coming in SharePoint 2013 site when refreshing or clicking on any slicer of  the Power table Report in excel 2013 workbook.

Issue Cause-This issue occurs because the Analysis Services instance has not been configured in the Central Administration site.

Issue Solutions-Restart your SQL Server Analysis Server (PowerPivot) and Reset the IIS.


In most of the case above will fix your above Issue.

If in case the above method will not fix the Issue then configure the Excel Services service application on the SharePoint server. To do this, follow these steps:

1.       In the Application Management  section of the Central Administration home page, click Manage service applications.
2.       On the Manage Service Applications page, click the Excel Services service application that you want to configure.
3.       On the Manage Excel Services page, click Data Model.
4.       Click Add Server.
5.       In the Server Name box, type the name of the Analysis Services instance that you want to add.
6.       Click OK.


Unable to open the physical file in SQL

                Unable to open the physical file in SQL

Issue-Issue in SQL while Attaching MDF File or Restoring Backup file from some location.

Error1
Msg 5120, Level 16, State 101, Line 1
Unable to open the physical file "C:\ DB \AdventureWorksDW2012_Data (1).mdf". Operating system error 2: "2(The system cannot find the file specified.)".

Error 2
Msg 5120, Level 16, State 101, Line 1
Unable to open the physical file "C:\ DB \AdventureWorksDW2012_Data.mdf". Operating system error 32: "32(failed to retrieve text for this error. Reason: 15105)".


Issue Description-While attaching the Database  mdf file in sql server we were getting these above errors.

--Attaching MDF File without ldf file
CREATE DATABASE AdventureWorksDW2012
ON (FILENAME = 'C:\DB\AdventureWorksDW2012_Data.mdf')
FOR ATTACH_REBUILD_LOG ;

Error

Msg 5120, Level 16, State 101, Line 1
Unable to open the physical file "C:\DB\AdventureWorksDW2012_Data (1).mdf". Operating system error 2: "2(The system cannot find the file specified.)".

Issue Solution

-Run SSMS as an Administrator
-Restart SQL Server

Now you will be able to attach the DB Successfully.

Run your query again 

--Attaching MDF File without ldf file
CREATE DATABASE AdventureWorksDW2012
ON (FILENAME = 'C:\DB\AdventureWorksDW2012_Data.mdf')
FOR ATTACH_REBUILD_LOg

Output.It will attach the mdf file and will create a new ldf (log file) in same location 
with the message below.

File activation failure. The physical file name "C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\AdventureWorksDW2012_log.ldf" may be incorrect.
New log file 'C:\DB\AdventureWorksDW2012_log.ldf' was created.

NOTE: If after Running SQL as Administrator and Restarting the sql server won’t work for you then check for permission in your folder where you have kept your mdf or back file then go to “Sharing and Security of that folder and Allow-Full control.

T-SQL Script to perform DML Operations (Select, Insert, Update and Delete) based on DB Name

T-SQL script that will Perform DML Operations (Select, Insert, Update and Delete) based on DB Name


Requirement-We were working with Different customers DB where different customers were having Different DB Names but the table name and Structure of Tables were same.

So our requirement was through same web application we need to perform DML Operations (Select, Insert, Update and Delete) based on DB Name passed from front end (i.e. web application).
For Eg

DB-Customer-X
Tables-Employee, Products, Product_Description, Customers……….

DB-Customer-Y
Tables-Employee, Products, Product_Description, Customers……….

DB-Customer-Z
Tables-Employee, Products, Product_Description, Customers……….

So below I created a Stored Procedure Script that used to perform DML in different db based on DB Name passed from Front end

So Below is the Script with two test DB and one Employee Table

--Creating two test DB
Create database Test1
Create Database Test2

--Run Table Script in both the Database
CREATE TABLE [dbo].[Employee1](
     [Empid] [int] IDENTITY(1,1) NOT NULL,
     [EmpName] [nvarchar](50) NULL,
     [EmpSalary] [float] NULL,
 CONSTRAINT [PK_Employee1] PRIMARY KEY CLUSTERED
(
     [Empid] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]

GO

Stored Procedure Script that will will Perform DML Operations (Select, Insert, Update and Delete) based on DB Name Passed.

 --Script Code
--Run this Procedure in DB with which your web application is connected
Create PROCEDURE [dbo].[proc_db_test]
 (
 --Passing DB Name
@dbname varchar(100)=null,
--For Passing Operation insert update delete select
@Operation varchar(100)=null,
--Passing table values
@EmpId int =null,
@EmpName nvarchar(200)=null,
@EmpSalary float=null
 )
 AS
 BEGIN
IF db_id(@dbname) IS NULL
 BEGIN
RAISERROR ('Database %s does not exists!', 16,1, @dbname)
RETURN
END

if @Operation='INSERT'
begin

  EXEC('INSERT INTO '+@dbname+' .dbo.Employee1(EmpName,EmpSalary)
        VALUES('''+@EmpName+''','''+@EmpSalary+''')')

END
else if @Operation='UPDATE'
begin
 exec('update ' +@dbname+'.dbo. Employee1
set EmpName= '''+@EmpName+'''
,EmpSalary= '''+@EmpSalary+''' where EmpId='''+@EmpId+'''')
END
else if  @Operation='DELETE' 
begin
exec('Delete  from  ' +@dbname+'.dbo.Employee1  where EmpId='''+@EmpId+'''')
end
else  if @Operation='SELECTDETAILS'
begin
exec('select * from   ' +@dbname+'.dbo.Employee1  where EmpId='''+@EmpId+'''')
end
else if @Operation='SELECTALL'
begin
exec('select * from ' +@dbname+'.dbo.Employee1 order by Empid')
end
End


Test the Script

Insert Operation in both DB
--Procedure will have following inputs
--Proj_DB_Test DBName OPeration,EmpID,EMPName,EmpSalary

Exec  [dbo].[proc_db_test] 'Test1','Insert',1,'RK','15000'

--Test1 DB Test
Select * from test1.dbo.Employee1

Output
Empid  EmpName       EmpSalary
1          RK        15000

--Procedure will have following inputs
--Proj_DB_Test DBName OPeration,EmpID,EMPName,EmpSalary

Exec  [dbo].[proc_db_test] 'Test2','Insert',1,'RK1','20000'

--Test2 DB Test
Select * from test2.dbo.Employee1


Output
Empid EmpName    EmpSalary
1    RK1  20000


Test Update Operation in both DB

--Updating Name in Test1 DB
Exec  [dbo].[proc_db_test] 'Test1','UPdate',1,'RK_new','15000'

Output
Empid EmpName    EmpSalary
1    RK_new     15000



Test Delete Operation in both DB
--For Testing Delete Operation we will insert one more record in any of DB

--Insert
Exec  [dbo].[proc_db_test] 'Test1','Insert',2,'RK_1','10000'

Output

Empid EmpName    EmpSalary
1    RK_new     15000
2    RK_1 10000

--Deleting above newely added Record
Exec  [dbo].[proc_db_test] 'Test1','Delete',2

Output

Empid EmpName    EmpSalary
1    RK_new     15000


Test Select Operations in both DB
--Test Specific Records of Both DB Employee Table by passing Employee ID

Exec  [dbo].[proc_db_test] 'Test1','SELECTDETAILS',2

Output

Empid EmpName    EmpSalary
1    RK_new     15000



Exec  [dbo].[proc_db_test] 'Test2','SELECTDETAILS',1

Output 
Empid EmpName    EmpSalary
1    RK1  20000

Test Select all Operation in both DB
--Test all Records of Both DB Employee Table

Exec  [dbo].[proc_db_test] 'Test1','SELECTALL'

Output

Empid EmpName    EmpSalary
1    RK_new     15000

Exec  [dbo].[proc_db_test] 'Test2','SELECTALL'

Output

Empid EmpName    EmpSalary
1    RK1  20000


Testing by Passing DB Name that doesn't exist in server-Will Raise the below error

Exec  [dbo].[proc_db_test] 'Test3','SELECTALL'

Msg 50000, Level 16, State 1, Procedure proc_db_test, Line 16
Database Test3 does not exists!

NOTE:The best use of this script when you have multiple customers having different Databases having same table Names and Same table Structure.