• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 785
  • Last Modified:

Error While Processing an Application in SAP BPC with SQL 2008 on backend

I am getting this error on two appsets when I try to reindex them.

Error message:: No accessible overloaded 'LogHandler.WriteLog' can be called without a narrowing conversion.

I know the main answer is the appset name needs be shortened, but i do not believe that is the problem in this case. I can run a full process without an issue and the appsets in question are only 3 characters in length. I get this error when I try to modify the application   SAP Error
0
Ottertail
Asked:
Ottertail
  • 4
  • 2
1 Solution
 
käµfm³d 👽Commented:
In the .NET world, a narrowing conversion means you are trying to stuff some data of one type into a similar type of a smaller size. For example, you may have declared a long, but then you try to force it to fit inside of an int. With a long being 64 bits, and an int begin 32 bits, you would lose the upper 32 bits of the long when you attempt to cast between the types. Could this not be the case here?
0
 
OttertailAuthor Commented:
That could be part of it, but what i dont understand is that I move the database and OLAP cube over from a server it work on and I still get the error. The Servers are identical except this one has SQL 2008 SP2 installed.
0
 
OttertailAuthor Commented:
I know this application uses .NET, where would I find the setting to change what you mentioned above?
0
Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

 
käµfm³d 👽Commented:
I believe you need to find the function call referenced in your screenshot:  LogHandler.WriteLog(). At some point, your parameter is too big for the function's defined list of parameters.
0
 
OttertailAuthor Commented:
not sure what went wrong, but I had to strip down the entire BPC install and start over... After that things were working correctly.
0
 
OttertailAuthor Commented:
Had to reinstall BPC to fix the issue.. it was not tied to .NET
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now