InvalidCastException with DI Company Object - SBO 2007 SP1 PL05

Hi, after updating to SBO 2007 SP1 PL05 i cannot start the AddOn, when it comes to the single Sign-On, i get the error message "InvalidCastException".
The code is as follows:
oCompany = new SAPbobsCOM.Company();
oCompany = (SAPbobsCOM.Company) SBO_Application.Company.GetDICompany();
Does anybody know the problem?

Solved, after re-reinstalling DI API!

Similar Messages

Document line with price zero in SBO 2007 A

Hi All
We have a DI API AddOn that occationally has to create a document line with the total price of zero.
In SBO 2005 A we just set SBODocument.Lines.Price = 0, but that doesn't work in SBO 2007 A.
In 2007A when we set SBODocument.Lines.Price = 0 it takes the price from the pricelist as though we had not entered a price at all. If we set SBODocument.Lines.Price to something else that zero it does correctly take the price we entered.
We have tried to set SBODocument.Lines.UnitPrice or SBODocument.Lines.LineTotal to zero in stead but it gives the same result.
Any help appriciated.
Rgds
Jesper Carstensen

Sorry, my mistake.
The solution WAS indeed to set SBODocument.Lines.UnitPrice = 0
Rgds
Jesper Carstensen

Can I bring up a SBO 2007 PL15 company in SBO 2007 PL 5 client?

Hi,
I am on SBO 2007 PL 15. If I backup my company database and send it to my client who is on PL05 of SBO 2007, will he be able to open this company.
I am no sure if my client wants to upgrade to PL 15. So, in case if he does not want to do an upgrade of his server, what is the alternate way?
Any help on this appreciated. Please reply ASAP.
Best regards,
Sudha

Hello Sudha,
I believe he would need PL15 to open the database as it is already upgraded. It might prompt them to upgrade.
The option if they do not want to Upgrade would be to send the DB at Patch level 5
Suda

Client OS - MS Windows XP Professional SP2 with SBO 2007 B

Dear All,
Is there any compatibility issue with the client OS - MS Windows XP Professional SP2 with SBO 2007 B?

Hi Narottam,
Yes, I did face problem with it. Once we upgrade XP with SP3 it works fine now.
Hope this help.
BR
Samir Gandhi

User name & password to log on SBO Integration that comes with SBO 2007

Hi
I have installed the SBO 2007 Demo product. It istall the the b1i. I'm trying to log onto the Control Center. A web page comes up with fields to add user name and password. In the older version it was B1iadmin, but it doesn't do anything after typing it. Doesn't go in or say incorrect password.
Any assistnace greatly appreciated

