Fact tables are resulting in error message

hello experts;
I am trying to create a mock-up report in OBI Answers and somehow Im having a problem with metric columns. When I pick any metric column then I get the: *(No Results: The specified criteria didn’t result in any data)*
I have doubled checked the rpd; the schemas btn the dimension and fact tables looks ok to me. I have tried union with another subject area, I get the same error. Anyone with an idea why fact tables are not collaborating with dimension tables?
will appreciate your help

In case if you are not able to see the logs,
follow this
Saving SET VARIABLE LOGLEVEL=2,DISABLE_CACHE_HIT=1; in a report
Mark correct or helpful if it helps,
Regards,
Veeresh Rayan

Similar Messages

In which tables are batch input error messages logged?

does anybody know in which table are the batch input error messages logged?
I have to display the error messages which have occured during the transaction
I tried to find out, but i could see only the table BDCMSGCOLL, this table has only the Batch input message number and not the message itself?
does anybody know about the batch input error messages?

hi,
check the sample code below.
messtab is of type BDCMSGCOLL.
Call the transaction and then use T100 to get the message.
DATA: l_mstring(480).
call transaction using
REFRESH messtab.
CALL TRANSACTION tcode USING bdcdata
                   MODE   ctumode
                   UPDATE cupdate
                   MESSAGES INTO messtab.
l_subrc = sy-subrc.
SKIP.
LOOP AT messtab.
    SELECT SINGLE * FROM t100 WHERE sprsl = messtab-msgspra
                              AND   arbgb = messtab-msgid
                              AND   msgnr = messtab-msgnr.
    IF sy-subrc = 0.
      l_mstring = t100-text.
      IF l_mstring CS '&1'.
        REPLACE '&1' WITH messtab-msgv1 INTO l_mstring.
        REPLACE '&2' WITH messtab-msgv2 INTO l_mstring.
        REPLACE '&3' WITH messtab-msgv3 INTO l_mstring.
        REPLACE '&4' WITH messtab-msgv4 INTO l_mstring.
      ELSE.
        REPLACE '&' WITH messtab-msgv1 INTO l_mstring.
        REPLACE '&' WITH messtab-msgv2 INTO l_mstring.
        REPLACE '&' WITH messtab-msgv3 INTO l_mstring.
        REPLACE '&' WITH messtab-msgv4 INTO l_mstring.
      ENDIF.
      CONDENSE l_mstring.
      WRITE: /4 messtab-msgtyp, l_mstring(250).
    ELSE.
      WRITE: /4 messtab.
    ENDIF.
ENDLOOP.

"None of the fact tables are compatible with the query request " error

I've got a situation where I have two facts(Fact_1, Fact_2) and three dimensions(dim_1,dim_2,dim_3) in 1 subject area. I've got dimension hierarchies setup for all the dimension tables.
Dim_1 is one to many to Fact_1
Dim_2 is one to many to Fact_2
Dim_3 is one to many to both Fact_1 and Fact_2
I've set up the content levels for the LTS for the Facts so that they are the lowest grain for dimensions they join to and the grand total grain for dimensions they do not join to.
My rpd is consistent. When I run a report using an attribute from Dim_3 and Dim_1 or Dim_3 and Dim_2, the report comes back fine.
But if I try to run a report using all three Dim tables, I get an error and the message "None of the fact tables are compatible with the query request ".
First of all, is it possible to make a report using all three dimensions?
Second, what's the best way to trouble shoot this error? Why are none of the fact tables compatible? I thought as long as the aggregation levels were set to grand total for non-shared dimensions, Answers would be able to create the report properly.
Any advise would be greatly appreciated.
Thanks!
-Joe

OBIEE is looking for a fact that can link ALL the dimensions together. This is also known as the implicit fact ... you don't have a fact that can relate all the dimensions - you have 2 facts that together they can. Perhaps you need to great a single logical fact that has both LTS for your physical facts and try it that way.
Then you'd have Dim1, Dim 2, Dim3 all being able to join to Fact1 (which is made of physical facts 1 & 2).

Error: None of the fact tables are compatible with the query request

Hi experts,
I have one confirm dimension D1 and other two fact table F1 and F2 (F1 and F2 are connected to D1)
when i create a report from D1 and F1 the report is running fine. But pull the column from F2 also in this report i am getting the following error
None of the fact tables are compatible with the query request Code Combinations
please suggest on the same.
Regards,
S

