I have fullcalendar scheduler script installed and everything was working fine for about 5 months. This week I noticed, that events are rendered only until Wednesday, August 10, 2016. After this day, no event is rendered, although data form db is loaded into the feed also behind this date.
http://www.slotenis.si/rezervacije/?lid=2
Strange problem, what could be the reason?
My mistake, my data source was limited to 500 records retrived from MySQL db. Once this limitation was removed, everything was working again.
Related
I have an Access database that was designed and developed back in 1997 - 99. all user interaction is through forms and reports, there is no end user access to the backend tables. It has worked flawlessly for the last 19 plus years. Both front and back end are still in .mdb format, but the front ends which are local to the workstation and are replaced with a clean copy upon every login are running on Access 2016. There are at a maximum, 6 users in the database at one time, usually there are only 4.
Starting about 90 days ago the back end would randomly corrupt when a request to write a record was made. The error message is “Database is in an unrecognized format”. We have replaced old workstations and the Server that host the back end, in addition we replaced the switch that all computers connect to. On the workstations that were not replaced Office has been re-installed and all updates applied to it. The corruptions cannot be reproduced consistently, it happens in different forms and from different workstations randomly. After the corruption, we have to delete the lock file, compact and repair the Back end and it will work just fine until the next corruption, and the data that was attempted to be written is there, so there has been no Data loss.
The back end data was rebuilt last year to remove the random primary key values, that were created when the database was replicated over a dial up modem back when the database was first developed. The replication functionality was turned off approximately 17 years ago. The back end has been rebuilt again from scratch, each table was created in a new Database and all the index's and relationships were rebuilt. The data from each table was exported to a Text file and then imported into the new database.
There were no changes made to the front end in the prior three or four weeks before this issue started happening. Just to ensure that it was not something in the frontend, it was rolled back to a version that was working fine in February of this year, unfortunately that did not resolve the issue
None of these steps have resulted in resolving the back end corruption, and if anything, the corruption is happening more frequently. The only thing that works at this point is to have one user at a time in the database, as soon as the second user opens the frontend, the back end will corrupt within a few minutes.
Any thoughts or ideas would be greatly appreciated.
Thank you
Steve Brewer
Update:
This is a known bug introduced by one of the Office/Windows updates. See http://www.devhut.net/2018/06/13/access-bu...ognized-format/ for all the details and workaround/solution.
We're using an Access application that stores and retrieves information from SharePoint, and the times and dates get viewed through the 'filter' of the Time Zone settings on SharePoint.
This has started to cause a problem when just trying to enter a date with no time. People marked as CST will see 7/1/2014 0:00, but those in PST will see 6/30/2014 22:00. Calculations that organise metrics by date would then show the same entry in June for PST users and July for CST.
Is there a way to adjust for this? I don't WANT to be capturing a time in this field, but since it's a Date/Time field on SharePoint, it's attaching a time anyway. Would changing the field in question to 'String' work or would that cause more problems than a more adaptive solution?
(I've read links that popped up in 'Questions that may already have your answer', conducted other searches on and off Stack.)
After a bit of testing after all my Users went home except for one, I found that just changing the type on SharePoint for the fields in question from 'Date/Time' to 'Text (Single Line)' worked perfectly. My Tester had no issues with the VB used to store information and bringing up the raw tables showed the 'proper' date stamps after a restart of the client database.
It seems a little too good to be true, but it appears to be a victory! I'll definitely come back here with an update if anything blows up.
I recently upgraded from 2005 to 2012 (about 10 months). When I first started using SSMS2012 it worked great was able to open multiple windows in a particular database. For about that last 2-3 months SSMS hangs when I try to open more than 1 query window or open a file. It is random but happens a majority of the time. I have been able to interrupt the hang a few times. When I interrupt it I get the login screen and it sits there trying to log in apparently unsuccessfully. If I cancel the login and try it again with the same entries it connects just fine and things are great, but I have to do this for every window and I cannot often break into that screen before it stops responding.
I have searched extensively and have not found an answer to this problem. It only appears to be happening to a particular instance. The instance does not show any signs of issues, has been rebooted and configuration checked for inconsistencies, etc. I am at a loss. If anyone has experienced this and has been able to resolve it I would appreciate a response.
Again this is a fresh install of 2012 standard with 2005 imported databases. All indications show that it is working fine. compatibility level for a majority of the databases are still 90, until I can clear them for 11 with the software they house. I have a test environment with the restored versions on a different server and no issues result from that instance - I can open up multiples without incident. My belief is it is something with that particular instance, but I am not sure where else to look.
Thank you in advance.
This is a strange problem im getting every now and then.
Im parsing a JSON and storing it into CoreData using several Entities. I save the data from the JSON and then I pull it to show it on a screen.
The app works perfectly fine when it's launched from XCode, always. But when I open it any other time from the iPhone it sometimes, it only happens roughly once every 20 times, it doesnt show the data saved from the JSON, I beleive the problem is that the info saved in CoreData is corrupted some how, the dates specifically, sometimes I can get to see that the dates are null on screen.
Here's how I save the dates
[event setValue:[df dateFromString:(NSString *)[key objectForKey:#"startSaleDate"]] forKey:#"dateStartSale"];
[event setValue:[df dateFromString:(NSString *)[key objectForKey:#"finishSaleDate"]] forKey:#"dateEndSale"];
If I relauch the app, that is killing the app and launching it again, it all works perfectly again.
The JSON is always correct, apparently it does the funky thing after some hours being installed in the phone. Does that make sense?
Thanks.
[UPDATE]
I did some more testing. This is a difficult bug to catch because it only happens after several hours in the background.
Figure out that the only problem is actually storing NSDates. Not the rest of data. After some time in the background it fails to save the NSDate, even though the JSON has a valid Date it stores null. And everytime I refresh it keeps on storing null.
If I kill and launch the app it stores correctly the date.
I tried using models but it happens the same thing.
Any ideas? Im quite lost now.
I had such an issue once I believe. In my case it had something to do with the display mechanism.
--> Try reloading your data more frequently (or resetting your fetched results controller) to test this.
Sorry guys, It was all a silly mistake from my part.
I thought it was something related to the background because I wasnt able to reproduce it, and since it only happened every now and then.
Well the thing is that I if you went through the screens in a certain way a following a certain order a NSDateFormatter got badly initialised and that made that the dates weren't saved properly.
SO nothing to do with CoreData...
So I have a document library with date, alert and alert-date fields.
The date and alert fields are completed when a doc is uploaded, and there is a workflow which takes the alert away from the date (and also takes an extra day off) and sets it as the alert-date. E.g. If the date is 15/07/2013, and the alert is 1 month, the workflow sets the alert-date to 14/06/013 (15/07/2013 - 1 month and a day). The alerts have options of 1 month, 3 months, 6 months or 1 year. A extra day is always taken off as these workflows are triggered by information management policy which only allows conditions of +1 day (the day is taken away via the workflow and then added via information management policy).
The problem comes when a .docx file is uploaded, as all the alert-dates (even if they relating date and alert aren't populated) are set to 01/01/1900.
I know SharePoint workflows pretty well and have never come across this problem before, so was just wandering if anyone else has and knows a solutions?
Thanks,
Josh.
Found a solution:
The alert-date fields didn't seem to be set at the same time that the workflow was looking them up (for docx files). So I added a minute pause at the beginning of the workflow which gave enough time for all the dates to be set and then for the workflow to look them up, and there are now no issues.
Thanks,
Josh.