MS EXCEL connectivity issue in OBIEE11.1.1.5 in online mode

Hi,
I am working on OBIEE 11.1.1.5, developing reports using excle data source. I am facing a issue connecting to EXCEL data source in online mode.
When I try view data, update row count in offline mode from RPD, it works.
I have created a ODBC with Excel data source, i have created a connection pool in RPD with ODBC, it works only in offline mode.
Please, let me know the workaround for working in online mode.
Regards,
Hemanth.

Hi,,
Refer the below link:
http://allaboutobiee.blogspot.com/2012/03/excel-as-data-source-in-obiee.html
Hope it helps

Similar Messages

Adobe Story going offline because of connection issues and now won't go into Online mode.

Adobe team. Need immediately to be able to go Online again.
Doug Morrow

When it restored it updated to firmware 4.0.2
Sounds like your phone was also locked back to the carrier it was originally locked to. That happens when you update software or restore an iphone that has been hacked to unlock it. Unfortunately for you, you won't be able to do anything with that phone until its first activated on the carrier's network(requires that carrier's sim) it was originally locked to. So yes, in a sense, you're SOL.

Webi XI report export to excel--- Formatting issue

Post Author: Sougata
CA Forum: WebIntelligence Reporting
We have WEBI report that contains cell with hyperlink. The value of the cell in numeric. Type is string.
When we export this report to excel. In, Excel version is MS-office Excel 2003. In excel it is showing those green with Error --- "NUMBER STORED AS Text".
Any solution?

Hi Steve,
As per my understanding, the issue occurs because Excel Destination gets the data from the source. We can change it, but once it re-validates it will change it back. This makes sense since we cannot change the data type in the actual table. To work around
this issue, I suggest that we can add a data conversion or derived column to explicitly cast the values.
Besides, the suggestion post by Arthur means that we can add IMEX=1 to the value of Extended Properties in the connection string of the Excel connection manager in the Properties window to specify Import Mode. For more details about the settings of IMEX,
please see:
https://support2.microsoft.com/kb/194124?wa=wsignin1.0
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Export to Excel formatting Issue

Good Afternoon,
I am trying to export a dataset to excel 2010, however all of the columns are exporting as DT_WSTR although the table that the data is coming from is set correctly either to money or int.
I have tried to change the data type in the advance editor for excel destination, however when I execute the package the data type changes back.
Any idea's?.
Thanks
Steve

Hi Steve,
As per my understanding, the issue occurs because Excel Destination gets the data from the source. We can change it, but once it re-validates it will change it back. This makes sense since we cannot change the data type in the actual table. To work around
this issue, I suggest that we can add a data conversion or derived column to explicitly cast the values.
Besides, the suggestion post by Arthur means that we can add IMEX=1 to the value of Extended Properties in the connection string of the Excel connection manager in the Properties window to specify Import Mode. For more details about the settings of IMEX,
please see:
https://support2.microsoft.com/kb/194124?wa=wsignin1.0
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Excel ODBC Connection Issues

I'm having some issues importing external data from an Oracle 9i database.
Here is what is happening:
I am initially able to import data from the table I want to into Excel.
I do this through "Data -> Import External Data -> New Database Query" where I have my .ORA data source. I'm able to log in using my user and password and import the table. My problems come after I import this first set of data.
If I try to "Edit Query…" I get an error box that says "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
If I try to "Refresh Data" I get two error boxes. The first is just: "[Microsoft][ODBC driver for Oracle][Oracle]" and the next says: "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed". It then prompts me for the User name and password of the DB I'm connecting and after I enter the information, I get the same two error messages.
Also, if I attempt to establish another connection following the "Data -> Import External Data…" steps I run into a different problem. Upon entering the information for the User Name and password prompt I get two error messages. One says "!" and the next box says "Couldn't read this file". Once I click "OK" in those boxes, the Microsoft Query window automatically opens with nothing in it.
I can't seem to figure out why I can initially pull down data and then cannot succeed afterwards. I'm unable to connect to the DB I have through Excel until I completely closed all Microsoft Excel instances.
I also use this data source in Microsoft Access without any problems.
My Excel version is 2003.
I'm using Oracle Drivers I'm using are from an "Instant Client" package.
Any thoughts why I'm having these connections issues?
Thanks in advance.

This issue is closed.
The solution was:
"Data -> Import External Data -> Import Data"
Select "New Source" and select the "Oracle" data source and filled in the appropriate information. This was similar to the database query but it actually works.

SSIS excel connection datatype issue

HI
Please find data below
ColA            ColB
74378             11213
312             21312
34                 234
7329             27924
23423             224353
42342             13243
54245             32321
25423             6483
5234             84379
dmf             934293
52                 9549
49                 439879
ads             asdf
asd             aesdf
asd             asdf
asd             asdf
asdf             asdf
sadf             asdf
asdf             sadf
Using excel connection to load data to SQL Server When I try doing this character data is loading as nulls, I have tried by putting IMEX=1 property in connection string and removing IMEX=1 property from connection string , in both cases it is showing nulls,
in the data viewer which i have placed after Excel source. I have also tried using the OPENROWSET which for some reason does not create an adhoc connection. I also tried changing the Datatypes in the advanced editor which again throws error. I tried all possible
ways of fixing this issue but no luck yet. Could you please help resolve this. For some reason SSIS excel connection reads only the first 8 rows and decides a datatype and rest showup NULL.

The problem with your data is that Excel is attempting to guess the data type of the columns. By default, the TypeGuessRows property is set to 8, which means it will sample the first eight rows. In your data, the first eight rows are all numbers,
so Excel interprets the entire column as numeric. When it encounters text, it decides it can't convert text to numbers, so it provides SSIS with a NULL.
IMEX has no effect in the above scenario (with the default TypeGuessRows value) because IMEX applies when Excel finds "mixed types" in the columns - and in your case (with eight rows) it does not.
TypeGuessRows can be modified (as Reza suggested) but only for values from 0 to 16. In your specific case, setting it to 16 would have an effect. Excel would read your file, see some numeric AND text values, and decide those columns have "mixed
types". NOW the IMEX attribute comes into play. If you DON'T specify IMEX=1, then Excel will choose a data type based on majority wins. In your specific case, it would still choose numeric for column A and column B, because most of the values
in the first 16 rows are numeric. If you specify IMEX=1, then Excel behaves differently. Instead of "majority wins", if multiple data types are detected, it ALWAYS picks text.
So - in your specific case, with this specific file, increasing TypeGuessRows to 13 or more, AND using IMEX=1 will allow you to read both columns as text, and not receive NULLs.
Talk to me now on

Excel Connection Manager suddenly can no longer connect to Excel from SSIS package

During the last 3 months, I used 32 bit SSIS 2008 (v 10.50.2500.0) on an WinXp machine (v 5.1.2600 SP3 Build 2600) to create a package that writes multiple query results (reports) to an excel spreadsheet. Each report is written to a different
tabbed sheet in the same spreadsheet. The package was working just fine until May 9 2013, when suddenly every single Data Flow task with an Excel Destination displayed error icons and raised the following
error message when opening the Advanced Editor:SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005 Description: "Unspecified error". Error at <DataFlow task name>: SSIS
error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager <Excel connection Manager> failed with error code 0xC0202009. There may be error messages posted before this with more
information on why the Acquire Connection method call failed. Exception from HRESULT: 0Xc020801c (Microsoft.SQlServer.DTSPipelineWrap)Originally the error message reported that the Error Code was "0x8000FFFF", but I can't seem
to reproduce that error code since. Now I am only getting the above error message.From the time I created the original package (when it worked fine) until now, I have been using the same computer, writing to a (32 bit) 2010 Excel file in
a local folder. The filename and location have not changed. The ConnectionString has not changed. The Connnection String I am using is Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Conversion\Conversion Results_dt01.xlsx;Extended Properties="EXCEL
12.0 XML;HDR=YES;". Now an attempt to create and test a NEW Connection Manager yields me this error. "Test connection failed because of an error in initializing provider. Unspecified error.",  whereas before I had
no problems creating a new connection manager.I checked a second SSIS package, which I also built during the past 3 months, which loads multiple sheets from multiple Excel files to a SQL Server 2008 database holding table. It uses the same
ACE OLE DB 12.0 connection to load the Excel speadsheets and this package continues to work fine on the same workstation.In desparation, wondering if the Microsoft ACE OLE DB 12.0 driver had become corrupt (even though the second package
was raising no errors), I did download and install the Microsoft ACE OLE DB 12.0 driver.  That did not solve my problems with the first package.I need to get this package running again ASAP as it is targeted for UAT testing in a
matter of days. Any help with this issue would be greatly appreciated!

I submitted this issue above and now I am having the same problem again. I am using the same local computer, the same operating system (WinXp v 5.1.2600 SP3 Build 2600) as originally described. I am working with the same SSIS package that
writes multiple query results (reports) to an excel spreadsheet. This package has been successfully executed multiple times, but now I am suddenly getting the same error as follows:
Error at 1ConversionContacts [Connection manager "Excel Connection Manager"]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft Access Database Engine" Hresult: 0x80004005 Description: "Unspecified error".
Error at DFlow Write soft deleted duplicate claims to Excel sheet [Excel Destination - write duplicate claim nbrs that have been removed to Excel [61]]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method
call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
The package will not run because of these multiple errors (multiple because it occurs on every single excel destination in the package).
I have Run64BitRuntime set to false on the project. I have triple checked that the excel file name (which I created and can access) exists with the correct name in the correct path, which is local on my machine. The file is the same file in the same
location as when the package worked. I am running the SSIS service under my own network login, as I was when the package worked. I have been consistently getting this same error whenever I change my network password without updating the password
in the SSIS service, but I have triple verified that the service is using my latest password. If I try to open and edit the Excel Destination in any DataFlow task I get the same error. I can successfully create a new Excel Connection Manager pointing
to the same excel file. However if I try to assign the newly created Excel Connection Manager in the data flow, I cannot activate the drop down to choose the Excel sheet without getting an 'Unspecified error' message. I then swapped out
the file with its template version, and ensured the name was updated as correct. I still get the same errors.
Oh, and the SSIS package is extracting data from a SQL Server 2008 database with an ADO.net Connection Manager using Windows authentication. I have no problems with the SQL Server connection, it has always worked and still does. It is only
the connection to excel output file which is locally stored on my machine.
Has anyone got any suggestions for me?

Connection issues with Safari 3

I'm having some connection issues with Safari 3.
When I connect wirelessly, Safari won't load any web pages. I go and use Firefox and everything is just peachy.
I've reset Safari, emptied the cache and whatnot. I went in and checked the permissions, everything checks out.
When I connect with Ethernet, there's nothing wrong, which is my dilemma.
Help would be greatly appreciated.

There are a number of posts in the Leopard forum from people with direct experience with upgrading from Panther to Leopard. Here is a relevant thread from there that should reassure you.:
http://discussions.apple.com/thread.jspa?threadID=1418714
Your system should be fine for Leopard, but you will probably need a current version of Photoshop if you don't already have it. See this download:
http://www.adobe.com/support/products/pdfs/leopardsupport.pdf
Also, Leopard doesn't run Classic (OS 9) apps.
One caveat - first make a bootable backup "clone" of your present system onto an external firewire drive so you can recover if anything goes wrong. You can use the "Restore" tab of Disk Utility to make such a clone, and there are also Panther-compatible versions of Carbon Copy Cloner (v 2.3) and SuperDuper (v 2.1.4), both excellent for this.
It's even possible to a create second Panther clone on a different external volume to create a "dual-boot" system, using that volume to continue to run old applications that you can't run with Leopard.

Sql Server Connection Issues

After reinstalling Windows Server 2008 R2 EE my SQL 2008 R2 Sp2 Instances have some connection issues.
The server were installed under the same hostname, but he got a new sid in my active directory.
On the server there one DB Engine MSSQLSERVER, two named Reporting Services for MS crm 4.0 and SCOM and one Analysis Services Instance.
The DB Engine will collect Data from another DB, before writing to Analysis Services.
Here are the problems on the server:
When I connect via SSMS remotly, I sometimes get this error: Failed to connect to server <hostname> ... Named Pipes Provider, error 40 - Could not open a connection to SQL Server - Error 5
Both RS Instances have many event log errors like "Report Server (Instance) cannot connect to the report server database.". RS Reports are working fine, but sometimes the rendering is taking a long
time.
The DB Engine Agent Job to collect Data sometimes throw the following error: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult:
0x80004005 Description: "Unable to complete login process due to delay in opening server connection". End Error Error: 2013-12-10 06:03:40.41 Code: 0xC00291EC
User use Excel to connect to the Cube on my server. Often they got timeout errors. When they connect again it will work.
Are there any solutons on this?
Thanks a lot!

Hello,
The server were installed under the same hostname, but he got a new sid in my active directory.
Did you connect to SQL Server instance with Windows authentication? Since the SID of domain account is changed, the SQL Server instace may cannot verify the login account which stored in the master with old SID. In that case, please try to connect
SQL Server with SQL authentication and then readd the domian as login the instance.
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

SSIS 2012: SSIS Error Code "Excel Connection Manager" failed with error code 0xC0202009.

Hi,
This is kind of weird issue that I am experiencing with excel connection manager in SSIS 2012. This issue occurs sometimes but when I close and re-open SSDT (SQL Server Data Tools - newer BIDS) then this issues goes off temporarily.
Just FYI, through SSDT environment I executed the package successfully with both settings Run64bit runtime setting to Yes and No when error does not occur.
So far I have installed
http://www.microsoft.com/en-us/download/details.aspx?id=13255 (Microsoft Access Database Engine 2010 Redistributable).
I still remember for older versions of SQL Server (2005 & 2008) that I have executed Excel connection SSIS packages with Run64bit runtime = false i.e. in 32-bit mode. As far as I know I think Excel 64-bit issue has been resolved with SQL Server
2012 release.
Here is the detail of error message:
TITLE: Package Validation Error
Package Validation Error
ADDITIONAL INFORMATION:
Error at Data Flow Task [Excel Source [2]]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection
Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error at Data Flow Task [SSIS.Pipeline]: Excel Source failed validation and returned error code 0xC020801C.
Error at Data Flow Task [SSIS.Pipeline]: One or more component failed validation.
Error at Data Flow Task: There were errors during task validation.
Error at Package [Connection manager "Excel Connection Manager"]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft Access Database Engine" Hresult: 0x80004005 Description: "Unspecified error".
(Microsoft.DataTransformationServices.VsIntegration)
Here are my environment details:
SQL Server 2012 {Microsoft SQL Server 2012 (SP1) - 11.0.3368.0 (X64) } , Excel 2010 (32-bit). I am developing SSIS code on Virtual desktops with Windows 7 32-bit OS.
Also it occurred to me that since Virtual Desktops are on Shared Infrastructure, the source files and SSIS packages (code) can be on Shared drives for e.g. \\<Corpnet>\userdata\<Corp_Users_Grp>\<Username>\Visual Studio 2010\Projects\Integration
Services Project2\Integration Services Project2\Package.dtsx.
Does this kind of Shared drives have any impact to give this issue?
Thanks in advance!
Ketan
P.S.: I had look at this forum question -->
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/903bbe1d-e070-4c43-9d3b-0a5193550029/64bit-error-in-excel-connection-manager-in-ssis

Hi Arthur,
Thanks for your response.
Yes, it looks like SSIS still has bunch of issues with Excel files like as follows:
1) Some times excel source files cannot be parsed by excel source connection manager.
2) For derive column conversion, we can't replace the existing column. rather, we have to add the derived column as " add as new column" which is tough to manage while destination mapping.
3) If an column in excel contains a data which is not of the data type assigned for the column in excel, the excel source reads that data as "null". For the same, we can't validate the data and redirect the erroneous data in reject file. <-- For
this we tried IMEX setting also
4) In multi-tab/sheet excel file, excel source is unable to detect a tab and identify the metadata of the excel.
I am also checking Microsoft connect for Excel issues with SSIS 2012(https://connect.microsoft.com/SQLServer/SearchResults.aspx?SearchQuery=excel#&&PageIndex=22
As worst case scenario, I am thinking of converting Excel to CSV file or Flat text file. (http://www.mssqltips.com/sqlservertip/2772/importing-data-from-excel-using-ssis--part-2/).
Do you think it is advisable to convert Excel into CSV or Flat file.
Thanks,
Ketan

AcquireConnection method call to the connection manager Excel connection Manager failed

I used VS Studio 2008 (BIDS version 10.50.2500.0) on an WinXp machine (v 5.1.2600 SP3 Build 2600) to create a package that writes multiple query results to different tabbed sheets of a single excel spreadsheet. The package was working just fine and has run
successfully multiple times, but all of a sudden when opening the project, every single Data Flow task with an Excel Connection Manager displayed error icons. Each raises the following error message when attempting to open the Advanced Editor:
SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005 Description: "Unspecified error". Error at DataFlow task name: SSIS error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method
call to the connection manager Excel connection Manager failed with error code 0xC0202009. There may be error messages posted before this with more information on why the Acquire Connection method call failed. Exception from HRESULT: 0Xc020801c (Microsoft.SQlServer.DTSPipelineWrap)
From the time I created the original package (when it worked fine) until now:
1) I have been using the same computer, the same login account and the same permissions.
2) I have been writing to the same (32 bit) 2010 Excel file (which I created) in a folder on my local machine.
3) The filename and location have not changed; a template file is used each time to move and overwrite the previous file. Both are in the same locations.
4) I can independently open the target Excel file and the template Excel files with no errors.
6) The ConnectionString has not changed. The Connnection String I am using is
Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\Conversion\Conversion\Results_dt01.xlsx;Extended Properties="EXCEL 12.0 XML;HDR=YES;".
7) Run64BitRuntime is set to False.
8) Delay Validation is set to true
9) This is not running under a SQL job
10) There are no child packages being run
I CAN create a NEW Excel Connection Manager, assigning it the exact same target Excel spreadsheet, successfully, but when I attempt to assign it to the Data Flow destination this error occurs:
"Test connection failed because of an error in initializing provider. Unspecified error."
Thinking that the driver might be corrupt, I opened a second SSIS package, which also uses the Excel Connection Manager (same driver) and this package continues to work fine on the same workstation with no errors.
I have searched online for causes of this error for many hours and found nothing that helps me to solve this issue.
Does anyone have any suggestions for me?