Hi
i have done the content level setting in each of the table, D1,F1 and F2(LTS), now i am getting the following error..
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Gl Sets Of Books) does not contain mapping for [Code Combinations.Code Combinations.Affiliate, GL Balances.GL Balances.Currency Code, GL Balances.GL Balances.PTD_Balance, Gl Sets Of Books.Gl Sets Of Books .SoB Name]. (HY000)
Gl Balances : D1
Code Commbination: F1
Gl Sets Of Books : F2
I have checked the joins in physical and BMM layer..all are fine..

None of the fact tables are compatible error

Hi All,
I do see this error (none of the compatible fact table) after setting the content level aggregation on the dimension tables and the fact table. This error i get only when i try to pull the calculated item which is based on a attribute in the fact table. I have an attribute like year in the fact table i need to display like 'CY'||'2013' in a calculated logical column and when i pull this into answers i get this error -
1) joins are ok ; only one fact table and 3 dimension tables
2). content level on the fact table are specified at the detail level and also for the dimensions
any suggestions - thanks for your time

can anyone please provide some suggestions -
> i looked at the fact table LTS and specified the logical level for each dimension as the detail
> specified the LTS for each dimension table
> I have a column in my fact table which is calendar year and i want to have a derived column like rep_cal_year with 'CY'||cal_year - so when i pull this derived column in my answers i get the error - none of the fact tables are compatibile with the query;
what could be missign?

Fact-tables not resulting in any data

hello experts;
I am trying to create a mock-up report in OBI Answers and somehow Im having a problem with metric columns. When I pick any metric column then I get the: *(No Results: The specified criteria didn’t result in any data)*
But when I pick just the fact tables, I see the results. I have doubled checked the rpd; the schemas btn the dimension and fact tables looks ok to me. I have tried union with another subject area, I get the same error. Anyone with an idea why fact tables are not collaborating with dimension tables?
will appreciate your help

Hi,
Can you try to check the physical SQL generated by the reports? and see if that query is returning result in the DB or not.
I am sure this will help you to find the root cause.
Regards,
Kashi

Essbase answers - None of the fact tables are compatible with the query request "member"

Hi,
I have modelled an Essbase database into the repository.
If I pull the measure, period and year dimension in and filter on the year (member) and display the year (member) along with the period (alias) and measure it errors with =>
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14020] None of the fact tables are compatible with the query request Fiscal Year.Fiscal Year Code. (HY000)
However, all other things being equal if I change the year displayed to the alias then it works.
Anyone tell me why??
Is there a limitation that Essbase brings through that you cannot view what you filter on?
thanks,
Robert.

Hi
i have done the content level setting in each of the table, D1,F1 and F2(LTS), now i am getting the following error..
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Gl Sets Of Books) does not contain mapping for [Code Combinations.Code Combinations.Affiliate, GL Balances.GL Balances.Currency Code, GL Balances.GL Balances.PTD_Balance, Gl Sets Of Books.Gl Sets Of Books .SoB Name]. (HY000)
Gl Balances : D1
Code Commbination: F1
Gl Sets Of Books : F2
I have checked the joins in physical and BMM layer..all are fine..

Fact tables are compatible with the query request

