Logging in Agents
What criterion determines which CTI Sever (7.1.2) a CTI OS agent logs into for a duplexed system? I have done a ton of tests and can report with 100% certainty that it is not round robin and does not balance out perfectly even. If there is a formula or a test the desktop runs while logging in could someone please share it with me?
As a follow up I've found some evidence that suggests if the last octet of the client IP address was odd then it would log into CTI OS A and if even it would log into CTI OS B on first attempts. This does not explain why after logging in and out on multiple occasions the system chooses to switch sides.
Please, if anyone has any information, feel free to share.
Similar Messages
-
One of our SQL Server started creating SQLDUMP file and and on investigation I found the error longs are filled with Errors 3624 & 17066. There is transnational replication configured on one of the databases is the LogReader Agent is failing error "The
process could not execute 'sp_repldone/sp_replcounters' on XXXXX".
Not sure if both these Assertion & Logreader Agent errors are related. Before I remove and put the replication, I wanted to check if anyone has experienced the same issues or aware of what the cause.
***********Error messages from SQL Logs******
**Dump thread - spid = 0, EC = 0x0000000111534460
Message
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to
Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
Error: 3624, Severity: 20, State: 1.
SQL Server Assertion: File: <logscan.cpp>, line=2123 Failed Assertion = 'UtilDbccIsInsideDbcc () || (m_ProxyLogMgr->GetPru ()->GetStartupState () < RecoveryUnit::Recovered)'. This error may be timing-related. If the error persists after rerunning
the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
Error: 17066, Severity: 16, State: 1.
External dump process return code 0x20000001.
External dump process returned no errors.
Thank you in advance.You need to determine if this error is a transient one or a show stopper one.
It sounds like your log reader agent has crashed and can't continue.
If so your best bet is to call Microsoft CSS and open a support incident.
It also sounds like DBCC CHECKDB was running while the log reader agent crashed.
If you need to get up and running again run sp_replrestart, but then you might find that replicated commands are not picked up. You will need to run a validation to determine if you need to reinitialize the entire publication or a single article.
I have run into errors like this, but they tend to be transient, ie the log reader agent crashes, and on restart it works fine.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941 -
Log Reader Agent: transaction log file scan and failure to construct a replicated command
I encountered the following error message related to Log Reader job generated as part of transactional replication setup on publisher. As a result of this error, none of the transactions propagated from publisher to any of its subscribers.
Error Message
2008-02-12 13:06:57.765 Status: 4, code: 22043, text: 'The Log Reader Agent is scanning the transaction log for commands to be replicated. Approximately 24500000 log records have been scanned in pass # 1, 68847 of which were marked for replication, elapsed time 66018 (ms).'.
2008-02-12 13:06:57.843 Status: 0, code: 20011, text: 'The process could not execute 'sp_replcmds' on ServerName.'.
2008-02-12 13:06:57.843 Status: 0, code: 18805, text: 'The Log Reader Agent failed to construct a replicated command from log sequence number (LSN) {00065e22:0002e3d0:0006}. Back up the publication database and contact Customer Support Services.'.
2008-02-12 13:06:57.843 Status: 0, code: 22037, text: 'The process could not execute 'sp_replcmds' on 'ServerName'.'.
Replication agent job kept trying after specified intervals and kept failing with that message.
Investigation
I could clearly see there were transactions waiting to be delilvered to subscribers from the followings:
SELECT * FROM dbo.MSrepl_transactions -- 1162
SELECT * FROM dbo.MSrepl_commands -- 821922
The following steps were taken to further investigate the problem. They further confirmed how transactions were in queue waiting to be delivered to distribution database
-- Returns the commands for transactions marked for replication
EXEC sp_replcmds
-- Returns a result set of all the transactions in the publication database transaction log that are marked for replication but have not been marked as distributed.
EXEC sp_repltrans
-- Returns the commands for transactions marked for replication in readable format
EXEC sp_replshowcmds
Resolution
Taking a backup as suggested in message wouldn't resolve the issue. None of the commands retrieved from sp_browserreplcmds with mentioned LSN in message had no syntactic problems either.
exec sp_browsereplcmds @xact_seqno_start = '0x00065e220002e3d00006'
In a desperate attempt to resolve the problem, I decided to drop all subscriptions. To my surprise Log Reader kept failing with same error again. I thought having no subscription for publications log reader agent would have no reason to scan publisher's transaction log. But obviously I was wrong. Even adding new log reader using sp_addLogreader_agent after deleting the old one would not be any help. Restart of server couldn't do much good either.
EXEC sp_addlogreader_agent
@job_login = 'LoginName',
@job_password = 'Password',
@publisher_security_mode = 1;
When nothing else worked for me, I decided to give it a try to the following procedures reserved for troubleshooting replication
--Updates the record that identifies the last distributed transaction of the server
EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1
-- Flushes the article cache
EXEC sp_replflush
Bingo !
Log reader agent managed to start successfully this time. I wish if I could have used both commands before I decided to drop subscriptions. It would have saved me considerable effort and time spent re-doing subscriptions.
Question
Even though I managed to resolve the error and have replication funtioning again but I think there might have been some better solution and I would appreciate if you could provide me some feedback and propose your approach to resolve the problem.Hi Hilary,
Will the below truncate the log file marked for replication, is there any data loss, when we execute this command, can you please help me understand, the internal working of this command.
EXEC sp_repldone @xactid = NULL, @xact_segno = NULL, @numtrans = 0, @time = 0, @reset = 1 -
Does Log reader agent use sa in sp_replcmds?
We have publisher, subscriber, and distributor on separate servers. Replication is Push Transactional with replication agents setup to run under SQL Agent account context. We are in the process of disabling sa from everywhere and I am monitoring sessions
that use sa to make sure there is no impact.
I see that log reader agent session sometimes uses sa as login name in its sessions on publisher. In sys.dm_exec_sessions, there are two columns for login: Login_Name and Original_Login_Name. The Login_Name shows sa. Most of the time the SPID of log reader
agent on publisher shows the SQL agent service account as login name of the session. But sometimes the same SPID shows sa as login name. This always coincides with session running SP_REPLCMDS without any parameters and also messages like "The Log Reader
Agent is scanning the transaction log for command to be replicated. Approximately...." in Replication Monitor. Normally, the session would run SP_REPLCMDS giving some parameters. When this happens, in sys.dm_exec_sessions, the log reader SPID keeps showing
Original Login name as that of Distributor agent service account but login_name sa.
Does sp_replcmds run as sa? If I disable sa on publisher, distributor, and subscriber, will it break replication?it all depends on what accounts you have set for log reader agent security, distribution agent security and snapshot agent security etc.. If you have not configured anything to use sa then you can disable and it should not have an issue.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com -
Log Reader Agent error "could not execute sp_replcmds' and causes stack dump
Publisher/Subscriber db: SQL 2008 R2, 2000 compatability mode
Distributor database is on separate server.
(note: There is another database on this instance that is running replication without error, it is not in compatibility mode)
After snapshot agent finishes, the log reader agent starts and fails immediately with this error in the Agent Job.
Then I get a SEV20 error and stack dump in the error logs.
Date 6/12/2014 3:12:26 PM
Log Job History (SERVER\INSTANCE-DBNAME-43)
Step ID 2
Server ######RT02
Job Name SERVER\INSTANCE-DBNAME-43
Step Name Run agent.
Duration 00:00:01
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
2014-06-12 20:12:26.302 Copyright (c) 2008 Microsoft Corporation
2014-06-12 20:12:26.302 Microsoft SQL Server Replication Agent: logread
2014-06-12 20:12:26.302
2014-06-12 20:12:26.302 The timestamps prepended to the output lines are expressed in terms of UTC time.
2014-06-12 20:12:26.302 User-specified agent parameter values:
-Publisher SERVER\INSTANCE
-PublisherDB DBNAME
-Distributor ######RT02
-DistributorSecurityMode 1
-Continuous
-XJOBID 0x8958DF32810C6849B28A037A8FF8DD92
-XJOBNAME SERVER\INSTANCE-DBNAME-43
-XSTEPID 2
-XSUBSYSTEM LogReader
-XSERVER SERVER\INSTANCE
-XCMDLINE 0
-XCancelEventHandle 0000000000000F98
-XParentProcessHandle 0000000000000F34
2014-06-12 20:12:26.459 Parameter values obtained from agent profile:
-pollinginterval 5000
-historyverboselevel 1
-logintimeout 15
-querytimeout 1800
-readbatchsize 500
-readbatchsize 500000
2014-06-12 20:12:26.493 Status: 4096, code: 20024, text: 'Initializing'.
2014-06-12 20:12:26.493 The agent is running. Use Replication Monitor to view the details of this agent session.
2014-06-12 20:12:27.885 Status: 0, code: 20011, text: 'The process could not execute 'sp_replcmds' on 'SERVER\INSTANCE'.'.
2014-06-12 20:12:27.886 The process could not execute 'sp_replcmds' on 'SERVER\INSTANCE'.
2014-06-12 20:12:27.886 Status: 0, code: 21, text: 'Warning: Fatal error 3624 occurred at Jun 12 2014 3:12PM. Note the error and time, and contact your system administrator.'.
2014-06-12 20:12:27.886 Status: 0, code: 22037, text: 'The process could not execute 'sp_replcmds' on 'SERVER\INSTANCE'.'.
I've tried removing replication and setting it back up again, restarting SQL, and restarting the server itself.
Let me know if you need any more information to help troubleshoot. Thanks.
Please help, thanks.Hi,
Enable Verbose logging and check the results.
Execute following commands: -Output C:\Temp\OUTPUTFILE.txt –Outputverboselevel 2.
Please refer following KB article for your reference -
http://support.microsoft.com/kb/q312292/
Thanks.
Tracy Cai
TechNet Community Support -
Log Reader Agent is not able to read Transaction Log of Publisher database.
Hi,
There is no restore or change in recovery model or detach-attach action performed on my production database but still I am seeing below error message from Log Reader Agent-
Error messages:
The process could not execute 'sp_repldone/sp_replcounters' on 'ProdInstance'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help:
An error occurred while processing the log for database 'MyDatabase'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log. (Source: MSSQLServer, Error number: 9004)
The process could not set the last distributed transaction. (Source: MSSQL_REPL, Error number: MSSQL_REPL22017)
Get help: The process could not execute 'sp_repldone/sp_replcounters' on 'ProdInstance'. (Source: MSSQL_REPL, Error number: MSSQL_REPL22037)
Note- CheckDB on production and distribution database executed successfully. Also, I need subscriber to be a true copy of publisher so I think sp_replrestart is not an option for me.
My question is how to resolve this issue? I am thinking that reinitialization should resolve the problem but what if this is not going to resolve? Do I need to reconfigure the transaction replication? Please sugegst.Hi,
Please check out this link on how to resolve “The process could not execute 'sp_repldone/sp_replcounters'” error.
http://blogs.msdn.com/b/repltalk/archive/2010/02/19/the-process-could-not-execute-sp-repldone-sp-replcounters.aspx
The possible cause could be:
1.The last LSN in Transaction Log is less than what the LSN Log Reader is trying to find. An old backup may have been restored on top of Published Database. After the restore, the new Transaction Log doesn't contain the data now distributor & subscriber(s)
have.
2.Database corruption.
Since you have not restored the published database, I suggest you run
DBCC CHECKDB to confirm the consistency of the database. Refer to the How to fix in the above link.
Thanks.
Tracy Cai
TechNet Community Support -
Log Reader Agent and Snapshot Agent wont start
Hi There,
I've two SQL 2012 servers with multiple instances installed.
I've started replicating the databases in these instances using transactional replication and thus far they've worked without a hitch.
One of my instances, annoyingly, has an issue where the Log Reader Agent and Snapshot Agent refuse to start, and I've followed exactly the same process as with the other instances\databases.
The Agents are configured to make use of a domain user account with sysadmin permissions to the instances on both servers.
I get the following two error when I View Log Reader Agent Status:
The job failed. The Job was invoked by User sa. The last step to run was step 2 (Run agent.).
I've asked the agent to run as my DOMAIN\sqlservice account, so I've no idea why it's moaning about sa?!!?
I get the following error when I View Snapshot Agent Status:
The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Di
If I try to start either agent I'm told that the request to run job was refused because the job has been suspended, "Changed database context"?? Error 22022.
Can anyone help?This is because your job owner is sa. Right click on your job and notice the owner - but is should be sa.
You likely have another issue. You may need to run the job and configure it for logging to see what the error is.
http://support.microsoft.com/kb/312292/en-us
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941 -
On a server with 4 merge publications I'm getting errors from a Log Reader Agent.
From documentations it seems to me that Log Reader Agent must be present only if there are some transactional publication, so I think that errors depends on this.
Probably the Log Reader Agent was created some time ago with a transactional publication that no longer exists.
So my question is: can I remove the Log Reader Agent?
To remove it can I simply remove the associated job?
The error are all like this:
The process could not execute 'sp_repldone/sp_replcounters' on 'GEREONTK'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20011)
Get help: http://help/MSSQL_REPL20011
Unable to execute procedure. The database is not published. Execute the procedure in a database that is published for replication. (Source: MSSQLServer, Error number: 18757)
Get help: http://help/18757
The process could not set the last distributed transaction. (Source: MSSQL_REPL, Error number: MSSQL_REPL22017)
Get help: http://help/MSSQL_REPL22017
Thanks,
RobertoThere's no more transactional replication on database but still exists two merge replications on some tables of the same db (publication Gereon and GereonPortfoliosAll).
So I've no replication to drop but only a Log Reader Agent that seems to be a survivor from a previous transactional pubblication.
In these day I've stopped the job related to the Log Reader Agent, and merge replication are working right. So I think I can remove this Agent from the server.
In
Log Reader Agent definition on MSDN I've found "The Replication Log Reader Agent is an executable that monitors the transaction log of each database
configured for transactional replication and copies the transactions marked for replication from the transaction log into the distribution database." so it seems to me that is not related to merge replication and it safe to be removed.
Thanks -
may i know the process involved in log reader agent or definition.
please suggest me about it.The following is an excerpt from here.
Modifying Data and the Log Reader Agent
The Log Reader Agent runs at the Distributor; it typically runs continuously, but can also run according to a schedule you establish. When executing, the Log Reader Agent first reads the publication transaction log (the same database log used for transaction
tracking and recovery during regular SQL Server Database Engine operations) and identifies any INSERT, UPDATE, and DELETE statements, or other modifications made to the data in transactions that have been marked for replication. Next, the agent copies those
transactions in batches to the distribution database at the Distributor. The Log Reader Agent uses the internal stored procedure sp_replcmds to get the next set of commands marked for replication from the log. The distribution database
then becomes the store-and-forward queue from which changes are sent to Subscribers. Only committed transactions are sent to the distribution database.
After the entire batch of transactions has been written successfully to the distribution database, it is committed. Following the commit of each batch of commands to the Distributor, the Log Reader Agent calls sp_repldone to mark
where replication was last completed. Finally, the agent marks the rows in the transaction log that are ready to be purged. Rows still waiting to be replicated are not purged.
Transaction commands are stored in the distribution database until they are propagated to all Subscribers or until the maximum distribution retention period has been reached. Subscribers receive transactions in the same order in which they were applied at the
Publisher.
Satish Kartan http://www.sqlfood.com/ -
How to stop the auto-start of log reader agent (replication) right after my database is restored?
I have the scenario where the SQL server is restored (after migration).
This database has transactional replication set-up on one of the databases. When I do a manual delete and restore of the database, I see that the replication starts right after the publisher and subscriber are restored.
Replication agents should not start and run before the integrity checks are completed. How to stop the replication from auto starting right after the migration?
Thanks in advance - JebahThanks Pradyothana, I have disabled the logreader, distribution agents through sp_update_job in Tsql script. I have also verified that there are no pending transactions to be replicated to the subscriber, I see that the job is still being executed. Is there
any other way to disable the jobs?
Steps I followed
Started with a Working publication and subscription
Disabled the jobs (log reader and distribution agents)
Backed up publisher, subscriber, distribution and msdb
Deleted the publication, subscription, publisher and subscriber
Restored the publisher, subscriber, distribution and msdb
Enabled the jobs and executed sp_replrestart
Observations/Issues
Replication does not work
Replication monitor does not show any error
Jobs are shows as enabled but not started in job monitor
Not able to start/stop the log reader and synchronization manually.
I am not sure if I have missed something while restoring the db.
Thanks in advance -
Agent Logs under agent names shows no information in CSD
I have 1 supervisor and that supervisor needs to see the agent logs under each individual agent name but for some reason there is nothing being reported there. If an agent takes a call or makes a call, inbound or outbound will appear under the agent name with data but logs just will not show anything. Is there a setting somewhere i'm missing?
You may have already checked this and apologize if you did, but have you verified that the supervisor is configured to see the columns under the Logs?
In Supervisor, go to View - Preferences. In the window that appears, go to Team - Agent - Logs and click on "Configure" on the right side, in the "Columns" field. Make sure that the columns have a check mark next to them.
If that is ok, have you tried running Supervisor from a different machine to see if that works? -
CSA MC Events Log and Agent Panel Events Corrolation
I have recently install CSA MC 6.0.0.201 and the agent on a Win2003 server. I have a question of events showing up in the agent panel and not showing up in the MC events log.
I see a number of events in the agent 'panel' event viewer. At the end of the event is a number in brackets like [176].
When I look at the MC event viewer but those events are not being reported.
My query is:
#1 I believe the example [176} is the rule being triggered. So if the event is not showing up in the event viewer how to I find that rule in the policies? I finally did stumble across the rule and I see that logging is disabled for that rule, but finding that rule was a needle in the haystack search. Is there an easier way to find rules?
#2 Maybe I do not understand this part but in the MC I placed this server (the one with the MC) into 'Audit Mode' in hopes that would get the events from the agent to show up in the MC event log. No good. Is there a way to get all events - even if the rule says to not log the event - so show up in the MC log so I can creat an exception?
Thanks
LarryTom,
I think I may have made some progress. Yes I'm in advanced mode. I went into Systems | Groups and first selected the 'Servers' and turned on logging. Still most the events in the agent event viewer were not making it to the MC event log.
So I went back in to the Systems | Groups and found there was a group called 'Servers - CSA Management Center' and turned on logging there and that got the events to start flowing into the MC events.
Maybe this will help me get going.
Larry -
This log -------------policy agent 2.1 for iis5.0
Sun Java System Identity Server Policy Agent 2.1 for Microsoft IIS 5.0
Sun\Identity_Server\Agents\2.1\debug\C__Inetpub_wwwroot\amAgent
2004-07-25 18:06:22.156 Warning 1064:00D01120 PolicyAgent: OnPreprocHeaders(): Identity Server Cookie not found.
2004-07-25 18:06:22.156 Error 1064:00D01120 PolicyAgent: do_redirect() ServerSupportFunction did not succeed: Attempted status = 302 Found
2004-07-25 18:06:22.156 Warning 1064:00D01120 PolicyAgent: OnPreprocHeaders(): No cookies found.
2004-07-25 18:06:22.156 Error 1064:00D01120 PolicyAgent: do_redirect() ServerSupportFunction did not succeed: Attempted status = 302 Found
2004-07-25 18:07:53.921 Error 1064:00D01120 PolicyEngine: am_policy_evaluate: InternalException in Service::getPolicyResult with error message:Policy not found for resource: http://guorui.mygodsun.com:49153/index.asp and code:7
2004-07-25 18:07:53.921 Warning 1064:00D01120 PolicyAgent: am_web_is_access_allowed(http://guorui.mygodsun.com:49153/index.asp, GET) denying access: status = no policy found (7)
2004-07-25 18:07:53.937 128 1064:00D01120 RemoteLog: User amAdmin was denied access to http://guorui.mygodsun.com:49153/index.asp.
2004-07-25 18:07:54.062 Error 1064:00D01120 PolicyAgent: do_redirect(): Error while calling am_web_get_redirect_url(): status = success
2004-07-25 18:07:54.078 Error 1064:00D01120 PolicyAgent: do_redirect() WriteClient did not succeed: Attempted message = HTTP/1.1 403 Forbidden
Content-Length: 13
Content-Type: text/plain
403 Forbidden
from that log,help me
my:
Sun Java System Identity Server 6.1
Sun Java System Directory Server 5.2
Sun Java System Identity Server Policy Agent 2.1 for Microsoft IIS 5.0
help me for that how config?
what error ?
thanks!Sorr for so many people faced the sam or similar issues. I just joined this support a short while. If you think any old problem which is still critical to you, please repost. We shall try our best to give you assistance. Jerry
Here are some of tips for debugging Web agent.
From the AMAgent.properties, are both IIS and AM are in the same domain? If they are not, then you need to use CDSSO. Also please check in AM, under "Service Configuration-> Platform -> Cookie Domains" , whether cookie is set for the entire domain which includes AM and IIS ("test.com") or just the AM machine name.
Also check whether correct value for "Agent-Identity Server Shared Secret" is entered. This should be your internal ldap password (amldapuser). In the AMAgent.properties for the below property the password will be encrypted and assigned: "com.sun.am.policy.am.password".
Could you also check if the Identity servver and the IIS web server are time synchronized. The problem may be that agent requests policy decisions and the response from server may be timed out due to non-syncrhonized clock.
Don't forget to restart the whole IIS service using internet
management console after making agent changes.
Some of the common error codes:
20: Application authentication failed. This occurs when Agent cannot sucessfully authenticate with Identity Server. This is mainly due to incorrect password for agent entered during agent installation. Please refer to another faq describing how to change password.
7: Policy not found. This error occurs typically if there are no policies defined on Identity server for the given web server URL. Otherwise, there may be time skew between Identity Server and Agent. So, polices fetched from Identity Server is instantly flushed by Agent and attempted to refetch over and over again. This can be solved by running rdate or similar command to synchronize time between the two machines. It is recommended to run NNTP server syncrhonize times between your Identity systems. -
Log Reader Agent is getting stopped
I am getting in the logreader agent and it getting stopped Abruptly showing below error
"The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher,
and Distributor are still active."
When i start the agent it gets started but can i know why its getting stopped and how can i resolve this issue.
Thanks in advance.I wish you have mentioned this was Oracle at the beginning:)
This is a known problem with Oracle Publishing. Microsoft is now recommending you use Attunity to track changes in Oracle and use SSIS to replicate the commands.
Open a support incident with Microsoft to help you to address the log reader problem and advise you on the best approach to this.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941 -
UCCX 7.1 - Check Logged in Agents for 2 CSQ's in same line
I have a logged in resources check that checks a CSQ String. Can I add another CSQ to this check? Right now it says: " intLoggedInResources = Get Reporting Statistic (Logged-In Resources{strTargetCSQ}from CSQ IPCC Express". I need it to check "strCanadaCSQ" at the same time.
No you cannot. One CSQ at a time with the Get Reporting Stats Step.
Maybe you are looking for
-
I just bought a Macbook Air almost a month now. When I bought it, the technician installed Microsoft Office 365 as they were having a promotion at the time. However after a week of using it, it started popping up a notice saying that it cannot verify
-
Is There any API in receivables payment will made against closed invoices ?
Hi ALL, i have requirement as below. i am doing AR Invoice Data Migration for Instance 11.5.5 (as a Source Instance) to the new instance R12 (as a target instance). Both open and closed invoices will have to be migrated from 11.5.5 to R12 to provide
-
Adobe Air 1.5 refuses to install
Hi, troubles getting AIR installed, perhaps somebody can give me a hint? System is a Quad core, 4GB RAM, MS-Vista 64 bit with SP1 all patches, Flash 10.0.12 installed. "Adobe Air installer" version 1.5, started as Administrator, hangs, no further mes
-
Hi Experts, I need to know when the user click at the button, but my toolbar is standard. I'm using the class cl_gui_alv_grid to generate ALV and show me the buttons standard. Somebody has any ideia how Can I to do this?? Thanks very much.
-
Org Modeler 3.0: Authentication Settings
Hi, I'm using Org Modeler 3.0 When I go to security settings->Authentication Settings, the settings never takes effect. For example, I change the Authentication Mechanism to Anonymous, but I was still prompted to logon. If you enter my crendital, it