Hi Louis,
I made the same mistake. In some part of a guide (don't have any document right now) says the user and password are the same of the database user.
HTH,
Ian

What is the diff between SAP Netweaver B1i and B1i that comes with SBO 2007

Hi
There is SAP Netweaver B1i which is used for integration with SAP R3. But when you get SBO 2007 it also comes with B1i. Is there a difference or is it the same tool??
Thank you for your time.

Louis,
B1i on the SAP Business One 2007A Preview release is the same as B1i 2005A as far as what it is and how it works with relation to integrating SAP Business One and R/3. There are new features that are part of B1i 2007A of course that are not in 2005A such as integration with SAP BW, an updated Control Center as well as some other features such as the installation and upgrade routines. You should have a look at the documentation in the ..\Documentation folder and specifically in the "Integration" and "PEP" folders on the preview media. This is also, as mentioned, the PREVIEW version, so there will be updates to it forth coming before general release.
HTH,
Eddy

Crypt acquire context failed with 0x8009000f after upgrade from sms 2003 to SCCM 2007 SP1

I've upgraded clients from SMS 2003 SP3 to SCCM 2007 SP1.
In the SCCM console some ressources are showing as not being client.
If I look on the machine, I can see that client is installed but the client cannot communicate with the management point.
CCMEXEC.log shows the following error message :
Crypt acquire context failed with 0x8009000f.
Failed to create certificate 8009000f CcmExec 21/04/2009 9:49:10 1948 (0x079C)
CCMDoCertificateMaintenance() failed (0x8009000f).
So, the issue is related to certificate
If I go to C:\documents and settings\all users\Application Data\Microsoft\Crypto\RSA\MachineKeys and delete the file begining by 19c5cf... and then restart the client the problem is solved.
Can someone explain what is happening ?
What can I do to prevent this problem
Kind regards

In Server 2008 R2 SP1 (when Pushing Out SCCM 2012 clients)
I just added another account to the security (local Administrators) for the key which starts with 19c5cf...
and restarted the SMS AGENT HOST SERVICE.
Thats also resolved the problem. (NETWORK was the only security account on the key file).

Excel-Import with SBO 2007

Hello to all!
I have problems concerning the Excel-Import-function within SAP 2007.
I want to import some business partners (what should not be such a huge problem), but an internal error occures which states:
"internal error: Payment Methods for Payment Wizard (OPYM) (-2007) occured.
After I set up the Payment Wizard it is still not working - now the internal error stats: "(-2007)".
Experimentally, I tried to import the bp-data into an older version SAP BO 2005 - as personally expected no internal errors occured! even if i do not set up the Payment Wizard...
Here are some facts to our sbo 2007 version:
2007A (8.00.178)
SP: 00
PL: 44
I tried to find a thread upon this topic, but I could not find any. Maybe some of you might be able to help me! I am looking forward to it,
thanks a lot
daniel

Hi Daniel,
i had have similar problems by importing datas via excel function. My suggestion is to import step by step.
Select a few records and separate it into an extra excel sheet...(5-10 Records)
First try to import only CardCode, CardName, second try 2 records more. So you will find the records, that makes some trouble.
Regards Steffen
(P.S. I think it could be the g/l account definition, but i am not sure.)

Error -111 Conecting Database (SBO 2007)

Hi gurus.
I'm developing an addon with SBO 2007 and I create another company object for referencing different Database
I conect this one like:
oCompany2.Server = oCompany.Server
oCompany2.LicenseServer = oCompany.Server & ":30000"
oCompany2.CompanyDB = mMatriz.Columns.Item("c_bbdd").Cells.Item(i).Specific.string
oCompany2.UserName = lUsuario
oCompany2.Password = lPassword
oCompany2.UseTrusted = True
oCompany2.Connect
Obtaining error code -111: Failed to Connect to SBOCommon
User, password and LicenseServer are ok.
Any ideas?
Thnx in advance!

DbUser and DbPassword are required

Exchange 2003 sp2 to exchange 2007 sp1 upgrade error

Hi,
We had Windows 2003 DCs and Exchange 2003 servers. We migrated AD DCs to windows 2008 R2 at parent domain.
We have one parent domain and 10 child domains in remote sites .3 remote sites have been migrated to windows 2008 R2.
Now at parent domain I am trying to install exchange 2007 SP1 on a server with windows 2008 R2 SP1. I am facing certain issues:
1. When I run setup /PrepareSchema on this new exchange server , the organization check fails with error stating that : cannot find at least one DC running windows 2003 SP1 or later in DC=xyx,DC=com. This could be the result of moving DC objects in AD. Check
that at least one DC running windows server 2003 SP1 or later is located in the "Domian Controllers" OU and rerun setup".
2. When I try to install exchange server 2007 , I get the following error
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported
by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
Can any one shed light on this issue.
Regards
Syed
sa

You cannot install Exchange 2007 SP1 on Windows 2008 R2 SP1 as it is unsupported.
Only version of Exchange 2007 supported when OS is Windows 2008 R2 or R2 SP1 is Exchange 2007 SP3.
Where are you installing Exchange ? child or parent domain ?
2. When I try to install exchange server 2007 , I get the following error "Object
cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
Above error indicates that Exchange setup is trying to modify
a version of an object which might have been created when organization is prepared for Exchange 2010. don't you have exchange 2010 Servers already in your environment ?
Please give more information about your current email infrastructure
and whether if you are installing exchange on parent or child domain?
Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

Upgrade Exchange 2007 sp1 to sp3

Good day,
I have 3 exchange 2007 sp1 servers in my domain in different subnets. I need to upgrade all of them to sp3. i started with one branch server that is not in the same site with the domain schema master and im getting errors during instalation preparations
that - "    Organization Checks              ......................... FAILED
     Setup needs to contact the Active Directory schema master but this computer
is not in the same Active Directory site as the schema master (Default-First-Si
te-Name).
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
    Hub Transport Role Checks        ......................... FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
    Client Access Role Checks        ......................... FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
    Mailbox Role Checks              ......................... FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
My question is do i need to first upgrade the one in the same site with the scema master? and what will happen to the other remote server in different subnets?? how will i upgrade them given these errors?
Regards,
Brian

Good day,
I have 3 exchange 2007 sp1 servers in my domain in different subnets. I need to upgrade all of them to sp3. i started with one branch server that is not in the same site with the domain schema master and im getting errors during instalation preparations
that - "    Organization Checks              ......................... FAILED
     Setup needs to contact the Active Directory schema master but this computer
is not in the same Active Directory site as the schema master (Default-First-Si
te-Name).
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
    Hub Transport Role Checks        ......................... FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
    Client Access Role Checks        ......................... FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
    Mailbox Role Checks              ......................... FAILED
     Setup encountered a problem while validating the state of Active Directory:
Exchange organization-level objects have not been created, and setup cannot cre
ate them because the local computer is not in the same domain and site as the sc
hema master. Run setup with the /prepareAD parameter on a computer in the domai
n toyota and site Default-First-Site-Name, and wait for replication to complete.
My question is do i need to first upgrade the one in the same site with the scema master? and what will happen to the other remote server in different subnets?? how will i upgrade them given these errors?
Regards,
Brian
Prepare the domains as required. You have to prep the forest first for SP3 before upgrading Exchange itself
Follow all the instructions
http://technet.microsoft.com/en-us/library/bb125224(v=exchg.141).aspx
Prepare Active Directory and Domains
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

BPA shows domain prepped for Exchange 2007 SP1 after SP3 install

Hello,
I have a Client with a domain that is at 2003 domain functional level and 2000 forest level.
The client had Exchange 2007 SP1 and I have just upgraded it to SP3. There is one CAS, one Hub Transport, and one Mailbox Server (All three had Exchange 2007 SP1).
The domain and forest were prepped earlier by someone else and when I ran the installation program, it didn't pop up any errors on any of the servers.
The upgrade to SP3 is in preperation to Exchange 2010. Everything is working ok. I have checked:
1) In ADSIEdit, Exchange System Objects properties: Object Version =11221.
2) In ADSIEdit, Services>Microsoft Exchange>Organization: Object Version =11222
3) In ADSIEdit, RangeUpper value of ms-Exch-Schema-Version-Pt object = 14625
However, When I run the Exchange BPA, it reports that the domain is prepped for Exchange Server 2007 Service Pack 1 (In informational items). This is an informational item and not a warning or alert. However, I am concerned. Is this normal, and will it affect
the migration to Exchange 2010?
Thanks,
HA