Hi,
i am using 11g.In 10g working fine without any error.After migrate 10g into 11g below error will returning. What is the problem and How we will fix.Could you pls let me know.Thanks
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14020] None of the fact tables are compatible with the query request FACT_AGENT_TIME_STATISTICS.FKEY. (HY000)
SQL Issued: SELECT s_0, s_1, s_2, s_3, s_4, s_5, s_6, s_7, s_8, s_9, s_10 FROM ( SELECT 0 s_0, "Team Performance"."DIMENSION - LOCATION"."COUNTRY CODE" s_1, "Team Performance"."DIMENSION - TIME"."BUSINESS DATE" s_2, CASE WHEN "Team Performance"."DIMENSION - TEAM"."ROLE" ='TEAM LEADER' THEN 'Team Leader' ELSE "Team Performance"."DIMENSION - TEAM"."TEAM" END s_3, CASE WHEN '30 Mins Interval' ='15 Mins Interval' THEN "Team Performance"."DIMENSION - TIME"."15 Mins Interval" ELSE "Team Performance"."DIMENSION - TIME"."30 Mins Interval" END s_4, ((SUM("Team Performance"."FACT - AGENT CALL STATISTICS"."TIME - ACD CALL HANDLING"+"Team Performance"."FACT - AGENT CALL STATISTICS"."TIME - AFTER CALL WORK (ACW)")+SUM("Team Performance"."FACT - AGENT TIME STATISTICS"."AVAILABLE TIME"))/60)/(COUNT(DISTINCT "Team Performance"."FACT - AGENT TIME STATISTICS"."DATE ID")*"Team Performance"."FACT - AGENT TIME STATISTICS"."INTERVAL TYPE") s_5, (SUM("Team Performance"."FACT - AGENT TIME STATISTICS"."AUX3 - TRAINING"+"Team Performance"."FACT - AGENT TIME STATISTICS"."AUX4 - MEETING"+"Team Performance"."FACT - AGENT TIME STATISTICS"."AUX5 - PROJECT"+"Team Performance"."FACT - AGENT TIME STATISTICS"."AUX6 - COACHING")/60)/(COUNT(DISTINCT "Team Performance"."FACT - AGENT TIME STATISTICS"."DATE ID")*"Team Performance"."FACT - AGENT TIME STATISTICS"."INTERVAL TYPE") s_6, (SUM("Team Performance"."FACT - AGENT TIME STATISTICS"."STAFFED TIME")/60)/(COUNT(DISTINCT "Team Performance"."FACT - AGENT TIME STATISTICS"."DATE ID")*"Team Performance"."FACT - AGENT TIME STATISTICS"."INTERVAL TYPE") s_7, COUNT(DISTINCT "Team Performance"."FACT - AGENT TIME STATISTICS"."DATE ID")*"Team Performance"."FACT - AGENT TIME STATISTICS"."INTERVAL TYPE" s_8, MIN("Team Performance"."DIMENSION - TIME"."FULL DATE TIME") s_9, REPORT_AGGREGATE(((SUM("Team Performance"."FACT - AGENT CALL STATISTICS"."TIME - ACD CALL HANDLING"+"Team Performance"."FACT - AGENT CALL STATISTICS"."TIME - AFTER CALL WORK (ACW)")+SUM("Team Performance"."FACT - AGENT TIME STATISTICS"."AVAILABLE TIME"))/60)/(COUNT(DISTINCT "Team Performance"."FACT - AGENT TIME STATISTICS"."DATE ID")*"Team Performance"."FACT - AGENT TIME STATISTICS"."INTERVAL TYPE") BY CASE WHEN '30 Mins Interval' ='15 Mins Interval' THEN "Team Performance"."DIMENSION - TIME"."15 Mins Interval" ELSE "Team Performance"."DIMENSION - TIME"."30 Mins Interval" END, CASE WHEN "Team Performance"."DIMENSION - TEAM"."ROLE" ='TEAM LEADER' THEN 'Team Leader' ELSE "Team Performance"."DIMENSION - TEAM"."TEAM" END) s_10 FROM "Team Performance" WHERE (("DIMENSION - TIME"."BUSINESS DATE" BETWEEN timestamp '2012-11-23 00:00:00' AND timestamp '2012-11-23 00:00:00') AND ("DIMENSION - LOCATION"."COUNTRY CODE" = 'US') AND ("DIMENSION - LOCATION".DEPARTMENT = 'CSG')) ) djm FETCH FIRST 65001 ROWS ONLY

Back up your repository before following these steps:
1 Reduce the problem report to minimum number of columns required to generate the error. This will usually identify which dimension and which fact are incompatible.
2 Open the repository in the Administration tool and verify that the dimension and fact table join at the physical layer of the repository
3 Verify that there is a complex join between the dimension and the fact in the business layer.
4 Check the logical table sources for the fact table. At least one of them must have the Content tab set to a level in the hierarchy that represents the problem dimension. This is usually the detailed level.
5 Check the logical table source Content tab for the dimension table. Unless there is a valid reason, this should be set to blank.
6. Save any changes to the repository.

None of the fact tables are compatible