Yes, I have verified that the Excel file is not in use or opened by anyone, including me. It has been two months since I opened this particular package, although I have been working with other packages in this project. I just discovered that another
package in the same project has the same problem - all Data Flows that output to an Excel Destination now have the same error icons. This second packages outputs to an entirely different Excel file than in the first package. A summay:
Package #1 has error on every Excel Destination and uses templateA to overwrite fileA and then writes to fileA
Package #2 has error on every Excel Desintation and uses templateB to overwrite fileB and then writes to fileB
Package #3 has no error on any Excel Destination and is linked to multiple files (none are A or B)
Package #1 and #2 are in the same project, but Package #3 is in a separate project .
I will try replacing the Excel files with new ones for Package 1 and 2.

[Load data from excel file [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messa

Error
[Load data from excel file [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There
may be error message
I am using BIDS Microsoft Visual Studio 2008 and running the package to load the data from excel .
My machine has 32 bit excel hence have set property to RUN64BITRUNTIME AS FALSE.
But the error still occurs .
I checked on Google and many have used Delay validation property at Data flow task level to true but even using it at both excel connection manager and DFT level it doesnt work
Mudassar

Thats my connection string
Provider=Microsoft.ACE.OLEDB.12.0;Data Source=E:\SrcData\Feeds\Utilization.xlsx;Extended Properties="Excel 12.0;HDR=NO";
Excel 2010 installed and its 32 bit edition
Are you referring to install this component -AccessDatabaseEngine_x64.exe?
http://www.microsoft.com/en-us/download/details.aspx?id=13255
Mudassar
You can try an OLEDB provider in that case
see
http://dataintegrity.wordpress.com/2009/10/16/xlsx/
you might need to download and install ms access redistributable
http://www.microsoft.com/en-in/download/details.aspx?id=13255
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SSIS package fails because of excel connection manager when deploying package from development to production

Hello,
When I move the package from development to production package fails due to excel connection manager.
Error message---
Message
Executed as user: Answers\Administrator. ...lt: 0x80040154 Description: "Class not registered". End Error Error: 2014-06-27 05:10:26.50     Code: 0xC0202009     Source: CPRO_Prod_to_XLS_Worksheet_Basic_EX
Connection manager "Excel Connection Manager"     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available. Source: "Microsoft OLE
DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2014-06-27 05:10:26.50     Code: 0xC0202009     Source: CPRO_Prod_to_XLS_Worksheet_Basic_EX
Connection manager "Excel Connection Manager"     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available. Source: "Microsoft OLE
DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2014-06-27 05:10:26.50     Code: 0xC0202009     Source... The package execution
fa... The step failed.
Any help would be appreciated.

Hi Vinay,
As Visakh mentioned, the issue usually occurs because the package runs in 64-bit runtime, however, the Excel driver is 32-bit. According to your another thread, it seems that you use SSIS 2005, right? In SSIS 2005, there is no “use 32 bit runtime” option
for the package executions of a SSIS package job step. In this condition, you have two choices:
Install the 64-bit Microsoft ACE OLE DB 12.0 Provider on the production server. Here is the download link (AccessDatabaseEngine_x64.exe):
http://www.microsoft.com/en-in/download/details.aspx?id=13255
Create a CmdExec type job step instead of SSIS Package job step, so that we can call 32-bit DTExec.exe to execute the package within command line. For more information, please see:
http://support.microsoft.com/kb/934653/en-us
Regards,
Mike Yin
TechNet Community Support

Troubleshoot TC connectivity issues

My Time Capsule has worked great for over two years. All of the sudden, my MacBook Pro started having connectivity issues. Eventually (over about two weeks), the issues became a total lack of wi-fi internet in our household. I disconnected and powered off the modem and the TC. I even called my ISP (Comcast). We reset everything and everything else works fine (phone, TV and Internet plugged directly into modem). I cannot plug my MacBookPro into the modem since I have no ehthernet port. The light on the TC blinks amber.
Our local computers can access the files stored on the TimeCapsule, but airport utility gave the errors below (see pictures) before the comcast assisted reset. Now the Internet icon shows green in airport utility, but the error on the top icon says "no internet access" (Or something like that, I am submiting this from memory since I am using the wi-fi at work- and I have NO IDEA why they pics are upside down, they are on my computer right side up).
Please tell me there is an easy fix, or at least one that can be accomplished via a computer that cannot cannect to the internet at the same time as the time capsule.

Your pictures sadly did not load correctly.. I see nothing but a blank square with the file name. You appear to have spaces in the names.. never a good idea. They are photo 1.jpg and photo 2.jpg
Try again if you want.
A Gen3 TC is now past 3years.. well past if you bought it early in the life of the Gen3. Oct 2009.
The economic life of most computer equipment is now 3years.
You should at least try a factory reset of the TC.
Before doing this I would also downgrade the TC firmware to 7.6.1 or even 7.5.2. You do this by holding the option key when clicking version.
And redo the setup. No files on the hard disk are lost doing this.
If the computers are using Mavericks.. I do strongly suggest you set names correctly.
Make all names in the TC short, Less than 10 characters is excellent.. no more than 20.
No spaces.
Pure alphanumeric.. no apostrophe. It is not legal even in Apple network as it is replaced.
Mavericks changed to using SMB networking by default and it leads to all kinds of issues.
But if you have network connection to the TC by wireless but not ethernet from WAN port to the main comcast modem.. the internals of the TC are simply failing.
It is old and tired. Repair is not part of apple's world view.
I have repaired them. And posted instructions but it is well beyond a tinkerer .. this needs fairly committed DIY repair.
https://sites.google.com/site/lapastenague/a-deconstruction-of-routers-and-modem s/apple-time-capsule-repair/new-issue-with-a1355-gen-3-tc

BRI-to-PRI Connectivity issues

I'm having some serious BRI-to-PRI connectivity issues, and I was hoping someone out there could offer some assistance. The devices call one another perfectly, but they just both send magic numbers out and never get the data from the other device so they are unable to setup a layer to connection. We're using 804 series routers to dial into a PRI running on a 2811. Here's the configurations running on the 804 -
sh run
Building configuration...
Current configuration : 601 bytes
version 12.2
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
hostname Router
ip subnet-zero
isdn switch-type basic-ni
interface Ethernet0
no ip address
shutdown
interface BRI0
ip address 172.16.213.2 255.255.255.252
encapsulation ppp
dialer map ip 172.16.213.1 speed 56 7349291319
dialer-group 1
isdn switch-type basic-ni
isdn spid1 73492960780101
isdn spid2 73492960790101
isdn incoming-voice data
ip http server
ip classless
dialer-list 1 protocol ip permit
line con 0
stopbits 1
line vty 0 4
end
And on the t1 and serial of the 2800 series.
interface Serial0/2/1:23
no ip address
dialer pool-member 1
isdn switch-type primary-ni
isdn incoming-voice data
no cdp enable
end
interface Dialer1
ip address 172.16.213.1 255.255.255.252
encapsulation ppp
dialer pool 1
dialer remote-name Router
dialer string 7349296078 class 56
dialer caller 7349296078
dialer caller 9296078
dialer caller 7349296079
dialer-group 1
peer default ip address 172.16.213.2
fair-queue
end
I've tried using encapsulation ppp on the s0/2/1:23 interface, but it drops connectivity with the CO as soon as I type the command. Any help someone could offer would be excellent as we're all stumped around here.
Thanks,
Steve

Steve,
I have seen this issue many times before and it always turned out to be an issue on the Telco network. It's quite possible either the line itself or some equipment on the provider network mayn't be provisioned for DATA or faulty equipment on their network.
Let us know how you do with it.
HTH
Sundar

MS EXCEL connectivity issue in OBIEE11.1.1.5 in online mode

Similar Messages

Maybe you are looking for