Hello Ha20,
Based on my experience, it will not affect the migration. However, it’s recommended to prepare the schema again to avoid any potential issues.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Too many fields in SBO 2007.

Hi friends,
I got an error at the moment to update or delete any account numbers in the areas of "Type of Account" from the G/L Account Determination, in a new company that I'm configuring in SBO 2007. The error says "too many fields" and I'm worried that error appears later in the production DB on my customer .
Thanks.
Daniel

Hi Marcia,
Just the error saying "too many fields", and I really want to get out the account or change it for other one. In 2005 i don't have any problem with that. In the other hand, the DB is new.
Thanks.
Daniel

SBO 2007 PL06 - GetCompanyList fails

Folks,
I am not able to get the list of companies on SBO 2007. The following code fails with "Failed to connect to SBOCommon" error.
try {
   SAPbobsCOM.Company c = new SAPbobsCOM.Company();
   c.Server = "Test17";
   c.DbServerType = SAPbobsCOM.BoDataServerTypes.dst_MSSQL2005;
   c.UseTrusted = "true";
   SAPbobsCOM.Recordset cl = c.GetCompanyList();
} catch (Exception e) {
   Console.WriteLine(e.Message);
Note that all other APIs work just fine. I am able to open connection to specific company and perform any programmatic operation. It is just that GetCompanyList fails.
I am running this code on the machine where SBO server is installed. So there are no network issues.
I have tried setting the server to "local," "(local)", "localhost", etc. Still no success.
I also tried setting UseTrusted to false and specified DbUsername and DbPassword. Still no success. As far as I know, GetCompanyList always uses trusted connection and ignores usrename/password fields.
Does anyone know what the problem could be?
Thank you in advance for your help.
Regards,
Pradeep

Hi
pls try this code,
oCompany = New SAPbobsCOM.Company
            If cmbServertype.Text = "SQL SERVER 2005" Then
                oCompany.DbServerType = SAPbobsCOM.BoDataServerTypes.dst_MSSQL2005
            Else
                oCompany.DbServerType = SAPbobsCOM.BoDataServerTypes.dst_MSSQL
            End If
            oCompany.Server = "Test"
            oCompany.language = SAPbobsCOM.BoSuppLangs.ln_English
            oCompany.DbUserName = "sa"
            oCompany.DbPassword = "SQL"
             oRecordSet = Me.oCompany.GetCompanyList()
            Me.oCompany.GetLastError(lErrCode, sErrMsg)
            If lErrCode <> 0 Then
                MsgBox(sErrMsg)
                Exit Sub
            Else
Msgbox("Connection Success")
endif
Regards
Senthil Kumar

CurrentPeriod property in SBO 2007

Hi all,
I tried to use the oSBOApplication.Company.CurrentPeriod() (I'm almost sure it was like it), but the result is always -1. I wrote a message to the support center and they tell me that this is a SBO 2007 behavior by definition, not a bug. Before I pull the trigger (just kidding), does someone have any logical explanation why this great new feature is like this? If not, at least how can I get the current period through UI API?
Thanks in advance,
Ian

Hi Owen,
Actually it's an addon UI/DI, so if there's a way in DI or I can look it just with SQL there'll be no problem at all. But there's no way to do that, because the current period just can be done with UI as there's no entry in the DB that tells the current period in which the current user is. I read a lot of threads about it, and I remember everyone was excited when this featured appeared.
Weird enough the formatted search $[Period] works!!! Of course I WON'T use a formatted search for an add-on. So if it's not a bug what else can it be? What about backwards compatibility? Changing behavior without even tell the partners about it? Sigh
SBO SDK Help Center 2007: <i>CurrentPeriod. The DI API Company Service can get and set posting periods in the application. However, you cannot get or set the current period (the default period in the Company database) via this service.
This property complements the DI API Company Service and allows you to get the current period from the application. To get all the properties of the current period, use the GetPeriod or Periods functions of the Company Service.</i>
Well Owen, if you (or anyone) find any solution or workaround please let me know.
Thanks,
Ian
PS. Owen, I think with this points you're now leading the Top Users in SBO. Congrats! You worked really hard on it!

InvalidCastException with DI Company Object - SBO 2007 SP1 PL05

Similar Messages

Maybe you are looking for