hi,
am developing report from two fact table columns and one dimension table in obiee 11.1.1.5.0.
am getting error
Error
View Display Error
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14020] None of the fact tables are compatible with the query request Fact - Retail.Retail. (HY000)
SQL Issued: SELECT 0 s_0, "TM Vehicle Sales"."- Offtake Facts"."Offtake" s_1, "TM Vehicle Sales"."- Retail Facts"."Retail" s_2, "TM Vehicle Sales"."Distributor"."Country" s_3 FROM "TM Vehicle Sales"
regards
vcm

need to see your design, dim is shared between the facts?
I think you can assume the physical query based on your columns selection..
Now pick one column from 1st fact and 2nd column from dim run a report, get physcial query and verify the joins with obiee and your own query.
then add column from 2nd query see how it works
Edited by: svee on Jun 29, 2012 6:21 AM

Content Tab: None of the fact tables are compatible with the query request

Hi All,
**One thing I am not clear yet of all my years with OBIEE is working with the content tab in BMM.**
I have made a rpd the joins in physical layer as shown below:
https://picasaweb.google.com/114804305606242416264/OBIEEError#5663056545119428530
And the BMM layer as:
https://picasaweb.google.com/114804305606242416264/OBIEEError#5663056519553812930
Error I am getting when i run a request from the 3 columns from the selected 3 tables is:
Dim - Comment Code Details
Fact - Complaint
Dim - Service Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14020] None of the fact tables are compatible with the query request Sr Num:[DAggr(Fact - Complaint.Sr Num by [ Dim - Service Details.Sr Cat Type Cd, Dim - Comment Code Details.Cmtcode name] )]. (HY000).
I get no error for consistency.. I read everywhere and I know i need to set the appropriate aggregation levels in the various dims and facts LTS properties to help OBIEE understanding our model, but how to do that.. how do i decide... how should I approach, what should be the aggregation level, what details.
When i click More button i see different options: Copy, Copy From, Get Levels, Check Level, what do these mean.
Aggregation Content, group by - Logical Level or Column which one should i choose and how should I decide.
Can anyone explain the Content Tab in details and from scratch with some example and why we get these errors.... I know many people who are well versed with many other things related to RPD but this. A little efforts of explaining from you guys will really be appreciated.
Thanks in advance,
Dev

Hi Deepak,
Option 1:
My tables in physical layer are joined as below:
D1--> F1 <--D2--> F2 <--D3
Same way i model it in BMM
D1--> F1 <-- D2--> F2 <--D3
Here D1 is non Conformed Dimension for F2 and D3 is non Conformed dim for F1. Later create Dimensional hierarchies, I tried setting up the content levels
I go Sources>content tab of Fact F1 I set
Dimensions----------- Logical level
D1---------------------- D1 Detail
D2---------------------- D2 Detail
D3---------------------- D3 Total
then, I go Sources>content tab of Fact F2 I set
Dimensions----------- Logical level
D1---------------------- D1 Total
D2---------------------- D2 Detail
D3---------------------- D3 Detail
Then, I also go in all the dimensions and set their content levels to Details, but it still gives me errors not sure where I am going wrong in setting the content levels.
I need to know whether the way I have modeled it in BMM is right,
Option 2:
I can combine the two facts in a single Logical Fact or the above design should also work.
(F1&F2)<--D1, D2 , D3 joined separately using complex logical joins.
what will be the content tab details?
Thanks,
Dev

When we post Inbound Invoice IDocs, we are getting an error message "Enter a tax jurisdiction code".

Hi Experts,
When we post Inbound Invoice IDocs, we are getting an error message "Enter a tax jurisdiction code". As checked, we have configured OBCD and OBCA for the vendor and we are passing the Tax Jurisdiction code in E1EDP04 SAL segment. Can anybody give us some idea to resolve this issue.
Regards,
Sameek

Hi Sameek,
Please refer the below link. Hope it helps.
http://scn.sap.com/thread/1435286
Regards,
Chandan.

Which Fact tables are part of OBIA Financial Analytics v796?

Does anyone know which fact tables (Star schemas) are associated with Financial Analytic license?
As of now, I am going thru the document: OracleBusinessAnalyticsWarehouseDMR_V796.pdf and i am trying to identify which Star Schema's are associated with the Financial Analytics and I was wondering if there was a more productive means of finding out this information.
thanks

