Closed Bug 411123 Opened 18 years ago Closed 18 years ago

Network calendars error: 0x804a0303 on creation and use

Categories

(Calendar :: Lightning Only, defect)

Lightning 0.7
x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: sam.rae, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b2) Gecko/2007121120 Firefox/3.0b2 Build Identifier: T-bird version 2.0.0.9 (20071031), lightning 0.7 Whenever I set up a network calendar I get the above error, stating that the location I selected is not a network share. It is a network share but the path entry field doesn't validate UNC paths, so it must want a normal path. The one I'm using is T:\pmdserver\network_support for example. T: is a mapped network share. Reproducible: Always Steps to Reproduce: 1.File>New>Calendar>On the network>Next 2.Either format produces the same problems>enter location 3.Name and colour don't affect it Actual Results: 10 error boxes with the above message about the drive not being a network share Expected Results: Created a network calendar
Version: unspecified → Lightning 0.7
You need to specify a valid file:// URL for the .ics file, e.g. "file:///T:/pmdserver/network_support/calendar.ics".
That stopped it returning the error but it didn't actually create the file or put the heading into the menu.
The .ics file will not be created unless you create one event or task. And what do you mean with "didn't put the heading into the menu"?
Sam, any update on the information requested in Comment #3? Maybe you could retest with a Lightning 0.8pre nightly test build? It now has a File -> Open -> Calendar File command like Sunbird that allows to browse for the .ics file (instead of having to enter the URL manually.)
No response from reporter, resolving incomplete. Please reopen the bug if you can provide the requested information and the issue still exists using Lightning 0.8.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.