Ir-respective of what Fact tables are used in Finacial Analytics, the Target DW will have these fact tables when used with EBS source. This is true even if you run ETL only for Financial analytics. This in general is true for EBS also, even though you may only Financial module of EBS, the data model of EBS will have most of the tables as often there are shared tables from other modules.
179 rows selected
TABLE_NAME
W_ABSENCE_EVENT_F
W_ACCT_BUDGET_F
W_ACD_EVENT_F
W_ACTIVITY_F
W_AGREEITEM_F
W_AGREE_F
W_APPL_ACC_SNP_F
W_APPL_EVENT_F
W_AP_BALANCE_F
W_AP_INV_DIST_F
W_AP_XACT_F
W_AR_BALANCE_F
W_AR_XACT_F
W_ASSESS_F
W_ASSET_F
W_BALHSTRY_F
W_BENEFIT_F
W_BOM_ITEM_F
W_CALL_ACCNT_F
W_CALL_ATTND_F
W_CALL_CON_F
W_CAMP_HIST_F
W_CAMP_OPTY_F
W_CASE_F
W_CASE_KPI_F
W_CASE_SNP_F
W_CASE_STG_F
W_CNTCT_CNTR_BNCHMRK_TGT_F
W_CNTCT_CNTR_PERF_F
W_CUSTOMER_COST_LINE_F
W_CUSTOMER_STATUS_HIST_F
W_DTL_FCST_F
W_EMPLOYEE_DAILY_SNP_F
W_EMPLOYEE_EVENT_F
W_EMPLOYEE_MONTHLY_SNP_F
W_EXPENSE_F
W_FN_HOLDING_F
W_FUND_F
W_GL_BALANCE_F
W_GL_COGS_F
W_GL_OTHER_F
W_GL_REVN_F
W_HOUSEHOLD_F
W_INCDNT_KPI_F
W_INCDNT_SNP_F
W_INCIDENT_F
W_INS_CLAIM_F
W_INVENTORY_DAILY_BAL_F
W_INVENTORY_MONTHLY_BAL_F
W_INVOICE_F
W_IVR_NAV_HIST_F
W_JOB_RQSTN_ACC_SNP_F
W_JOB_RQSTN_EVENT_F
W_KPI_F
W_LEAD_F
W_LEAD_KPI_F
W_LEAD_SNP_F
W_LM_ENROLLMENT_ACC_SNP_F
W_LM_ENROLLMENT_EVENT_F
W_LOY_ACCRUAL_ITEM_F
W_LOY_ACTIVITY_F
W_LOY_COST_F
W_LOY_MEMBER_MARKETING_F
W_LOY_MEMBER_STATUS_HIST_F
W_LOY_MEMBER_TIER_HIST_F
W_LOY_PARTNER_POINT_BLOCK_F
W_LOY_PROMOTION_ENROLLEE_F
W_LOY_PROMOTION_MEMBER_F
W_LOY_PROMOTION_PRODUCT_F
W_LOY_REDEMPTION_ITEM_F
W_LOY_REVENUE_F
W_LOY_STATEMENT_F
W_MED_ED_F
W_MKTG_COST_F
W_MKTG_GOAL_F
W_MKTG_LEAD_F
W_OBJECTIVE_F
W_OFR_PROD_F
W_OPTY_CMPT_F
W_OPTY_CON_F
W_OPTY_STG_F
W_ORDERITEM_F
W_ORDER_F
W_ORDIT_WTR_LOG_F
W_PAYROLL_F
W_PERFORMANCE_F
W_PERSON_F
W_PER_RANK_F
W_PIPELINE_F
W_PRODUCT_COST_LINE_F
W_PRODUCT_XACT_F
W_PROJ_BUDGET_F
W_PROJ_COST_LINE_F
W_PROJ_EXP_LINE_F
W_PROJ_FORECAST_F
W_PROJ_FUNDING_HDR_F
W_PROJ_FUNDING_LINE_F
W_PROJ_INVOICE_LINE_F
W_PROJ_RETENTION_F
W_PROJ_REVENUE_HDR_F
W_PROJ_REVENUE_LINE_F
W_PROMOTION_F
W_PURCH_COST_F
W_PURCH_CYCLE_LINE_F
W_PURCH_ORDER_F
W_PURCH_RCPT_F
W_PURCH_RQSTN_LINE_F
W_PURCH_RQSTN_STATUS_F
W_PURCH_SCHEDULE_LINE_F
W_QTEIT_WTR_LOG_F
W_QUOTEITEM_F
W_QUOTE_F
W_RCRTMNT_EVENT_F
W_REP_ACTIVITY_F
W_RESPONSE_F
W_RESP_PROD_F
W_REVN_F
W_RQSTN_LINE_COST_F
W_RTLAUDIT_F
W_SALES_BACKLOG_HISTORY_F
W_SALES_BACKLOG_LINE_F
W_SALES_BOOKING_LINE_F
W_SALES_CYCLE_LINE_F
W_SALES_INVOICE_LINE_F
W_SALES_ORDER_LINE_F
W_SALES_PICK_LINE_F
W_SALES_SCHEDULE_LINE_F
W_SRVREQ_F
W_SUM_FCST_F
W_SURVEY_F
W_SYNDD_DS_F
W_SYNDD_IDS_F
W_SYNDD_PT_F
W_SYNDD_RX_F
W_SYNDD_W_F
W_SYNDD_XPT_F
W_SYNDM_DS_F
W_SYNDM_IDS_F
W_SYNDM_PT_F
W_SYNDM_RX_F
W_SYNDM_W_F
W_SYNDM_XPT_F
W_SYND_DS_T_F
W_SYND_IDS_D_F
W_SYND_IDS_T_F
W_SYND_PT_T_F
W_SYND_RX_T_F
W_SYND_W_T_F
W_SYND_XPT_D_F
W_SYND_XPT_T_F
W_SYNM_DS_T_F
W_SYNM_IDS_D_F
W_SYNM_IDS_T_F
W_SYNM_PT_T_F
W_SYNM_RX_T_F
W_SYNM_W_T_F
W_SYNM_XPT_D_F
W_SYNM_XPT_T_F
W_UA_ACCAPLN_F
W_UA_ACCSUM_F
W_UA_ACCUSG_F
W_UA_ACTUSG_F
W_UA_ADOPT_F
W_UA_ASTAPLN_F
W_UA_ASTSUM_F
W_UA_ASTUSG_F
W_UA_CONAPLN_F
W_UA_CONSUM_F
W_UA_CONUSG_F
W_UA_OPTAPLN_F
W_UA_OPTYSUM_F
W_UA_OPTYUSG_F
W_UA_QOTUSG_F
W_VEHICLE_F
W_WRKFC_EVT_AGE_F
W_WRKFC_EVT_F
W_WRKFC_EVT_MERGE_F
W_WRKFC_EVT_MONTH_F
W_WRKFC_EVT_POW_F
Edited by: shyamvaran on Jul 22, 2009 2:55 PM

Thunderbird will not send emails...but claims they are "sent" (no error message)

Up until the beginning of this month my Thunderbird was working fine with my roadrunner email address. I have not downloaded any new software or made any changes to my settings during this time. Now I can no longer send emails (although it claims they are sent) and I never get an error message. I'm definitely in online mode, can receive all messages fine, and can send messages from my road runner server fine through webmail. I have checked to ensure no firewalls or antiviruses are blocking my outgoing messages and know the SMTP is correct. Please help!

Hi...thanks so much for your help! It says "mail sent successfully" and shows it in my sent folder after I click send.
Troubleshooting:
Application Basics
Name: Thunderbird
Version: 24.4.0
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
Profile Folder: Show Folder
(Local drive)
Application Build ID: 20140316131045
Enabled Plugins: about:plugins
Build Configuration: about:buildconfig
Crash Reports: about:crashes
Memory Use: about:memory
Mail and News Accounts
account1:
INCOMING: account1, , (pop3) pop-server.tampabay.rr.com:110, plain, passwordCleartext
OUTGOING: smtp-server.tampabay.rr.com:25, plain, none, true
account2:
INCOMING: account2, , (none) Local Folders, plain, passwordCleartext
Extensions
Important Modified Preferences
Name: Value
browser.cache.disk.capacity: 358400
browser.cache.disk.smart_size.first_run: false
browser.cache.disk.smart_size.use_old_max: false
browser.cache.disk.smart_size_cached_value: 358400
extensions.lastAppVersion: 24.4.0
font.internaluseonly.changed: true
font.name.monospace.el: Consolas
font.name.monospace.tr: Consolas
font.name.monospace.x-baltic: Consolas
font.name.monospace.x-central-euro: Consolas
font.name.monospace.x-cyrillic: Consolas
font.name.monospace.x-unicode: Consolas
font.name.monospace.x-western: Consolas
font.name.sans-serif.el: Calibri
font.name.sans-serif.tr: Calibri
font.name.sans-serif.x-baltic: Calibri
font.name.sans-serif.x-central-euro: Calibri
font.name.sans-serif.x-cyrillic: Calibri
font.name.sans-serif.x-unicode: Calibri
font.name.sans-serif.x-western: Calibri
font.name.serif.el: Cambria
font.name.serif.tr: Cambria
font.name.serif.x-baltic: Cambria
font.name.serif.x-central-euro: Cambria
font.name.serif.x-cyrillic: Cambria
font.name.serif.x-unicode: Cambria
font.name.serif.x-western: Cambria
font.size.fixed.el: 14
font.size.fixed.tr: 14
font.size.fixed.x-baltic: 14
font.size.fixed.x-central-euro: 14
font.size.fixed.x-cyrillic: 14
font.size.fixed.x-unicode: 14
font.size.fixed.x-western: 14
font.size.variable.el: 17
font.size.variable.tr: 17
font.size.variable.x-baltic: 17
font.size.variable.x-central-euro: 17
font.size.variable.x-cyrillic: 17
font.size.variable.x-unicode: 17
font.size.variable.x-western: 17
mail.openMessageBehavior.version: 1
mail.winsearch.enable: true
mail.winsearch.firstRunDone: true
mail.winsearch.global_reindex_time: 1386018562
mailnews.database.global.datastore.id: d0565083-6917-4a0a-868f-37bebde1e81
network.cookie.prefsMigrated: true
places.database.lastMaintenance: 1398260550
places.history.expiration.transient_current_max_pages: 104808
plugin.importedState: true
plugin.state.npdeployjava: 0
print.printer_Lexmark_X264dn.print_bgcolor: false
print.printer_Lexmark_X264dn.print_bgimages: false
print.printer_Lexmark_X264dn.print_colorspace:
print.printer_Lexmark_X264dn.print_command:
print.printer_Lexmark_X264dn.print_downloadfonts: false
print.printer_Lexmark_X264dn.print_duplex: -1574483314
print.printer_Lexmark_X264dn.print_edge_bottom: 0
print.printer_Lexmark_X264dn.print_edge_left: 0
print.printer_Lexmark_X264dn.print_edge_right: 0
print.printer_Lexmark_X264dn.print_edge_top: 0
print.printer_Lexmark_X264dn.print_evenpages: true
print.printer_Lexmark_X264dn.print_footercenter:
print.printer_Lexmark_X264dn.print_footerleft: &PT
print.printer_Lexmark_X264dn.print_footerright: &D
print.printer_Lexmark_X264dn.print_headercenter:
print.printer_Lexmark_X264dn.print_headerleft: &T
print.printer_Lexmark_X264dn.print_headerright: &U
print.printer_Lexmark_X264dn.print_in_color: true
print.printer_Lexmark_X264dn.print_margin_bottom: 0.5
print.printer_Lexmark_X264dn.print_margin_left: 0.5
print.printer_Lexmark_X264dn.print_margin_right: 0.5
print.printer_Lexmark_X264dn.print_margin_top: 0.5
print.printer_Lexmark_X264dn.print_oddpages: true
print.printer_Lexmark_X264dn.print_orientation: 0
print.printer_Lexmark_X264dn.print_page_delay: 50
print.printer_Lexmark_X264dn.print_paper_data: 1
print.printer_Lexmark_X264dn.print_paper_height: 11.00
print.printer_Lexmark_X264dn.print_paper_name:
print.printer_Lexmark_X264dn.print_paper_size_type: 0
print.printer_Lexmark_X264dn.print_paper_size_unit: 0
print.printer_Lexmark_X264dn.print_paper_width: 8.50
print.printer_Lexmark_X264dn.print_plex_name:
print.printer_Lexmark_X264dn.print_resolution: 0
print.printer_Lexmark_X264dn.print_resolution_name:
print.printer_Lexmark_X264dn.print_reversed: false
print.printer_Lexmark_X264dn.print_scaling: 1.00
print.printer_Lexmark_X264dn.print_shrink_to_fit: true
print.printer_Lexmark_X264dn.print_to_file: false
print.printer_Lexmark_X264dn.print_unwriteable_margin_bottom: 0
print.printer_Lexmark_X264dn.print_unwriteable_margin_left: 0
print.printer_Lexmark_X264dn.print_unwriteable_margin_right: 0
print.printer_Lexmark_X264dn.print_unwriteable_margin_top: 0
Graphics
Adapter Description: Intel(R) HD Graphics
Vendor ID: 0x8086
Device ID: 0x0152
Adapter RAM: Unknown
Adapter Drivers: igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32
Driver Version: 8.15.10.2639
Driver Date: 2-1-2012
Direct2D Enabled: false
DirectWrite Enabled: false (6.2.9200.16571)
ClearType Parameters: ClearType parameters not found
WebGL Renderer: false
GPU Accelerated Windows: 0
AzureCanvasBackend: skia
AzureFallbackCanvasBackend: cairo
AzureContentBackend: none
JavaScript
Incremental GC: 1
Accessibility
Activated: 0
Prevent Accessibility: 0
Library Versions
Expected minimum version
Version in use
NSPR
4.10.2
4.10.2
NSS
3.15.4 Basic ECC
3.15.4 Basic ECC
NSS Util
3.15.4
3.15.4
NSS SSL
3.15.4 Basic ECC
3.15.4 Basic ECC
NSS S/MIME
3.15.4 Basic ECC
3.15.4 Basic ECC

Cannot install itunes 10.6 to my windows 7 computer. Have tried several times, completely unistalled several times, all with same result. Error message that starts "An error occurred during the installation of assembly 'Microsoft VC80 CRT. type="win 32"

Keep getting the following error message when I try to instal itunes 10.6. An error occurred during the installation of assembly 'Microsoft VC80 CRT.type="win 32". version = "8.0 50727.61 95". public Key token = ""1fc8b3b9a1e18e3b." processor architeture = "x86". Please refer to help and support for more information.
HRESULT:0x80073712
The program then acts like it is still trying to load, but then I get another message later which reads:
Service 'Aple Mobile Device' failed to start. verify that you have sufficient privileges to start system services.
any suggestions?

HRESULT: 0x80073712
These ones are typically caused by underlying problems on the PC that also often cause Windows Updates to fail to install. If we can fix the Windows Update trouble, we can usually get the iTunes trouble cleaned up en passant.
Go into your Windows update and try to check for new updates. If updates install, stock up on the ones you're behind on, restarting the PC if requested to do so. After the restart, try installing iTunes again. Does it go through this time for you?
If windows updates fail to install, go into your Update History and doubleclick the failures. What alphanumeric codes appear for you? Are they also 80073712, or some other number? (If they're another number, what number are you getting?)

"Entitlements are not valid" error message when trying to sync ipa file from iTunes to iPad

Is anyone else getting this error message, "Entitlements are not valid", when trying to sync .ipa file from iTunes to iPad?
The issue I'm having is getting the ipa file that was built by the 'Adobe Flash Packager for Iphone' installed into my iPad.
So, I have a swf file that works and was able to publish it into the Android Market. I then compiled and build the same flash project with the Packager for Iphone into an .ipa file. But when I try and install this .ipa file into my iPad to do my testings, i'm getting the error message.
I would like to test my ipa file in my iPad device before submitting it to the Apple Store.
Any help would be appreciated. thank you.

Developing for iphone can be amazingly complicated and frustrating. (even before you start coding). The process of having to create a Certificate, to approving the Certificate, to Assigning the deviceIDs to the certificate, to creating the AppIDs, to creating the provisioning profiles and then creating the .p12 file... is just too tedious.
I solved the problem of the "Entitlements are not valid". The AppID i had set in the iPhone Developer Portal did not match that of the AppID i had set in the Adobe Flash CS5 -> Publish Settings. (ie. com.yourdomainname.yourappname). After I re-entered my AppID and compile, i was able to sync the .ipa file into my ipad.
I wish the error message had been a little more descriptive. Could have saved me a whole day.
I hope this helps others. But my guess is, if you don't set the 40 character device ID correctly, or the email in the signingcertificate correctly, you'll get this same generic error message.

Fact tables are resulting in error message

Similar Messages

Maybe you are looking for